ID
|
TOPIC
|
NEW FEATURE
|
5854
|
Design
|
By using the dynamic properties window you can now replace variables used in script code of drawings forming a symbol.
NOTE: Only directly used basic script code variables are listed in the "Dynamic Property Explorer" and not those used as function parameters.
|
5615
|
Screen Objects
|
A new basic shape object called the "Closed Polybezier" has been added. This object allows you to draw closed polybeziers within which you can apply backgrounds.
|
5576
|
Screen Objects
|
The possibility to set an error text in the 'Recipe Manager' window object has been added to appear when the user edits invalid values. Variable value minimum and maximum limits can also be shown in the error text.
|
5011
|
DOM (Document Object Model
|
The basic script interface has been implemented for the "Recipe Manager" window. The new basic property and function library is called "RecipeWndCmdTarget" and contains all the functions and methods that allow user interaction with the recipe manager object loaded on screen.
|
5251
|
SofLogic Multiprog
|
Support has been added to the Logicon 2.0 version, based on the Multiprog 5.0 version.
|
5272
|
Design
|
The management to preview resources during project design mode has been modified. The showing of the preview window is now disabled for default for screens and basic script resources, but can be reactivated by inserting the "General\ShowTooltipPreview" DWORD value with "1". In addition screen jpeg image files are saved/deleted only on command and not in automatic as was the case before.
|
5167
|
Screen Objects
|
Another two columns had been added to the "Recipe Manager" object which allow the minimum and maximum value input limits for each recipe data. These columns can be added or deleted as required by using the object's layout editor.
|
5439
|
Screen Objects
|
A property field has been added to the "Recipe Manager" object's properties window where you can now set a variable. This variable will activate when the recipe is activated with the "Activate" command. This variable can be string or numeric type. A numeric variable will contain the index of the last activated recipe, whereas a string variable will contain the name of the recipe activated.
|
5012
|
Screen Objects
|
A possibility has been added to exploit basic script events for "Recipe Manager" objects. The added basic script events are:
-
OnActivateRecipe (bRet As Boolean)
-
OnReadRecipe (bRet As Boolean)
-
OnRefreshRecipe (bRet As Boolean)
-
OnSaveRecipe (bRet As Boolean)
-
OnDeleteRecipe (bRet As Boolean)
-
OnCopyRecipe (bRet As Boolean)
-
OnPasteRecipe (bRet As Boolean)
-
OnImportRecipe (bRet As Boolean)
-
OnExportRecipe (bRet As Boolean)
-
OnRecipeIndexChanged(ChangedRecipeIndex As String)
|
5618
|
Screen Objects
|
The click management for clicking on clickable overlapped objects has been modified. As from the 1055, a mouse click will only activate the action set in the object shown in the foreground in respect to the others. If you wish to return back to original behaviour, set the "General->CheckCoveredOnClick" registry key with the "0" value.
|
5507
|
Real Time DB
|
The possibility to record on change when only the variable's timestamp varies has been added. This modification applies to Data Logger record on variable changes and TraceDB recording of variables. A new "Notify TimeStamp Variations" option has also been added to project "Real Time DB" "Variables in Use" management group. Furthermore, a "SetTimeStamp" basic script method has been added for the "DBVarObjCmdTarget" basic script interface, with which the variable's timestramp can be updated with the current time prompting a rewrite of the same value on the connected devise.
|
5509
|
Screen Objects
|
A possibility has been added in the "Embedded Screen" object to modify the screen displayed in dynamic mode using a project variable. This variable can be string or numeric type. When string type a screen with the same name as the string value is searched for in the project; when numeric type, the first screen with ID equal to the set value is taken.
|
5880
|
Design
|
Variable renaming management support is now indicated in the selected driver's properties window. This lets users know beforehand if the driver to be used supports the following two functions:
Note: Drivers linked with 257 base library or later should all support the renaming management.
|
4323
|
Design
|
The renamed variable and resource management has been revised and is now more "user-friendly" especially in the following aspects:
a) The old name of variables and resources now appears between brackets in the project explorer window (can be disabled using an option from the "View" menu).
b) A command now exists for each renamed variable or resource to allow the application of the new name throughout the whole project.
c) A general command had been inserted for applying new names of all renamed variables and resources throughout the whole project.
Note: Communication drivers that support this command are those linked with the 257 base library or later.
|
5354
|
Design
|
The refactoring window displays a "Warning" message when a "Recipe Manager" object is linked to a InMemoryDB recipe. This warning indicates that it is not possible to activate commands simultaneously from the same window object and with the variables or script functions directly in the recipe object.
|
4328
|
User Interface
|
Options have been add to consent users to customize certain elements of customizable windows: numeric pad, alphanumeric pad, user logon and password expiry. With these options you can:
-
Choose to display window title
-
Choose to display window border
-
Choose to have window resized
-
Choose to have the window's system menu available
|
4604
|
Screen Objects
|
Alarm windows used as Client display alarm times using the colour set in the Server.
|
4149
|
User Interface
|
An option has been added to disable messages that show in the Movicon icon tray (i.e. the tooltip that appears on the bottom right when a project is put into run mode). Setting the "General\EnableSysTrayMessage" DWORD value to "0" will disable this message type.
|