Jerome Vernet (Orange) wrote:
> Hi,
>
> Some things to see about wxWidget performances on macOsX, from reading
> on the web:
> - disabling CORE in wxWidget build is a very bad idea, at least on Tiger.
>
Hi Jerome,
Thank you for helping out. I appreciate your patience.
The problem with enabling Core Graphics instead of Quicktime is that it will try to double-anti-alias the images making them look very ugly - you'll get vertical stripes, and it also seems to slow the blits down even more. :-(
Today I've coded up a version that directly does blits to the display, perhaps it's faster, perhaps it isn't. I'm still debugging it so that it works right before I test the speed. I suspect it will be faster for minor changes such as the mouse cursor moving around the screen, but slower for things such as a whole desktop repaint.
I'm also using wx2.8.3 on PPC now to see if that fixes any of the issues.... The big difference is that you'll see the Lisa draw objects, and perhaps stop in the middle, then update. i.e. if it draws a square box, you might first see a portion of the box, then some milliseconds later, the rest of it.
I really should get a book on XCode and Cocoa and rewrite the display directly. This is annoying me to no end. The whole point of wxWidgets is that the code should be exactly the same across platforms, instead it's behaving very differently. Between windows and linux it seems to be fine, I've noticed very little problems. But not on OS X. It's not OS X's fault, that's for sure as every application I use just flies.
On your notebook for example, if I ask it what the size of your screen is, it returns garbage. Like -5,39847329847329. On other platforms it works..
I also found that the saved screen size grows with each run of LisaEm on OS X which is what you saw with the window being larger than your screen. The information that GetSize returns is different from SetClientSize, this is a bug on my part.
> - it seams that drawing ouside some bound (windows ? Bitmaps ?) is also
> a very bad thing. As I have problems with windows size, it may be the point.
> - wxMac do not need, as for windows or linux to force refresh (I do not
> know wich refresh)
>
From what the wx guys told me is that if I use the OnPaint event to draw the screen, it's fine to not care about the bounds because it knows which areas were dirty/updated and therefore, it will only update what it needs. Perhaps that's not quite right on OS X since it's double buffered. Received on 2007-04-06 17:55:19
This archive was generated by hypermail 2.4.0 : 2020-01-13 12:15:14 EST