Mac Performance Update

[CarinaPDX]

I'll test it. You can post or PM me how to get DMG.


Greg

[CarCode]

Using the latest wxWidgets 2.9.5 build you will see such messages in the OCPN log:
Warning: iCCP: known incorrect sRGB profile

That is because wx uses also a new libpng version now with better checks for *.png files. To fix that, first download and install srgb-icc profiles e.g. from sRGB profiles

Then convert all images of the OCPN sources to higher standards:
for x in *png; do convert $x -profile sRGB_v4_ICC_preference.icc $x; done

Gerhard

[Icnoships]

Dave
just did a compile of 705, i already have wx 2.9.4 installed on this machine so compiled it against that.
Didn't make an Xcode project just used - "$cmake -DCMAKE_OSX_64=ON -DPREFIX=/Users/mo/tmp .."

Compiled with no errors but plenty warnings.

Then went the whole hog an created dmg, first time I've managed that !

can confirm same good speed performance when O is in action.

Nothing untoward in O's log except - "13:43:17 EST: Error: File '/Users/mo/Library/Preferences/navobj.xml.changes' couldn't be removed (error 2: No such file or directory)"

strangely as a bonus all text in the Options windows are back to normal size.

good stuff

mo

[CarCode]

Originally Posted by Icnoships

Nothing untoward in O's log except - "13:43:17 EST: Error: File '/Users/mo/Library/Preferences/navobj.xml.changes' couldn't be removed (error 2: No such file or directory)"
mo

There is a missing file check in the OCPN code, something like this:

if( ::wxFileExists( m_sNavObjSetChangesFile ) ) <-- This line is missing
wxRemoveFile( m_sNavObjSetChangesFile );

Gerhard

[bdbcat]

Hello Mac testers....

Here is another quick check of our build process.

https://www.dropbox.com/s/c5ainewgut...PN_3.3.710.dmg

Here is the build spec:

Built on Lion 10.7
Target minimum system and SDK linkage is 10.6 (Snow Leopard)
wxWidgets version is 2.9.4(Cocoa)

We have two questions: (Tight focus, please...)

1. Does it run on Snow Leopard? (Hint: it does on my SL system.)

2. On SL, Lion and Mountain Lion, is the performance roughly the same as 3.3.705 (i.e. the latest Mac test, which is significantly faster than 3.2.2)? (Hint: it is on my Lion system)

For those interested, it turns out that wxWidgets 2.9.5 will not load on Snow Leopard, probably due to a system function call, missing in Snow Leopard, which was inadvertently added to wxWidgets sometime after 2.9.4 was released. 2.9.5 has some improvements, none of which are really important to us since we no longer depend on the native wxRegion class in the Mac build. We can live with 2.9.4 (Cocoa).

If we get affirmative answers to the two questions, then this will be our next build target environment for Mac.

Thanks
Dave

[CarinaPDX]

Hi Dave-

I just downloaded and installed on Snow Leopard, 10.6.8. It seems to work just fine, with ENC, RNC, and CM93 charts, GPS attached. I didn't have 3.3.705 installed so I can't compare, but I can attest that it is noticeably faster than earlier versions. Actually, a lot faster. Good work. (2006 MBP C2D 2.33GHz)

One point: I didn't know what "Chart Information Objects" was (vector chart tab) so I gave it a try. It hammered both cores and pegged the cooling fans with the spinning beach ball, but did end after a minute or two. Then the chart was covered with horizontal red ovals with "U" inside. Unchecked and back to normal. 'Not sure what that was about.

Greg

[Icnoships]

Dave
just tested 710 on OS 10.7.5 and all appears to be the same ..no noticeable difference in performance to 705. All good.

Dont Have snow leo so cant comment.

regards

mo

[Capt Rottnest]

On my MacbookPro (2.6GHz C2D) with Mountain Lion this version 3.3.710 runs just as quick as 3.3.705. Tens times faster that 3.2.2
It doesn't crash, but the inability to draw new routes that remain uncorrupted is still there.

[CarCode]

I found another bug:
Menu IDs must be 16 bits. So this enum in chart1.cpp is wrong:

enum {
ID_PIANO_DISABLE_QUILT_CHART = 50000, ID_PIANO_ENABLE_QUILT_CHART
};

int16 have a range = -32,768 to 32,767

Gerhard

[nohal]

Gerhard...
Where is it declared as int16, please? It's a wxWindowIdRef I would say.

Pavel

[bdbcat]

Capt Rottnest...

Gary, I cannot reproduce any problem with route point scrambling on 3.3.710.

Lets try a simple test:

1. Run O, and delete all routes. Close and restart.
2. Make a simple 5 point route, as you showed in earlier post. Close OCPN.
3. Upload to this thread a copy of /Users/{name}/Library/Preferences/navobj.xml.

4. Run O again, and confirm that the simple route is scrambled.

5. Show the Route Properties dialog for the route, and take a screen shot, post it here.

It looks to me as though some of the waypoints in the route are being set to lat/lon = 0,0. Is this the case?

Thanks
Dave

[CarCode]

Originally Posted by nohal

Gerhard...
Where is it declared as int16, please? It's a wxWindowIdRef I would say.

Pavel

Pavel,
you always don't understand my english I guess. When I write Menu IDs I mean Menu IDs and not Window IDs.

Look at wxMenuItemBase() in /common/menucmn.cpp
You will see:

// ids are limited to 16 bits under MSW so portable code shouldn't
// use ids outside of this range (negative ids generated by wx are
// fine though)
wxASSERT_MSG( (itemid >= 0 && itemid < SHRT_MAX) ||
(itemid >= wxID_AUTO_LOWEST && itemid <= wxID_AUTO_HIGHEST),
wxS("invalid itemid value") );

Gerhard

[nohal]

Gerhard...
I understand your English very well... I just did not understand the int16 thing when it's not used in the WX code a single time except in the embedded libtiff library. If you post the real cause of the porblem right away next time, I will certainly not ask.

Pavel

[CarCode]

Pavel,
your questions are annoying. I never talk about libtiff library nor wxWindow IDs but Menu IDs.
Please stop your questions and read instead...
Thank you.

Gerhard

[nohal]

Gerhard...
As you sure have seen during your endaevour through the code of both OpenCPN and WX, the WX menu ID is a WindowID and it is an integer (normal integer, 4 bytes). If you find an assertion like this, please save us the lecture about 16bit integers and post what you posted in #42 next time, please, really.
Note that this is not a question, this is an appeal on what I hope is sanity.

Thank you for thinking about what I wrote, and I mean it

Pavel