fargo@rpgportland.com wrote:
calculations tend to be based off incorrect information. Specifically the
window will have returned to its smaller size, in this case 469 wide, but
the 3d space still reports 1280 at the time of my method call.
Yeah, the Rb3DSpace probably has to be updated before it will realize
that it's been resized.
Anyone know of a good way to get around this lag? I tried running this
loop before my position update method-
if me.FullScreen then
me.FullScreen = False
while myspace.width <> me.width
wend
Hah, good try, but no, it's not a time lag here; it's an
event-processing thing. Try myspace.Update. If that doesn't work, then
you'll have to simply start a single-fire timer whose Action event calls
MoveLabels. Even a period of 1 would probably suffice, since the point
is just to let the event loop finish doing its work.
Best,
- Joe
--
Joe Strout
Inspiring Applications, Inc.
http://www.InspiringApps.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|