215_3391 - Watch out for.

[peteconway]

This build has changed the way client side true/false work - do not update your sever with making the change if you use these conditions - it will fail, I'm also getting an error with div's fom a dynamic image or link, work fine if an ajax window but fails as a div. - remember test first.

[Steve Wood]

Re: 215_3391 - Watch out for.

I'm runnign that update, does that mean a Client Side Show/Hide expression would fail? Such as:

if(alltrim(Id) ="",false,true)

Its giving a javascript error dialog and also not working.

[fsi]

Re: 215_3391 - Watch out for.

For whatever reason, my show/hides began behaving properly and consistently (consistency had been a problem) with this patch.

After reading the release notes, my interpretation was that overall syntax had changed.

You might try this, Steve:

alltrim(Id) <> ""

as my expression in my own app, entered as "FieldVar > 0" (sans quotes), results in perfect show/hide rendering.

[Peter.Greulich]

Re: 215_3391 - Watch out for.

if(alltrim(Id) ="",false,true)

I believe that is the correct syntax.

But:

if(alltrim(Id) ="",False,True)

would fail.

[Steve Wood]

Re: 215_3391 - Watch out for.

I think part of my answer is a misconception on my part. I was using the Show/Hide in a Detail view, so only viewing one record at a time. But the Show / Hide options are for COLUMNS, i.e. it affects that field for every row in the grid. So whatever rule you apply, will apply to all rows, even the detail views. So as I tested, I was testing a Detail View record at a time.

I wanted to control the show / hide for a button to make the button NOT appear for new records. Hence, if ID is blank, its a new record, since ID was an autoincrement value on the table. Apparently that isn't going to work -- it isn't going to hide it for one Detail view, but show it for another records Detail view.

Maybe I can figure it out using Calculated Fields or Custom Fields, since those are evaluated on the server.

[Peter.Greulich]

Re: 215_3391 - Watch out for.

-- it isn't going to hide it for one Detail view, but show it for another records Detail view.
.

Not sure I follow. You can hide a button if the ID field is blank. I do.

See image...

[peteconway]

Re: 215_3391 - Watch out for.

I think the syntax of the conditions will get fixed once things stop working as expected. I get mixed results. On the DIV issue I have just comfirmed if you make any change to a dynamic image special control that has Java onclick to use a DIV in a grid it will stop working from that time on - the only way to get it going again is to set it to a popup - so take care with this.

[Steve Wood]

Re: 215_3391 - Watch out for.

PeterG - OK, got it to work, sort of.

Plain old: Name<>"" worked.

Not out of the woods yet - although my button properly show/hides. The Javascript under the button has this expression: upload.a5w?id={id}. The ID is an autoincrement field in the table. Unfortunately, even though I have saved the Detail record, it has not come back and populated my ID field in the Detail record, even though it has been written to the table. So my ID is still blank when the user clicks the button, so my parameter is blank and the xbasic in the popup fails.

But I'll probably figure it out. I can tell the page needs to be refreshed. It does not seem to help to choose a special value for teh "Row refresh method after edits" or other property settings. The only way I can get it to work is to click the Save icon twice. It populates the ID field on the second press.

[Peter.Greulich]

Re: 215_3391 - Watch out for.

The ID is an autoincrement field in the table. Unfortunately, even though I have saved the Detail record, it has not come back and populated my ID field in the Detail record, even though it has been written to the table. So my ID is still blank when the user clicks the button, so my parameter is blank and the xbasic in the popup fails.
...
The only way I can get it to work is to click the Save icon twice. It populates the ID field on the second press.

I see the problem.
Let us know if you figure a work around.

[Steve Wood]

Re: 215_3391 - Watch out for.

I think a lot of this is getting used to the new features, especially the client-side aspect.

[peteconway]

Re: 215_3391 - Watch out for.

Steve, control the button using the Client Side Grid System Events.

Under Properties>Java Script>System Events.


Here are some examples I use to have pages like Google map and web pages appear by having Java click the (hidden) button.

$('{Grid.componentname}.V.R1._UNBOUND_BUTTON_1').click();
$('{Grid.componentname}.V.R1._UNBOUND_BUTTON_2').click();
$('{Grid.componentname}.V.R1._UNBOUND_DYNAMICIMAGE_4').click();
$('{Grid.componentname}.V.R1._UNBOUND_BUTTON_3').click();

I use them after grid submit & after pagenavigate.

You can find the value of your button using Firefox>FireBug.

Hope this helps.

These are very powerful control not yet fully explained to people.

[peteconway]

Re: 215_3391 - Watch out for.

The DIV issue has been resolved and will be in the next build.