Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

The three script steps in a new script

Featured Replies

If my memory serves me well, these are:

Enter browse mode

Go to Layout (Current)

Show All Records.

Now my back to basics question is, to what extent is everyone including them? I am particularly curious about the layout step which I really can't see much value there.

In fact, I don't use it at all.  I create my own template to use.  Show All Records itself is quite hoggish and ridiculous.  Rarely does a User need to see all records and it puts a heavy hit on the server.

 

It feels like they thought it would be a good idea but like many things they do, they did not think it through or provide TRUE functionality with the thing ... it is like it was a thrown-in afterthought.  If they would let us put the things we TRULY need in it, it would be useful - things such as $$disable to disable triggers, controlling user abort - things we want in every script.  As is, it is worthless.

What's the context of this? When I create a new script, it starts out completely empty, as well it should until there are universally accepted practices for what components should always be included in every script, which will be moments before hell freezes over.

I believe it is the create new 'default' script.  

Wow, you made me look for that.  Did not know that it was still around...

Clearly I do not use it.  I use Clip Manager to paste in relevant default parts depending on the what the script does:

 

- always a header to describe the script, it's input and output

- + set allow user abort off / set error capture on

- a script parameter parsing routine if needed

 

- things like a basic loop structure

It's one of those forgotten aspects that could be truly useful if we could establish our own 'default' steps for it.  The steps they chose, as fmow indicates, are unnecessary in most scripts.

Whaddaya know!  

 

Like almost everyone in the thread, I usually start with my own template (basically a comment header, plus a few other steps).  Like Jeremy, I also remembered that clicking the "New script" button creates a new, empty script.  How many times have I gone to the "New" drop-down menu (looking to create a new folder or separator) and never even noticed that "New Default Script…" option?  

 

There was a time—a loooong time ago in FM annals—when all new scripts started out with something like 6 default steps that almost always had to be deleted, but I have vague recollections of that changing, a good number of versions ago, to start with an empty script instead.  Apparently it never went away entirely, but just got a bit hidden (for the better, of course).

 

@LaRetta - I like your idea of FM letting users define their own template that would show up on clicking "New script."

 

Mark

Never. Not once.

 

I always duplicate an existing script. Either one similar to the one I'm creating, or my "Generic Script" which as my own set of frequently used script steps in it already.

Completely useless feature. Nobody uses it.

Don’t sugar coat it Tom, tell us what you really think.   :giggle2:

  • Author

Great thread and thanks to everyone for chiming in with great tips... I am taking notes. 

 

I really didn't expect the topic to get any traction, and always though this is just what should probably be in every script, but most of the time it did not fit my logic to be in any script, what an an irony.

 

Love your show Lee, aren't you guys releasing the new one some time today? I wanted to email you guys but I had a hard time finding the email, I know you mention it in  a few shows, but I d thought I could google my way though it but alas no. 

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.