When GWT Designer parses

[pe_oliff]

the following code crashes the system because the line EHCEntry.frontendCache.userPropertyNo("OnlyShowMemberSearchCombo")
is not initialized.

Code: Select all

if (EHCEntry.frontendCache.userPropertyNo("OnlyShowMemberSearchCombo"))
      {
         final EhcLabel groupLabel = new EhcLabel("Group:");
         flexTable.setWidget(3, 0, groupLabel);
         groupLabel.setWordWrap(false);

         flexTable.setWidget(3, 1, locateMemberGroupTxt);

         final EhcLabel memberIdLabel = new EhcLabel("Member Id:");
         flexTable.setWidget(4, 0, memberIdLabel);
         memberIdLabel.setWordWrap(false);

Is there a way to test that the code is being parsed by the designer like with some sort of code like

Code: Select all

if (GWTDesigner.inCodeParser() || ... my other if statements) {
}

[Eric Clayberg]

You can use an isDesignTime() check as shown in the docs...

http://download.instantiations.com/Desi ... DesignTime

Or possibly use a code hiding tag...

http://download.instantiations.com/Desi ... rsing.html

[pe_oliff]

Thanks for your reply I found the isDesignTime() but it only works by itself in an if

Code: Select all

if (isDesignTime())

when I use it with an || (or) it will not go in the code.

Code: Select all

if (isDesignTime() || .. other test)

does not work
even this fails

Code: Select all

if (isDesignTime() || 1==1)

[Eric Clayberg]

That is correct. The parser looks for that very specific pattern. That is intentional.

Note that you can also use code hoding tags. The isDesignTime() call is primarily used to suppress design-time behavior at runtime or runtime behavior at design time.

[pe_oliff]

I pondered this for a while and figured out that the // $hide>>$ and unhiding code is what I needed.

Thanks for your support

I liked the fact that this is configurable so it allowed me to change the expression that is used for hiding and unhiding because when you run the formatter on the code it puts a space between the // and the $ so your example on the help page was useful.

So I am using

Code: Select all

      // $hide>>$
      if (userPropertyIsNo("OnlyShowMemberSearchCombo"))  // show or hide widget based on a property
      {
         // $hide<<$

                ... widgets here who's visibility are property driven ...

         // $hide>>$
      }
      // $hide<<$

[Eric Clayberg]

I liked the fact that this is configurable so it allowed me to change the expression that is used for hiding and unhiding because when you run the formatter on the code it puts a space between the // and the $ so your example on the help page was useful.

That was exactly why we made it configurable.