Is it possible to set a trigger on the tabs that sets one global field/one variable?

For example: I have seven tabs: Monday, Tuesday....Sunday.

Clicking each tab would set a variable: Mon, Tue... and so on accordingly.

But I can't assign script parameter to each tab - it sees it as one script with one parameter.

I can name each tab as object, but how do I extract object name and use it for changing data in the field/variable?

I hope it's clear...

Hi Monarch

You can use the Get ( TriggerTargetPanel) function to give you the index number and object name of the panel that you are switching to, and you use the OnPanelChange trigger to run a script to make use of that.

I've done a simple test file for you to take a look at if that helps?

 

TEST.fmp12

2 hours ago, Monarch said:

I have seven tabs: Monday, Tuesday....Sunday.

Are you sure you need to have seven different tabs? I would suspect seven buttons (possibly arranged to look like tabs) would be sufficient.

16 hours ago, rwoods said:

Hi Monarch

You can use the Get ( TriggerTargetPanel) function to give you the index number and object name of the panel that you are switching to, and you use the OnPanelChange trigger to run a script to make use of that.

I've done a simple test file for you to take a look at if that helps?

 

TEST.fmp12

Thank you rwoods!

As always - it's simple... These "get" functions can really get me.

Thanks again!

14 hours ago, comment said:

Are you sure you need to have seven different tabs? I would suspect seven buttons (possibly arranged to look like tabs) would be sufficient.

Thank you comment.

Yeah, I am considering the same thing - buttons vs. tabs...

Not sure what would be more efficient:

a. multi tabs with same portals in each tab, but different filtering.

or

b. buttons, as you said, with one portal, but more complex dynamic filtering.

But here my concern is - if I have thousands records in the portal to filter, would it slow it down filtering if I use buttons?

If you have thousands of records, then you probably don't want to use portal filtering at all. In any case, this is a separate issue. My point was that you probably don't want (and don't need) to replicate every object shown in the tab control 7 times. And have to carry out every design change 7 times.

On 2/11/2017 at 3:02 AM, comment said:

If you have thousands of records, then you probably don't want to use portal filtering at all.

Well, then how do I do it, if not filtering, thru relationship?

And yeah, you are right about 7 tabs. It didn't feel right, so I am going to do it with seven buttons.

9 hours ago, Monarch said:

Well, then how do I do it, if not filtering, thru relationship?

I can only guess (since you never explained what exactly your filtering does), but in general you would have the buttons set a global field instead of a variable, and instead of filtering the portals, you would filter the underlying relationship by adding the global field as a matchfield.