Studio Preference Settings

This is where Studio looks for samples and other components at startup. If you modify this setting, restart Studio for the change to take effect.

In general, do not change this setting, except under the direction of product Support.

A perspective is a collection of Eclipse views that are opened together to perform a set of related tasks. StreamBase Studio can be set to automatically switch between perspectives on certain triggering events. Studio automatically switches to the SB Test/Debug perspective when you launch one or more fragments, and stays in that perspective as you continue to launch fragments. By default, the setting for Switch to SB Authoring perspective when stopping the last fragment is enabled.

An operator or adapter is marked deprecated with the Java annotation @Deprecated in its primary Java source file. You can mark your custom operators or adapters deprecated as your project evolves and new components replace older ones.

StreamBase® occasionally marks certain components as deprecated to encourage the use of newer components. If you are working on a legacy application and need to continue using a deprecated component, enable this setting.

With this setting disabled, the display of EventFlow fragments that were saved with now-deprecated components is not affected. However, such fragments cannot pass typechecking and cannot be run in Studio, because the code that underlies the deprecated components was not loaded. You can continue to work on such fragments by enabling this option, or by upgrading the deprecated components with their replacements.

Site-specific Component Exchange URLs can use the HTTPS protocol, in which case Studio prompts you for access credentials on the specified server.

If you supply a URL that begins with HTTPS or FTP, Studio automatically prompts for credentials. If you supply a URL for another protocol, you can force authentication prompting for that protocol by setting the Java property streambase.ide.component-exchange-force-auth to true for the JVM that runs Studio.

Specifies that components are automatically typechecked as you build your EventFlow fragment. Disable this preference to suppress automatic typechecking.

See also the related checkbox to enable Typecheck EventFlow Editors in background on the Typechecking panel, described below.

This feature adds an extra step to keyboard shortcuts that place new components on the canvas. For example, to add a Map operator, the keyboard shortcut is (at minimum) O M Enter with this option enabled, but is O M with this option disabled. You may prefer to disable this option temporarily when entering a long sequence of keyboard shortcuts to quickly fill a new canvas, then re-enable it. See Studio Keyboard Shortcuts.

When enabled, auto-centers the canvas on components selected when navigating in two ways:

With this checkbox cleared, Studio highlights the selected component on the canvas, but does not center the canvas. If the component is offscreen when selected, Studio moves just enough of the canvas to make the component visible.

When cleared, the check box, radio button, and drop-down menu controls in Java operator and adapter Properties views display a T icon () to the right of their text labels. Clicking the icon or typing Alt+F2 (Option+F2 on Mac) replaces the check box, radio button, or drop-down menu with a text field, in which you can enter:

When this preference is enabled, you can still convert a UI control to a text box with the keyboard shortcut when the control has focus. For additional details, see Parameterizing Java Operator and Adapter Properties.

StreamBase Studio respects the layout status it detects for each EventFlow fragment individually. That is, if Studio detects an .sblayout file with the same base name as the EventFlow file you are opening, it uses the layout information in the .sblayout file, and stores layout information there when saving the fragment. If Studio detects no .sblayout file, then it uses the layout information in the .sbapp file, and on save, stores layout information back to the .sbapp file. This Studio behavior is NOT changed by setting this preference.

This setting controls only whether .sblayout files are created automatically when you create and save new EventFlow fragment files, and does not affect existing .sbapp files in your workspace. For further details, see EventFlow Layout Options.

Enable this option (default) to show tiles around component icons, whose left and right edges are where ports attach. Disable to remove the tiles. The selection outline still appears with or without tiles.

When disabled (default) the selection outline is filled with light blue as shown above. When enabled, the selection outline shows as an unfilled dotted line, as follows:

When enabled (default), shows a yellow information box for a component when hovering the mouse over it.

When enabled (default), if a component has the Run this component in a parallel region option selected in its Properties view, the component is shown with a circle inside the bounds of the icon.

When disabled, the circle decoration is not shown, and there is no visual indicator of the component's separate thread state.

Resizes columns to fit content.

Resizes rows to fit content.

Displays filter when present.

The Table Analyzer takes into consideration the optional domain model when analyzing the decision table to report any uncovered domain entries.

Displays Table Analyzer contents when the decision table is open. However, you must click the Analyze button to invoke the analysis.

This setting in Preferences is global for all projects. You can override this setting for individual fragment launches in the Environment tab of a fragment's Run Configuration dialog.

When you specify formatting for numeric values, you can directly enter a format string that follows the java.text.DecimalFormat standard. Format string fields also serve as drop-down lists that offer a selection of predefined formats. You can also select the Edit Recommendations link from the dropdown list to view formatting examples.

Use this control to add human-facing formatting to incoming data fields, such as adding the appropriate currency symbol, commas, and two decimal places to an incoming double value to show it as a currency value.

The row limit for query results allows a LiveView client to prevent the server from sending excessive data. The limit specifies the maximum number of rows that the server returns to the client. Without a row limit, an insufficiently restrictive query on a large table or a rapid-changing table might overwhelm the client with more data than it can process.

Regard the row limit feature as a mechanism to protect clients from an extraordinary data load or from incorrectly defined queries. Because query results are not updated once the row limit is reached, It is a best practice that you do not run queries that consistently reach the row limit. (If a query does reach the row limit, you can use the Refresh menu option in Studio to see recent updates.) Set row limits low enough that client processing capacity is not exceeded, and define query predicates to be restrictive enough that the row limit is never or rarely reached.

When you run a fragment and enqueue data, the number of input tuples can become quite large. It can be helpful to limit the number of tuples in the Input Streams view's display buffer. When the limit is reached, newer tuples are kept in the view while older tuples are allowed to scroll off the view.

The specified display buffer size applies to the total number of tuples in the Input Streams view, from the total of all input streams.

Same as above, but for output tuples in the Output Streams view.

The specified display buffer size applies to the display of each output stream, as well as when (All Output Streams) is selected.

Enabled

"null"