If the appearance of disabled fields is not a problem for you, you
could also group the fields and disable the group when a user should
not be able to edit, or enable the group when they can:
set the enabled of group "Field Set" to <true if this user may edit>
or
if <this user may edit> then enable group "Field Set"
else disable group "Field Set"
On Sep 6, 2004, at 11:24 PM, Sarah Reichelt wrote:
On 6 Sep 2004, at 2:57 pm, Sannyasin Sivakatirswami wrote:
I want to be able to "lock up" a stack such that the user cannot
select text in fields, but all the buttons run.. then, when he clicks
"edit" the application drops a "in use" semaphore file on the server
so that others can read the stack from the server but not make
changes... and the user with edit privileges can now edit text and
when he saves, the changes are saved to a temp stack on disk and the
app FTP's the changed stack back to the server and delete the
semaphore file.
How about a large transparent button that covers all the fields. Your
actual buttons could be on top of this transparent button so they are
clickable, but by toggling the visibility of the big transparent
button, you could toggle the ability to type or select any field data.
Cheers,
Sarah
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
-----------------------------------------------------------
Frank D. Engel, Jr. <[EMAIL PROTECTED]>
___________________________________________________________
$0 Web Hosting with up to 120MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at www.doteasy.com
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution
