Capellan wrote: > Visit report 8251 to vote for disable image copy from > password protected stacks. > > http://quality.runrev.com/qacenter/show_bug.cgi?id=8251 > > To copy an image from a password protected stack, > users just had to select the image and write > in the message box: > set the clipboarddata to the text of the selobj > > Then, to paste the image in a new stack, > users create a new empty image object and > type in the message box: > set the text of the selobj to the clipboarddata > > Using this method, i was able to copy gif animations > from a password protected stack.
This is the way it has always been. The only thing protected is the scripts. Things like images, properties and custom properties are not. Given that: 1. You can encrypt and decrypt the custom properties and images of a protected stack from within the protected code of the stack itself. 2. Having these elements unprotected allows for updating the protected stack without having to unlock and relock it and therefore can be done on a user's machine. 3. In the case of a library stack, the stack can use itself for storage and be saved. I don't see what you are requesting as an advantage or desirable. Aloha from Hawaii, Jim Bufalini _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
