Skip to main content

Developer mode

Introduction to the developer mode

When your end product is started in developer mode, extra options become available in the Developer tab in the ribbon.
For main administrators, developer mode is enabled by default.

ribbon_developer Developer tab in the ribbon

These options are:

  • Refresh model (Ctrl+Alt+F5) - Reloads the model, so modifications in the end product are immediately visible. (The shortcut might be blocked by certain applications.)

    Universal GUI Refresh model is available from the profile menu.

  • Debug - Displays events that are performed on the database, such as look-up queries, views, defaults, layouts, etc., and more information about error messages from the database. Filtering on events can be done in the filter at the upper left.

  • Version check - Checks whether the versions of all the required DLLs are correct, such as database drivers and Crystal Reports.

  • Open folder - Opens the GUI folder.

  • Location (Alt+F1) - Shows detailed information on the current screen and the focused component.

    Location popup

  • Translate - Switches between translated and untranslated mode.

  • Process flow monitor - Opens the Process flow monitor, to observe what happens while running a process flow.

  • Test console - Opens the test console to run test cases. The test console is only available if your application has been started against the Software Factory.

  • Test case recorder - Opens the Test case recorder, to record test cases.

  • Documentation - A direct link to the online documentation (www.docs.thinkwisesoftware.com).

  • Community - A direct link to the Thinkwise Community.

Error messages

In developer mode, error messages about defaults, layouts and contexts are displayed in the Windows GUI in the info panel. The GUI also executes the logic so the existing functionality continues to work after, for example, adding or removing a field or reference.

In end-user mode however, error messages are displayed as pop-ups, and the user action is blocked to prevent business logic being bypassed.


Was this article helpful?