Select button issue

[kingja]

Bruce,

     In a NT 8.23 app I have a browse with the select button set.  When I call it from a menu, the select button is correctly hidden.  When I next call it from a look up button, the select button is correctly displayed.  Now, with all subsequent calls to the same browse from a menu, it retains the select button.
     I have tried using the loc:act variable and the condition on the select button, but so far have had no success.  How can I get the Select button to only display when the browse is used as a lookup?

Thanks,

Jeff

[kingja]

Bruce,

     I continue to struggle with this.  The condition field in the templates seems to apply only to an in-line select button, not the Select button under the update buttons.  So, once I use the browse as a lookup, it seems to stay in lookup mode.  I have tried setting loc:Selecting = 0 in various places but have not had any success.  Can you help?

Jeff

[Bruce]

Hi Jeff,

example 3 has a browse (mailboxes) that is called from the menu, and also as a lookup from the aliasForm.

In that example I'm not seeing the problem you are having though. Perhaps take a look at the example and see if you can tweak it to generate the effect you are seeing. Perhaps it's related to page / popup mode or perhaps your oblique mention of a Select condition is the key.

If you can tweak the example and post that here, that would be great. (please include app, dict, and data files with any example posted.)

cheers
Bruce

[kingja]

Bruce,

     I was able to duplicate the effect in the example app, which I attached.  My only change was to add a new menu item called "Jeff Menu"  It calls the Mailbox browse.  Here are the steps to follow:

1.  Log in
2.  In the Jeff Menu, click on the browse mailbox item.
3.  Note there is no select button.
4.  Go to Alias, click Insert, do a lookup (click the look up button), click select.
5.  Click on home.
6.  Once again, click on the Jeff Menu item to call the mailbox browse.  Now you will see it has a select button.

     This issue only happens when the mailbox browse is called as a procedure, pop up.  Calling as a URL or procedure without pop up has the expected select button behavior.

[attachment deleted by admin]

[Bruce]

Hi Jeff,

ok, this is gonna be a bit complicated to explain, so pay attention;

The simple answer is that you have a "mix" of a popup and a page - where the same component is both on the page and on the popup.

In this case the page http://127.0.0.1:88/MailboxesBrowseControl contains 2 copies of the browse - one that you can see and one waiting to popup (from your menu item.)

In short - you can have popups from your menu, but then you can't have the same procedure as a page on your menu. Either different procedure name, or both must be a popup (or both must be a page.)

you'll actually see the fail in step 4 of your instructions. There's a error in the console window at this point.

Cheers
Bruce