bug

Dan Shafer revdan at danshafer.com
Sat Jun 4 20:06:25 EDT 2005


As others have said, you lost the table because it was selected and  
the select arrow was active when you hit the backspace key.

I've long though Rev needed a preference setting to prevent this sort  
of accidental deletion, which can be fairly catastrophic. My testing  
in 2.5.1 on OS X 10.4 with your scenario reveals a couple of things.

First, if the properties inspector is open and selected, pressing the  
delete key does not have any effect at all. The field, though it is  
selected, is not deleted. If, OTOH, I select the window in which the  
field appears and then hit the backspace key, the field is in fact  
deleted, but -- and this surprised me and contradicts what others  
have said here -- Undo did not bring the field back to life.

None of the fields is salvaged from an unintentional delete via  
backspace or delete key by an undo operation, though all other object  
types from the palette behave exactly as expected (i.e., undo  
restores them from accidental deletion).

SO while it seems like there was user error involved here (I don't  
believe in user error, by the way), this clear bug at least possibly  
prevented you from recovering cleanly.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Shafer, Co-Chair
RevConWest '05
June 17-18, 2005, Monterey, California
http://www.altuit.com/webs/altuit/RevConWest

On Jun 4, 2005, at 5:28 AM, Jon wrote:

> I was editing the custom properties of a table.  I wanted to delete  
> the most recently entered custom property, so I pressed the <del>  
> key.  The TABLE was deleted, not the property; and UNDO did not  
> bring the table back.
>
> :(
>
> Jon
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>



More information about the use-livecode mailing list