Is there a simple method to hide a tab in find mode?
I want to only hide ONE of the tabs in a tabbed interface, NOT the whole tabbed interface.
Hi. I haven't found a way to hide a tab, but you can come close. You might try 1) making the tab label a calculation that becomes null in Find Mode and 2) 'hiding' all object on that tab using a calculation (be sure to check the 'find mode' check box).
You may find it easier to display another object in find mode, that overlays the tab button, making it inaccessible.
I replied already to your respoinse but can't see it here. Oh well, here I go again.
I also thought of that but was hoping for a way to disable the tab from appearing at all in Find mode since it contains objects not applicable in Find mode.
I may just remove the tab and have a command to invoke a small window displaying all the objects that I only want displayed in Browse mode.
Yep, I thought of that as well but want to keep it simpler.
As for the objects within the tab, yes, I can change their behaviour to NOT display in Find mode using the a function but refer to not see the tab at all in Find mode.
I will likley go with a different approach; have a command to open a small window displaying the objects while in Browse mode.
So many cool and easy options availabe in FM 13.
Thank you for your response.
You could also have a OnTab Switch trigger that prevents the tab from loading in Find mode.
Duplicate your tab panel. Remove the one tab from the duplicate. Set the orignal panel to be invisible in find mode and set the duplicate to be invisible in browse mode. Then stack the panels on top of each other.
Now THAT sounds interesting. I might well try it. Thanks.
It is working
If you plan to do duplicate objects to create a browse and a find version it may be simplest to duplicate the entire layout. Use script triggers to switch between them. A colour-coded background ensures that the user knows that they are in the find layout. This has the advantage that you can optimise every object for find oriented behaviours.
Actualy, I have done similar things in the past but I'm tryinig to build a new template minimizing the number of layouts. Just keeping it as simple as possible. When I used a find and browse layout (and still do suppot it in many files from the the past that are still being used), I had to change both everytime a change was asked for, such as new fields, change the tab order etc etc.
I'm hoping that FM will release a version at some point that will allow us to globally change objects throughout the database. That would be great. Imagine having 20 layouts and then then 6 months down th road the client wants a colour or some other format change. Instead of visiting each layout, just make changes as variables. I've done some similar things in the past but it was cumbersome and involved lots of calcuation and scripts.
I'm forever on the quest for simplicity, and avoiding complexity if at all possible.
For any Form layout, I create a hidden tab panel. One tab is named "tab.Browse", another is "tab.Find". The actual labels a blank and there's no border, so the panels cannot be selected by the user. An onModeEntry script trigger uses Go to Object selects the correct panel for the mode. One layout, two very different looks. The Find panel is colored differently and has only the fields the user may find on. No portals (only the related fields), text areas become text boxes, etc etc.
I would recommend against a tabbed interface in Find mode. It's confusing for users.
Hmmm, also a creative and simple solution. Thank you.
like we could with HyperCard in the 90s?
mrosenhek wrote: I'm hoping that FM will release a version at some point that will allow us to globally change objects throughout the database. That would be great. Imagine having 20 layouts and then then 6 months down th road the client wants a colour or some other format change. Instead of visiting each layout, just make changes as variables. I've done some similar things in the past but it was cumbersome and involved lots of calcuation and scripts.
Isn't that exactly what custom themes are for? Or perhaps I'm not understanding what you mean by "format change?"
I admit I've not worked much with themes. I think you can save your own themes to apply at will but that is not exaclty what I meant.
I'm talking about making a change in one spot and have it flow through to all layouts. Kind of like a global field if y ou get my drift. That could be very useful at times especially when you have 100 layouts to deal with. OTOH, using themes to appy to a layout after the fact, can be very useful too, especially when you want to pick and choose only specific layouts.
That said, I tend to desisgn very simple layouts, no bell and whistles. I'm not all that interested in bling and neither are my typical clients.
Thanks for your response.
I just wanted to re-iterate that I used your suggestion and find it works like a charm; simple and easy to do and gave me exaclty what I was after.
Retrieving data ...