• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOTextField looses value when disabled has been unset
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOTextField looses value when disabled has been unset


  • Subject: Re: WOTextField looses value when disabled has been unset
  • From: Chuck Hill <email@hidden>
  • Date: Thu, 9 Dec 2010 11:48:53 -0800

On Dec 9, 2010, at 10:48 AM, René Bock wrote:

> Hi all,
>
> I just ran into a curious problem (WO 5.4.3, Current Wonder)
>
>
> In a Form, I have a WOTextfield
>
> aText : WOTextField {
>   value = aValue;
>   disabled = application.viewOnly;
>   WODebug=true;
> }
>
>
> After a request/response cycle (1), there is
>
>
> Dez 09 19:16:18 HelloText[52423] DEBUG NSLog  - Main ==> aText:WOTextField { disabled=application.viewOnly; } value false
> Dez 09 19:16:18 HelloText[52423] DEBUG NSLog  - Main <== aText:WOTextField { value=aValue; } value "foo"
> Dez 09 19:16:18 HelloText[52423] DEBUG NSLog  - Main ==> aText:WOTextField { disabled=application.viewOnly; } value true
> Dez 09 19:16:18 HelloText[52423] DEBUG NSLog  - Main ==> aText:WOTextField { value=aValue; } value "foo"
>
> 	application.viewOnly = true
> and
>  	aValue = "foo"
>
>
> Now, application.viewOnly will be set to false (e.g by an other thread) before the next request/response cycle.
>
>
> After the next request/response cycle (2) (caused by a do noting submitAction) there is
>
>
>
> Dez 09 19:17:49 HelloText[52423] DEBUG NSLog  - Main ==> aText:WOTextField { disabled=application.viewOnly; } value false
> Dez 09 19:17:49 HelloText[52423] DEBUG NSLog  - Main <== aText:WOTextField { value=aValue; } value null
> Dez 09 19:17:49 HelloText[52423] DEBUG NSLog  - Main ==> aText:WOTextField { disabled=application.viewOnly; } value false
> Dez 09 19:17:49 HelloText[52423] DEBUG NSLog  - Main ==> aText:WOTextField { value=aValue; } value null
>
> 	application.viewOnly = false
> and
>  	aValue = null
>
>
>
> Has anybody noticed this before?

Yes.


> Is there workaround?

Not an easy one.  I try to view the R-R cycle as appendToResponse - takeValues - invoke action.  The best course of action is to not allow things like disabled to change during this chain of events.  That often means looking at and caching the value at the start of appendToResponse.


Chuck


--
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects







Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >WOTextField looses value when disabled has been unset (From: RenĂ© Bock <email@hidden>)

  • Prev by Date: Re: OT: Which computing language is fastest?
  • Next by Date: RE: WOBrowser selections missing
  • Previous by thread: WOTextField looses value when disabled has been unset
  • Next by thread: Ant woapplication not building as expected
  • Index(es):
    • Date
    • Thread