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.

Cool usage of the "Not" operator

trevorg
in Script Workspace and Script Triggers

Featured Replies

I just learned something and thought I'd share.

In the past whenever I wanted to use a field as a toggle (on, off) I would write a script that would check if on/true/1 then set it set it to off/false/0 , else set it to the other on/true/1.

This can all be replaced with just ONE set field and no [if's] inside.

Lets say we had the field called "Toggle" and it's a number field. Since this technique only uses the 0, and 1 (0=off, 1=on), then a number field makes sense to me.

If we simply make a set field command like this:

Set Field ["Toggle", "Not Toggle"]

This automatically flips the 0 to a 1, or a 1 to a 0.

The only problem is if the field is empty to start, then it doesn't enter anything.

I thought it could be useful and wanted to share.

To deal with the null field issue, you can use the slightly less "streamlined" version:

Set Field ["toggle", "Case(toggle, not toggle, 1)"]

Create an account or sign in to comment
Go to topic listing

Important Information

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

I accept

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.