So all your 11 million buttons have to be clickable at any given time?
You want it all, don't you? ;-)
If you just want to change the hilite of one via script, that takes no
time (0.000627 secs on my mini to invert the hilite of btn 8888). Can
you tell us any more about the requirements without having to kill us
afterward?
Phil
Richard Gaskin wrote:
Phil Davis wrote:
on mouseUp
lock screen
lock messages
create group "test"
repeat with x = 1 to 12000
create btn ("test_" & x) in grp "test"
if x mod 100 = 0 then put x
end repeat
remove grp "test" from this cd
unlock messages
unlock screen
beep
end mouseUp
Then I did this in msg:
put the id of button 4444 of bg "test"
... which returned this:
11212
So you CAN access those objects.
Oh, I can access them alright, at least in my own tests up to a modest
11,000 buttons.
But here's the catch: how long does it take for the button to hilite
when you click on it?
Between the lag in hit testing and the loooong save times and more,
I'm using 7k objects as an upper threshold for getting work done.
--
Richard Gaskin
Fourth World
Rev training and consulting: http://www.fourthworld.com
Webzine for Rev developers: http://www.revjournal.com
revJournal blog: http://revjournal.com/blog.irv
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
