Checking on Daves #25, the Korean ENCs, the fix just works, no problem.A few other things caught my eye. Look at this: korea.PNG
Size: 85.7 KB
ID: 25475" style="margin: 2px" />
A screenshot using XP, with full screen quilting on. See all the black rendered in the ENCs. They are pylons.
Somehow they seems to dominate more than other objects.
I suppose this is Nohals territory.
Windows dimming with F6, works fine on XP. The ATI catalyst control-center crashes but that has very little impact.
I can see a need for further dimming, it is still probably to bright for night navigation.
As it is now the dimming is in steps for each time F6 is pressed and then suddenly back to full brightness. A better way, if possible, is to cycle in steps to the dimmest setting and further pressing of F6 should then lead back to increasing brightness step by step.
The chart rendering bug still exists in build 324:
Take a CM93 chart, quilting off, move the chart horizontal by the mouse (left-click pressed) any small amount to the left and the right. Regard the depth values which has been out of the screen and comes back while moving the chart back to the right.
Result as seen in the snippes and only 2 values red circled: Truncated numbers.
The same happens when scrolling the chart back and forth the right side, the upper side and the bottom side of the window.
1. start with clean 2.4.324; no navobj.xml, no opencpn.ini present
2. select CM93, zoom in to first Overzoom level - you are at (0 N, 0 W)
3. move the chart around a bit - takes a lot more time than in 2.3.1, often even looks like hanging
4. select quilting in toolbox
5. move a bit around, zooming in and out
There are too many different approaches right now. The one try a 32bit Carbon version, the next a 64bit Cocoa version, others try to use static libraries while most try to use dynamic libraries, not to speak about the different wxWidgets versions.
Common to all of them is only: They do not run as expected, crashes and have lots of bugs.
There should only be two version, Patrik's and mins should be the same. I see now i got only statis libraries fomr my wx build, the seciotns where Partik didn't write how he did it. I will rebuild my wxWidgets, thats is the same or about same version Patrik uses. Useless he changed his. We are both waiting for the 2.9.2 version to build aganist. That realase look to be the first even usable on MacOS X, recent versions.
Development have to start some ware, the starts can't be stable, I don't suggest anyone used only a Mac with OpenCPN to navigate. But given that there are still very many uses where it's usefull today, in the form it have today. With the current version i can plan my trips. I have not yet verified if the transfer of trips to my onboard Gps and plotter works. But even with out that its a great help to figure out where to go. Talking ove the mac on land is much easier that sitting both over the plotter onboard on over the paper charts. Personally I always have paper charts at reach, and the plotter running, having a MacBook showing the map in OpenCPN and the imho. I hope we have these issues sorted out when the season gets on the way here in Sweden.
And no don't expect the MacOS version to be bug free, we don't even have a the build procedure so we can build the same binaries yet. Thansk for finding out the differences in the wxWidgets. When it comes to Malcoms approach with using his own XCode project file, becase of how paths got hardcoded into that I was not able to make a build as my username and paths differ form his, he found and we all used man small bugs that make the program run at all. For the first time in ages I have hopes in thet we might make a usefull mac version soon.
The above snippes are taken with version 324 with Windows.
My bad, didn't realize how much Windows 7 looked like MacOS, I'm just allowed to used Win Xp on my work computers. I don't have any CM93 charts, so there probably is a different bug on BSB and MacOS then.
But coding have to wait, I have a boat to get ready for the seasson.