• 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: WOConditionnal strange behavior
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOConditionnal strange behavior


  • Subject: Re: WOConditionnal strange behavior
  • From: "Jerry W. Walker" <email@hidden>
  • Date: Fri, 15 Sep 2006 18:07:47 -0400

Hi, Gilles,

I think Ken and David have pegged the source of your problem. For a more succinct explanation, go to:

http://www.wodeveloper.com/omniLists/webobjects-dev/2005/April/ msg00023.html

To really understand what's going on, pay attention to the links in that message, follow them, and read them.

Good luck.

Regards,
Jerry


On Sep 15, 2006, at 10:12 AM, Gilles MATHURIN wrote:

Sorry to disturb you, but my english is not that good, so i have some difficulties to understand your workaround …
What I typically do is have the controls affect flags/objects that are not used in conditionals.
i don't really understand what that means… may u (or anyone else who understand) give me a little more explanation please, if u have time.

Thanks you.

GM.

Le 15 sept. 06 à 09:56, Ken Anderson a écrit :

Yes.

What I typically do is have the controls affect flags/objects that are not used in conditionals. Then, in appendToResponse, I set the flags that control the conditionals from those temporary variables. This way, when the form post comes back, the page still has the original structure, but it gets 'fixed' before appendToResponse generates the new page.

Ken


On Sep 15, 2006, at 9:50 AM, Gilles MATHURIN wrote:

Hello,

this two WOConditionnals aren't in a Form, but the following WOFileUpload is. Plus, more generally, my page is composed of several forms and/or part that show and hide depending on buttons the user click, so, i think that yes the structure of the page is affected.

illustration :

=====

Button 1 when clicked, show Form1 (which is in a WOCond) and hide others (if others were showed)
Button 2 wen clicked show Form2 a (which is in a WOCond) and hide others
Button 3 when clicked show Part 3 whith a Fom all in another WOCond and hide others … etc …


=====

So i guess that this behavior is what u called "To affect the structure of the page" …

Any workaround ?

Regards

GM.

Le 15 sept. 06 à 09:38, Ken Anderson a écrit :

In my experience, weird behavior like this usually stems from the object graph of the page changing from when the page was rendered to when a form post comes back. Is this inside a form? Are you modifying any state that would affect the structure of the page?

On Sep 15, 2006, at 8:34 AM, Gilles MATHURIN wrote:

Hello List,

i have a strange behavior with my WOConditionnal, it seems to do not work as it should.
Explanation:
I have a WOCond within another WOCond. Each is bind to a different boolean.


WOCond n°1 : works great, it appears when his boolean resolves to true.
But WOCond n°2 doesn't. It is set like that :


======= Code =====

public WOComponent editPhotos()
{
// afficher le formulaire d'édition des photos et masque les formulaires au dessus
boolPhoto = true;
boolBiog = false;
boolActu = false;
// recupérer le contexte d'édition de l'artiste
EOEditingContext ec = artiste.editingContext();

// récupère l'Array (tableau) de photos de l'artiste.
NSMutableArray photosArtist = artiste.artistephotos ().mutableClone();


// Display the option to Add a new photo, if there are already ones (boolAjouterUnePhoto)
if (photosArtist.count() > 0) {
boolAjouterUnePhoto = true;
}
else { // If there aren't any existing photos, just create a new one withour displaying the Add action possibility.
boolAjouterUnePhoto = false;
ArtistePhoto newPhoto = (ArtistePhoto) EOUtilities.createAndInsertInstance(ec,"ArtistePhoto");
// Passe newPhoto à photoForm
setPhotoForm(newPhoto);

}
// afficher le formulaire d'édition des photos et masque les formulaires au dessus

return null;
}


==== End of Code ====

Any idea of why it doesn't work ?

Thanks for your support.

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


This email sent to email@hidden




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


This email sent to email@hidden


--
__ Jerry W. Walker,
WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems


    email@hidden
    203 278-4085        office



_______________________________________________
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


  • Follow-Ups:
    • Re: WOConditionnal strange behavior
      • From: "Jerry W. Walker" <email@hidden>
References: 
 >WOConditionnal strange behavior (From: Gilles MATHURIN <email@hidden>)
 >Re: WOConditionnal strange behavior (From: Ken Anderson <email@hidden>)
 >Re: WOConditionnal strange behavior (From: Gilles MATHURIN <email@hidden>)
 >Re: WOConditionnal strange behavior (From: Ken Anderson <email@hidden>)
 >Re: WOConditionnal strange behavior (From: Gilles MATHURIN <email@hidden>)

  • Prev by Date: Re: Key value coding and inner classes?
  • Next by Date: Re: WOConditionnal strange behavior
  • Previous by thread: Re: WOConditionnal strange behavior
  • Next by thread: Re: WOConditionnal strange behavior
  • Index(es):
    • Date
    • Thread