[REBOL] Re: problems with RATE ( what do you think Carl )
From: petr:krenzelok:trz:cz at: 10-Jan-2003 8:31
Anton wrote:
>Hi Oldes,
>
> either f/user-data < 5 [
> f/user-data: f/user-data + 1
> f/image: pick imgs-water-explosion f/user-data
> ][
> rate: none
> ]
>
>Shouldn't that be:
>
> f/rate: none
>
>?
>
I am not sure. Maybe it is exactly the same case as Cyphre described
almost two years ago. He wanted to have faces displayed, but events
freezed. Here's the excerpt of Cyphre's and Holger's message exchange:
---- Cyphre explains:-------
We need command which might be derived from 'hide. For example 'freeze.
This
command will behave simmilar like 'hide but without feature to hide face(s)
i.e. when you "freeze my-face" all subfaces of my-face will recursively stop
receiving of time events but will remain shown on the screen. Command with
reversed behavior would be 'unfreeze or something like that.
I know, we can recursively search the whole face-tree and
set rate to 0 or so(this would be sloow when searching more complex faces)
but why not use the part of code from 'hide command and make similar one for
example 'freeze.
Maybe this could be solved differently when creating/changing of events
will
be implemented. Then we could for example filter all time events containing
destination my-face using own functions inserted on the top of the event
tree...for example: func [face event][if all [event/type = 'time event/dest
= my-face] [return none] return event]
-------------------
What Holger replied:
Cyphre: For removing timeouts without hiding a face ? The solution is
probably something like "face/changes: 'timeout show face" in the next
version. We are already using face/changes in some other places to limit
the work show has to do, and to avoid flickering. Seems like a natural
addition.
-------------------
Of course I am not sure Oldes refers to the same problem ...
-pekr-
