Jim Ault wrote:
Couldn't you create a substack "undo" and set a series of custom properties
to the mainStack as a binary+save this stack. In the beginning of stack
development, this would be small overhead and the undo series could be
purged when not needed any more.
Added benefit is that the
On 2/19/07 10:49 AM, "J. Landman Gay" <[EMAIL PROTECTED]> wrote:
> But for a product like Rev, where the current state could be
> almost anything, it would be much harder. We'd need an engine change, I
> think, and I like Richard's idea of having a property we could read that
> would return the cu
Malte Brill wrote:
> Malte, what did you do for drops, where you have 5 undos?
I did something I would not do again. :-)
I am cloning the playgrid and copy it to an undo card. If there are more
than 5 groups on that card I delete the one with the lowest layer. when
undoing I copy the one with
> Malte, what did you do for drops, where you have 5 undos?
I did something I would not do again. :-)
I am cloning the playgrid and copy it to an undo card. If there are
more than 5 groups on that card I delete the one with the lowest
layer. when undoing I copy the one with the highest layer
Richard,
Thanks for all these details. The state approach is something I am
keen on investigating as well. I know that Andre in a previous
discussion had discussed the idea of storing and restoring states.
Was this solution implemented or were there only ideas being discussed?
Malte, what
J. Landman Gay wrote:
Ben Fisher wrote:
Create a new stack. Create two buttons.
Delete one of the buttons. Go Edit->Undo, and nothing happens. Imagine
if this button had all the scripts for your application. This is a
problem.
I didn't follow your recipe exactly, but I had a stack already made
Ben Fisher wrote:
Create a new stack. Create two buttons.
Delete one of the buttons. Go Edit->Undo, and nothing happens. Imagine
if this button had all the scripts for your application. This is a
problem.
I didn't follow your recipe exactly, but I had a stack already made and
opened. I deleted
Ben Fisher wrote:
In the script editor: there is no good reason. I have written undo for
small scale text editors, simply by remembering the last 10 states. It
is not like this is storing images in memory or something.
Thanks for the background info. At least we can spare the longer part
of
Ben Fisher wrote:
In the Script Editor as well as in the form designer (for lack of a
better term).
In fact, while designing forms, even basic Undo itself does not seem
to work. I'm using beta 2.8. Create a new stack. Create two buttons.
Delete one of the buttons. Go Edit->Undo, and nothing happe
As far as the form designer goes: I understand that this is not
trivial. I assume that your point is that anything done from, say the
message box, would be hard to keep track of and undo. True.
It would be reasonable if basic IDE actions could be undone. Other
form designers can accomplish this.
(
Ben Fisher wrote:
In the Script Editor as well as in the form designer (for lack of a
better term).
In fact, while designing forms, even basic Undo itself does not seem
to work. I'm using beta 2.8. Create a new stack. Create two buttons.
Delete one of the buttons. Go Edit->Undo, and nothing happ
In the Script Editor as well as in the form designer (for lack of a
better term).
In fact, while designing forms, even basic Undo itself does not seem
to work. I'm using beta 2.8. Create a new stack. Create two buttons.
Delete one of the buttons. Go Edit->Undo, and nothing happens. Imagine
if thi
Ben Fisher wrote:
Will Revolution ever support multiple undo/redo?
Are you wanting this just for the Script Editor, or are you looking for
an API to implement multiple-Undo in your own apps?
--
Richard Gaskin Managing Editor, revJournal
_
Will Revolution ever support multiple undo/redo?
This seems like a pretty basic thing to have for a mature product. I
cannot imagine why it is missing, even in the script editor.
I think this has gone beyond the point where it is that would be
something nice to have. Lacking multiple undo/redo i
14 matches
Mail list logo
