Controls: Overview

A control is defined as anything you can drag into the Canvas section of your Design Mode (remember when we talked about the Design Mode? No? It’s okay, there’s a whole section about it!) There are a variety of different kinds of controls, all of which can be found in the right nav section of your Design Mode. They are divided up into three sections: containers, objects, and fields. Let’s take a look at each and get to know them better, shall we?

Containers

A container is exactly what it sounds like - it’s placed on the canvas to “contain” objects, fields, and even other containers. In fact, you can’t drag an object or a field onto the canvas without one! Currently, there’s only one kind of container available, called a section.

Objects

Simply put, objects are the things containers are designed to contain. You will recognize objects as the elements you interact with when you’re using a screen (everything from a simple button to a full calendar is considered an ‘object’). Each object has unique characteristics built by the Method team to perform certain unique functions in an easy-to-use drag-and-drop package.

The objects available in Method are:

  • Button
  • Calendar
  • Chart
  • Checkbox
  • Date/Time Picker
  • Dropdown
  • File attachment
  • Grid
  • HTML Editor
  • Icon
  • Picture
  • Radio button
  • Text input
  • Text
  • Toggle
  • App ribbon
  • Portal navigation
Every object has an “Actions/Events” section that can be used to assign and change actions and events associated with this object. For more information on events and actions please see our documentation on the topic. You can also find a full list of actions here, and a full list of events here.
Almost every object also has a Caption. Internally, the Caption will be used to name the control if you need to reference it within Actions. In the case of two or more controls with the same name, a number will be appended to the internal name for reference within actions only. This number does not appear on the live screen. Example: If there are two “Save” buttons, one will be named “Save”, the second one will be named “Save1” to help you distinguish within actions. When viewing the button text on the live screen, however, both will display “Save”.

Fields

We talked about fields in our Databases section, so for the full story on fields, check it out.  We aren’t going to list every single field available in Method right here because there are hundreds associated with many, many different tables.  The takeaway from this part is that you can drag a field into a section just as you can an object, and that field will draw information from its associated table.

[top]

Was this article helpful?

Can’t find what you’re looking for?

Contact Us