"movestack" sent continuously!

[Klaus Major]

Hi all,

looks like something has changed (again and silently) in 2.9?

 From the docs:
...
The moveStack message is sent after(!) the movement is finished.
...

But on OS X it is apparently being sent continuously!
Can someone confirm this?

Simply create a new stack and put this into the stackscript:

on movestack
   put the loc of this stack
end movestack

And you will probably see the loc being updated in realtime in the msg.

Not a big thing, although we have an "activity logging" (including  
"movestack")
in our current project and this way the log is being written to disk  
quite often
and unecessarily.

This has been working as the docs state in earlier versions
I do not like this surprises, at least not in Rev :-)


Best

Klaus Major
klaus@...
http://www.major-k.de


_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

[Mark Schonewille-3]

Hi Klaus,

This has been changed in Rev 2.9, to make Mac OS X consistent with  
Windows. The docs are wrong.

Best,

Mark

--

Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz

Get your store on-line within minutes with Salery Web Store software.  
Download at http://www.salery.biz

Op 15-mei-2008, om 11:03 heeft Klaus Major het volgende geschreven:

> Hi all,
>
> looks like something has changed (again and silently) in 2.9?
>
> From the docs:
> ...
> The moveStack message is sent after(!) the movement is finished.
> ...
>
> But on OS X it is apparently being sent continuously!
> Can someone confirm this?
>
> Simply create a new stack and put this into the stackscript:
>
> on movestack
>   put the loc of this stack
> end movestack
>
> And you will probably see the loc being updated in realtime in the  
> msg.
>
> Not a big thing, although we have an "activity logging" (including  
> "movestack")
> in our current project and this way the log is being written to  
> disk quite often
> and unecessarily.
>
> This has been working as the docs state in earlier versions
> I do not like this surprises, at least not in Rev :-)
>
>
> Best
>
> Klaus Major
> klaus@...
> http://www.major-k.de
>

_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

[Klaus Major]

Dag Mark,

thanks for testing!

> Hi Klaus,
>
> This has been changed in Rev 2.9, to make Mac OS X consistent with  
> Windows. The docs are wrong.

And fragmentary!

Did not know that this had been working this way on windows before.

> Best,
>
> Mark
> --
> Economy-x-Talk
> Consultancy and Software Engineering
> http://economy-x-talk.com
> http://www.salery.biz

Regards

Klaus Major
klaus@...
http://www.major-k.de


_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

[Ken Ray]

>> This has been changed in Rev 2.9, to make Mac OS X consistent with
>> Windows. The docs are wrong.
>
> And fragmentary!
>
> Did not know that this had been working this way on windows before.

Actually there's a similar situation with resizeStack - in the earlier days
of Rev/MetaCard, resizeStack was sent continuously on Windows/Linux, but not
on Mac. Now, in order to get continual resizeStack messages on OS X, you
need to set the "liveResizing" of the stack to true.

Along these lines, I think it might be good to have liveResizing default to
"true" for new stacks instead of "false" - otherwise it makes resizing look
"old" on OS X. In fact the IDE itself doesn't even default to
liveResizing=true. This hasn't been filed as a bug report AFAIK.

Opinions?

Ken Ray
Sons of Thunder Software, Inc.
Email: kray@...
Web Site: http://www.sonsothunder.com/


_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

[Sarah Reichelt-2]

>  Actually there's a similar situation with resizeStack - in the earlier days
>  of Rev/MetaCard, resizeStack was sent continuously on Windows/Linux, but not
>  on Mac. Now, in order to get continual resizeStack messages on OS X, you
>  need to set the "liveResizing" of the stack to true.
>
>  Along these lines, I think it might be good to have liveResizing default to
>  "true" for new stacks instead of "false" - otherwise it makes resizing look
>  "old" on OS X. In fact the IDE itself doesn't even default to
>  liveResizing=true. This hasn't been filed as a bug report AFAIK.

I agree that the IDE should have live-resizing, but not that
live-resizing should be on by default. I always roll my own resizing
handlers as I don't trust the Geometry manager. When testing, it is
much better to have live-resizing off, so if I have made a mistake,
there is only one resizeStack message sent, not hundreds. Once I know
I have it right, then I turn on live-resizing.

I guess my preferred option would be to have the standalone builder
turn on live-resizing for every resizable stack.

Sarah
_______________________________________________
use-revolution mailing list
use-revolution@...
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution