You could start another thread. We take off-topic posts here :-)
Bill Wrote:
As to whether you are nuts or not, well, that would be "off topic."
:)
Bill
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.
Chuck,
Sounds like you have a good handle on a productive approach that meets
your needs.
As to whether you are nuts or not, well, that would be "off topic."
:)
Bill
Chuck Lockwood wrote:
> Three things I'm trying to accomplish:
> 1. I do not want to have 5 different but similar forms for thi
-Original Message-
From: Bill Downall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 13, 2005 5:20 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: Disabling form fields
Chuck,
I agree with Bill C. I do the same sort of thing as you server-side,
within Witango <@IF> expressions
<@ASSIGN request$EMode VALUE="3">
>> <@ELSEIF EXPR='@@User$vUserPriv[1,M] < 45'>
>> <@ASSIGN request$EMode VALUE="4">
>> <@ELSEIF EXPR='@@User$vUserPriv[1,M] < 75'>
>> <@ASSIGN request$EMod
02 PM
To: witango-talk@witango.com
Subject: Re: Witango-Talk: Disabling form fields
I can understand having a client side calculator to help the users, and
avoid a round trip to the server for updating the totalcharge. But
nothing that's submitted can be trusted, and the Total Char
abled!
Chuck Lockwood
~~~~~~~~
LockData Technologies, Inc.
309 Main Avenue, Hawley, Pa 18428
570-226-7340 ~ Fax: 570-226-7341
[EMAIL PROTECTED] ~ www.lockdata.com
-Original Message-
From: Willochell, Mike [mailto:[EMAIL PRO
~
LockData Technologies, Inc.
309 Main Avenue, Hawley, Pa 18428
570-226-7340 ~ Fax: 570-226-7341
[EMAIL PROTECTED] ~ www.lockdata.com
-Original Message-
From: Willochell, Mike
onchange="return false;" works nicely in conjunction with
onfocus="blur()" but some browsers that try to protect users from
malicious javascript err on the side of safety and these dont work
like you would hope (firefox is an example of that)
a fool proof thing you could do is put it in as a hidde
What we do is something like this (let's presume text fields for this example)Based on access levels/functionAccessible field: Inaccessible field: data string Works like a charmI am not sure, however, that this addresses what you are attempting to achieve. However, hidden fields can wor
Title: Re: Witango-Talk: Disabling form fields
I agree then it is just a case of using the <@IF> and displaying a different type of field depending on criteria.
Would you be disabling the whole form or just certain fields.
If it is just certain fields remember you will have to subm
Chuck,
Try READONLY=TRUE.
Mike
From: Chuck Lockwood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 12, 2005 7:58 PM
To: WiTango-Talk
Subject: Witango-Talk: Disabling form fields
What is the easiest, safest, most reliable way to disable editing of
how, 'bout using the user priviledge to determine whether it is a form field or just a presentation of the content of the field. If you use _javascript_ then you can be run around pretty easily.On Jul 12, 2005, at 4:57 PM, Chuck Lockwood wrote:What is the easiest, safest, most reliable way to disab
What is the easiest, safest, most reliable way to disable editing
of selected form fields based on privilege levels or other criteria.
I have used in the past, but was hoping to
use disabled=true now. I find it displays the fields grayed out which is
great, but doesn’t include them as
13 matches
Mail list logo
