Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 7161 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

What's the best way to get visibility into intermediate values calculated during a Script step? For example, I have the following script step:

Move/Resize Window[CurrentWindow, Height:Get(WindowHeight), ...]

and I want to see what the value for Height turns out to be.

Thanks!

Posted

You could set variables into separate global fields as the script progresses, then look at them afterwards. I would think of putting the global fields in their own table. You don't need a relationship to set global fields, just a table occurrence of the globals table.

If you have FileMaker Developer (which it appears you don't), then there is a Debug mode for scripts, which lets you run them 1 step at a time. Great for those pesky Loops, and as you say, intermediate values. You still often have to put the fields on the layout however, or you can't see what's happening. Get (WindowHeight) would not be visible (except visually as the height of the window).

Posted

That did it. You've clued me into an important tool that I'd missed. Thanks!

Thanks to the other responder, too. I had a hunch that might be an avenue. sbg's suggestion was more like what I wanted. (P.S., I do have Developer, but I needed internal visibility to what was happening inside a step - which the debugger doesn't provide.)

Rick

This topic is 7161 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.