On Saturday, Feb 22, 2003, at 13:01 US/Pacific, Joseph J. Strout wrote:
At 11:24 AM -0800 2/22/03, Jarvis Badgley wrote:
Since this is obviously much more useful, what is the benefit to not
using composite? Why not just switch to this completely?
Apple still has a number of bugs on composite windows -- and we have a
few too. It's a completely different drawing model that requires a
lot of code changes under the hood, and even when you do all of those
according to the docs, some things don't work quite right yet (no
doubt because it's completely different under Apple's hood too). So I
would not recommend turning it on at this point unless you have a need
for it -- which most windows do not.
Are the performance issues on the RS end, the Apple end, or both?
To put it this way, I have a custom canvas based listbox that scrolls
perfectly fine in non-composite mode, but the scrollthumb lags way
behind the mouse in a composite window. I changed all of the code to
avoid using canvas.graphics. The built in listboxen seem to perform
equally well on both types of windows.
(kudos on the 'new' listbox btw, I hadn't used it since the 2drX days
and if I could get rid of the RB storage behind the listbox, I'd start
using it again for more than just testing purposes)
- michael
---
A searchable archive of this list is available at:
<http://support.realsoftware.com/listarchives/search.php>
Unsubscribe:
<mailto:realbasic-betas-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-betas-digest at lists dot realsoftware dot com>
.
|