Get button action

[siroos12]

Hi folks,

Is there any way that a developer can get the associated action of a button without physically checking the buttons in layout mode?

To see whether or not the button has an action. If it has, then is it single script step or a script (what is the script name)? 

 

Warm regards,

 

Regards.

[Ocean West]

Using the DDR and FM Perception would be my guess. 

 

[siroos12]

Thanks Ocean West,

 

I am aware of DDR and FM Perception  or similar products. My goal is to use this in conditional formatting to disable or enable buttons.

[Ocean West]

So your trying to determine what the user clicked? 

Perhaps these functions?

http://www.briandunning.com/cf/1942

http://www.briandunning.com/cf/1943

http://www.briandunning.com/cf/1792

[siroos12]

Not actually, I wanna gray out (Or apply any other actions) those buttons that has no action associated to them on layout load.

[Lee Smith]

Hi Siroos,

See if this topic helps/

https://community.filemaker.com/thread/185397

Lee

[Fitch]

2 hours ago, siroos12 said:

Not actually, I wanna gray out (Or apply any other actions) those buttons that has no action associated to them on layout load.

Could you give a real-world example of how this would be used?

Would this work for you:

1. add a Hide condition to each button that references a $$variable

2. add a triggered layout or record-load script that sets the $$variable

Buttons don't have much "self-awareness" so your options are limited I think.

[Lee Smith]

Tom,

The link I posted is to a Friday Nite Challenge by Todd Geist that took place on Friday 13th 2018, on community.filemaker.com, having to do with hiding and showing segments when wanted.

Several members met the challenge and provided their idea of the answers.

Lee

[siroos12]

4 hours ago, Lee Smith said:

Hi Siroos,

See if this topic helps/

https://community.filemaker.com/thread/185397

Lee

Awesome methods. Thanks for that. This helps us a lot!

 

4 hours ago, Fitch said:

Could you give a real-world example of how this would be used?

Would this work for you:

1. add a Hide condition to each button that references a $$variable

2. add a triggered layout or record-load script that sets the $$variable

Buttons don't have much "self-awareness" so your options are limited I think.

Thanks Tom, 

 

I am aware of this technique and already being using it, but I just want to prevent the trigger script. The methods o that folks shared on Tod's challenge are pretty helpful.

 

Thanks for your input.

[Ocean West]

Many times  I will come up with an abstract index of "actions" - create a calculation on the table where that will result in a simple number 1, 2, 3, 4, 5 etc

then use that value to make your hide object when condition work - or other formatting conditions, or even branches in your scripts based on the value.

• isAction = 1 then hide
• isAction =2 format icon green etc. 

Remember you can set the hide object when calc to use a  "LET" notation to declare $$variables since "hide" feature needs to execute very quickly it's one of the first things that is evaluated - so by the time the window draws you can use that $$var to format or hide elements or even display a merge variable on the layout.

[Lee Smith]

Hi Ocean West,

You just described this file you and I work on 3 years ago.

Is this what you mean?

Lee

GlyphsAlt-1.fmp12