Read-Only Input Fields

On Feb 7, 2008, at 12:46 PM, Roberto Fonseca wrote:

> Hello everyone,
>
> Just a quick question here: I have input fields throughout the  
> application that we migrated from VW v.3 to v.7.5 that are read-only  
> but I can still select/copy the fields contents. (This is not the  
> same behavior found in the original application). Is there any way  
> of making the read-only fields contents un-selectable?

The ability select and copy text (but still not edit it) was added  
somewhere between those two releases. I *think* you can still put a  
ReadOnlyController on the widget and have the old behavior. Or a  
NoController.

--
Travis Griggs
Objologist
"Every institution finally perishes by an excess of its own first  
principle." - Lord Acton

Thanks for the info, Travis. I'll let the users know that this is a new feature introduced to Smalltalk after v3.x. I believe they will be OK with that.

Roberto

-----Original Message-----
From: Travis Griggs [mailto:[hidden email]]
Sent: Thursday, February 07, 2008 8:05 PM
To: ([hidden email])
Subject: Re: Read-Only Input Fields


On Feb 7, 2008, at 12:46 PM, Roberto Fonseca wrote:

> Hello everyone,
>
> Just a quick question here: I have input fields throughout the
> application that we migrated from VW v.3 to v.7.5 that are read-only
> but I can still select/copy the fields contents. (This is not the
> same behavior found in the original application). Is there any way
> of making the read-only fields contents un-selectable?

The ability select and copy text (but still not edit it) was added
somewhere between those two releases. I *think* you can still put a
ReadOnlyController on the widget and have the old behavior. Or a
NoController.

--
Travis Griggs
Objologist
"Every institution finally perishes by an excess of its own first
principle." - Lord Acton

Roberto,

You can mark the input field as disabled. It will have a greyed out look
and will not respond to user input, but will display programmatic
updates to the model.

Dave

Roberto Fonseca wrote:

Thanks for the suggestion, Dave. I'll see if the users would prefer to go that route. Even though I personally think the current behavior is how it should be.

Roberto

-----Original Message-----
From: Dave Stevenson [mailto:[hidden email]]
Sent: Friday, February 08, 2008 2:32 PM
To: Roberto Fonseca
Cc: ([hidden email])
Subject: Re: Read-Only Input Fields

Roberto,

You can mark the input field as disabled. It will have a greyed out look
and will not respond to user input, but will display programmatic
updates to the model.

Dave

Roberto Fonseca wrote:

You can also add validation code on entry and return false .. that should
prevent clicking in the field.

Roberto Fonseca wrote:

Thanks for the suggestion, Dave. I'll see if the users would prefer to go that route. Even though I personally think the current behavior is how it should be.

Roberto

-----Original Message-----
From: Dave Stevenson [[hidden email]]
Sent: Friday, February 08, 2008 2:32 PM
To: Roberto Fonseca
Cc: ([hidden email])
Subject: Re: Read-Only Input Fields

Roberto,

You can mark the input field as disabled. It will have a greyed out look
and will not respond to user input, but will display programmatic
updates to the model.

Dave

Roberto Fonseca wrote:
  

Hello everyone,



Just a quick question here: I have input fields throughout the
application that we migrated from VW v.3 to v.7.5 that are read-only
but I can still select/copy the fields contents. (This is not the same
behavior found in the original application). Is there any way of
making the read-only fields contents un-selectable?



TIA,


Roberto

    

-- 
Dennis Smith                 		         +1 416.798.7948
Cherniak Software Development Corporation   Fax: +1 416.798.0948
509-2001 Sheppard Avenue East        [hidden email]
Toronto, ON M2J 4Z8              [hidden email]
Canada			         http://www.CherniakSoftware.com
Entrance off Yorkland Blvd south of Sheppard Ave east of the DVP