MuseScore for Mac

[Joachim Ganseman]

Dear all,

I've compiled a first MuseScore for Mac version and put it online at
http://tinyurl.com/cul4ah for the moment. A few very important notes
however:

- Requirements are Mac OSX 10.4 or higher, and a G4 processor or
higher or an Intel processor. It is compiled as universal binary
(32-bit) and tested to run on a G4 10.4 system and an Intel 10.5
system.
- It is based on revision 1685 of the trunk.
- this is an alpha version and is NOT suitable for production
environments AT ALL. Really. It contains loads of issues and bugs
which I know of but for which I need way more time to solve them. Only
reason that I make this available already is the MusikMesse, people
over there might be interested to know that a Mac version is really on
it's way.
- executable size is about 80 MB

List of known issues:
- crashes on shutdown (on my system at least), seems to be something
with the QApplication destructor failing to end properly or waiting
for some thread to yield which doesn't.
- synthesizer (playback of score) does not work or is not active yet.
- layout of some tabs in the preferences menu is still messy.
- tooltips often have the wrong length -> probably tweaking the normal
text fonts is necessary as it was for the music fonts.
- the splash screen does not display.
- svg images for some reason did not work. I'm not yet familiar with
the resources system in XCode and Mac Application Bundles, I guess the
problem is because I don't use that properly. As quick fix in this
version I converted all resources to xpm format, which does work.
- "open recent files" has some problems, could be that case
sensitiveness might be an issue here, not sure of that.
- this version I put online is not linked to portaudio. I didn't see
the use really since the synth did not work even when portaudio was
linked in.

With this list of known issues, one might wonder what does work:
- Opening, editing and saving scores. If not too fancy.
- that's about it.

I invite people to test it and let it know if anything is not right
that is not in the list that I already mentioned. Then we can compile
a workable TODO-list which can be used to work towards a future 'real'
release. For solving the problems I already mentioned, I'll probably
compile a debug version of my own in order to be able to do some
decent debugging. The software as it is now is really fragile, it's
not a release but more a partially functional 'proof-of-concept'.

Compilation options were: base SDK is 10.5, deployment target is 10.4
. In this way any 10.5-only functionality is "weak-linked" into the
project, which means that the executable will use the most recent
versions of the framework when possible but will only use
functionality which is certainly available in 10.4 already. It was
statically linked against Qt 4.5.0 and uses static linking for all the
other dependencies too at the moment.

Have fun!

Joachim

------------------------------------------------------------------------------
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer

[Thomas Bonte]

Great timing Joachim! Thanks!

[Joachim Ganseman]

Hello,

after some silence, the latest developments regarding MuseScore for Mac:

I've done some attempts in finding the cause of the crash at shutdown.
I found a 'solution' on
http://sqliteman.com/bugtracker/view.php?id=140 . As far as I
understand it, It seems that an application on mac initializes some
hidden widgets to store pointers to the OS viewport in which the
application needs to draw (a hidden qpaintdevice* called
qt_mac_safe_pdev in qapplication_mac.mm). But in mscore.cpp, in the
routine closeEvent(), all child widgets are closed manually. This
causes a crash later, since the qApplication wants to delete this
hidden widget on destruction, and thus tries to delete a pointer that
has already been deleted.

Unfortunately, when trying to remove this code, another and even
nastier crash came up: somewhere, a QIcon crashes on deletion as well,
this time the stacktrace goes all the way back to QHashTable. I
haven't yet figured out what the cause of that is, or what the
application tries to do there. Since things only got worse, for now
I've left the crash in...

I still also don't have svg files working, which is really strange
because they did work at some point when I just started my porting
efforts a few months ago. I guess this is something that popped up in
Qt 4.5.0 . Converting all resources to xpm, as I did in the alpha
version that I built a month ago, is unfortunately still necessary.

I have not tried yet to get the synthesizer working. I consider the
synthesizer functionality as less important, since the main goal of
MuseScore is to edit and display scores. Fortunately, all seems to go
well for these basic features.

Actually, I just see that Qt 4.5.1. has been released a few days ago.
I'll give it another shot while I do some administration work here - a
lot of time for compiling. But further, all ideas are welcome of
course,

Joachim

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations
Conference from O'Reilly Media. Velocity features a full day of
expert-led, hands-on workshops and two days of sessions from industry
leaders in dedicated Performance & Operations tracks. Use code vel09scf
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Mscore-developer mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mscore-developer