|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
6135
|
Basic Scripts
|
The "Dynamic Property Inspector" window would not display variables used within a Basic Script after a "Movicon programming Interface" object declaration such as the DrawCmdTarget or the SynopticCmdTarget, etc..
|
|
6155
|
Design
|
When a Movicon resource contained thousands of items, operations carried out on them, such as selecting or searching, would take a long time and the user interface would freeze until operations were terminated.
|
|
6094
|
Design
|
Variables that had been expanded in the editor window would not always get put into the correct order when ordering variables, mapped in shared memory areas, by address.
|
|
6453
|
Design
|
Associating a renamed screen to the Tab Group, its old name would get displayed both in the "Edit Screen List" command's screen list and in the Tab titles that appeared once the object was inserted on screen.
|
|
6422
|
Design
|
Using the "Apply Renamed Variables and Resources" command for scripts in which had been inserted a public Script using the "'#Uses", a message saying that the public Script had already been renamed would get inserted in the script by mistake when substituting the name of the renamed resource.
|
|
6095
|
Design
|
Variable "Address" properties remained disabled when a Shared Area was selected and the variable type was not a "Bit" or "Array" type.
|
|
6412
|
Design
|
The "General->AppTitle" registry key would not completely substitute the "Movicon" string in all the necessary points until the "Office 2007" look was put into use.
|
|
6175
|
Design
|
The "Tag Browser" window would generate memory leaks if called from the project's properties window followed by the command to close project before properties window got confirmed.
|
|
6333
|
Design
|
Using the multi tab window, such as the Refactoring window, would generate a "The required resource was not available" error message performing operations with a lot of variables selected at the same time.
|
|
6162
|
Design
|
The "Apply new name" function for project variables would replace the names of variables in the Basic Script resource incorrectly when containing the "_" character.
|
|
6369
|
Design
|
A symbol or an object within a symbol group would not display correctly when rotated in runtime with rotation animation. This problem would happen when the variable used for dynamic rotation had a null value when the screen while screen was being loaded.
|
|
3943
|
Design
|
You can set default colors in the following fields using the current color palette:
-
Text and background color of alarm thresholds
-
Transparency color of objects on screen
-
BCG and FGC colors of variables
|
|
3975
|
Design
|
An "Access Denied" message would show in Window VISTA when opening and saving a symbol category.
|
|
6036
|
Design
|
A variable's "Apply New Name" command would not replace the variable correctly is used in an expression within a screen object. This problem did not happen when the "Apply Renamed Variables and Resources" command was used.
|
|
6226
|
Design
|
The "Project Explorer" window would not display names of variables associated to "Scaling" objects correctly: in the name of the scaled variable showed in the "Raw" column while nothing was shown in the "Scaled" column.
|
|
6210
|
Design
|
The "Update Public Symbols" manual command would not preserve the default structures of sub-symbols.
|
|
6209
|
Design
|
The fourth command in the "Action" list when opened from the System command list would show the wrong text "Event Column Name..." when it should have been "Launch Application and Wait".
|
|
6487
|
Design
|
The Movicon menu would remain in the previous language when changing the IDE language with the "Language Manager" tool.
|
|
6451
|
Design
|
The Renaming management of the Movicon Resources would freeze if on screen objects had VB script code with syntax errors.
|
|
4081
|
Design
|
Setting a variable as script event in a composed symbol would make it disappear from the list in the "Script Explorer" window, corresponding to the symbol tree, when the project was closed and then re-opened.
|
|
5780
|
Design
|
Deleting an item from the project's resource window, the focus would not position on the next member in order of display but in order of definition.
|
|
6068
|
Design
|
Rename command activation applied incorrectly to resources that still had to be saved.
|
|
6260
|
Design
|
"Hour Plan" schedulers would not manage holiday activations properly if the current day got added or deleted as day of holiday.
|
|
6479
|
Design
|
In the alarm window the order by Severity was in alphabetic and not numeric type. For example, when there were alarms with severity 1,2 and 10, the alarm with severity 10 would get put in order between 1 an 2.
|
|
5936
|
Design
|
The update public symbols command would not work correctly in sub-symbol groups and contained symbol would get updated with the wrong positions and sizes within the symbol container.
|
|
6156
|
Design
|
Easy access to button commands would not work properly trying to access a button's command list using the small circle at the top right made visible when the object is selected. This command list would only open if the button had been associated with at least one command. This problem would only occur when the button was added directly from the Toolbox and started happening with build 1050.
|
|
6418
|
Design
|
Movicon would remain pending when stopping a project that had been started up from design mode when a screen had been added and answered "NO" when asked to save project before going into run mode.
|
|
6096
|
Design
|
Once an expanded group of variables (Type, Area, etc) was set in the editor, the only way to remove it was to set another group type. To remedy this problem, a "None" item has been added to allow you to cancel variable groups in the editor.
|
|
6410
|
Design
|
the Undo and Redo operations in renamed resources with the Rename resource management active would have no effect. This problem started happening with the Movicon build 1050.
|
|
6100
|
Design
|
Symbol code dropping would not mark Screens as being modified when the Dropping code was called using the Shift+DblClick shortcut.
|
|
6330
|
Design
|
When Movicon could not access a symbol library in read, a misleading message would show informing user that the library had been created with a previous Movicon version and that compatibility could not be guaranteed when converting back. This problem started occurring with build 1051.
|
|
6406
|
Design
|
The alignment of Multi Line text on Buttons would not work correctly when the Text Align property was set other than "Center".
|
|
6402
|
Design
|
In the "Tag Browser" window would not show Child projects of Child Project and their relating variables. This problem started with the build 1055.
|
|
6037
|
DOM (Document Object Model)
|
The "TraceUseIMDB" property from the "DBVariableCmdTarget" interface would not get managed in read only and could be written even though this type of connection cannot be changed in runtime for Data Logger objects.
|
|
6178
|
DOM (Document Object Model)
|
When set the VariableMin" and "VariableMax" Basic properties from the "DisplayEditCmdTarget" interface would be ignored in limit checks.
|
|
6489
|
DOM (Document Object Model)
|
The "GetObjectInterface" function from the "DrawCmdTarget" interface would send the basic script in the screen context in error if the screen has a local structure variable.
|
|
4309
|
IL Logic
|
The "A" IL logic instruction with a "Byte" variable would set the CLR (Combinatory Logical Result) to the value "1" even though variable had a zero value.
|
|
6202
|
IMBD
|
Occasionally values read when loading data on screen were not the ones saved in recipes when using a lot of recipes containing numerous columns at the same time in the IMDB.
|
|
6038
|
IMDB
|
When the IMDB engine created a XML file an error would always appear in the log for each value saved:"- XML parser. Error in file ...' : 'Root element has sibling'". However, the XML would get generated correctly even though log would get filled with error messages.
|
|
6419
|
License
|
The Movicon desktop version in Demo Mode would enable more than the maximum limit of 99 drivers allowed.
|
|
6028
|
Menu Resources
|
An "Sharing violation while accessing ....." error would arise while accessing resource files. This would happen when the resource opened in exclusive read mode, impeding other processes to access in read the same resource at the same time. Now the resource files are opened in read controlling whether another process is opening them or already opened them in write.
|
|
6064
|
Networking
|
A network variable's networking connection would get removed from client only and not from server when the client and been create with the Parent-Child project techniques. This problem would occur in these conditions:
-
Child project variable got used in a parent project resource with "ChildProjectName\VariableName" notation
-
Child project could not startup and was set with a network ip for connecting to a server
-
The child project did not have variable manager active.
This problem started happening with build 1053.
|
|
6258
|
Networking
|
Request to enter Comment would not appear when modifying variable structure members using the Audit Trail on Client side for "Parent-Child" projects.
|
|
6058
|
Networking
|
When a variable with its "Trace Comment" option active was modified on Client side, the name of the user logged on Client would not show in the Trace table's "User" column.
Problem started with build 1050.
|
|
6075
|
Networking
|
Setting a network address in a variable's dynamic link would fail. This problem happened only when the network client server services had not been started up. For instance no variable had not yet been connected to a network server.
|
|
6367
|
Networking
|
It was not possible to communicate with a server run as service on Windows 2003 Server from a Server Terminal client session. Now runtime and service communication works using the local protocol.
|
|
6158
|
ODBC
|
Movicon would re-create Log tables (Historical Log, DataLogger, etc) when the project was started up by Windows in Auto Run mode. This would happen at operating system start up due to possible ODBC connection timeouts caused by the fact that the SQL Server service was no longer being run when Movicon tried to record the first data on a table.
NOTE: when inserting the "ODBCQueryTimeout" registry key set with a high value, instead of re-creating tables only errors were generated upon opening DSNs.
|
|
6132
|
OPC Communication
|
Movicon would freeze when an OPC client required the value of an Item from the field in synchro mode.
|
|
6494
|
Real Time DB
|
The (Audit Trail) Comment on a variable being Traced was not asked for when the variable had been set with a Initial default value in its "Data Engineering - Initial Default Value" property.
|
|
6050
|
Report Management
|
Data could not be viewed with the Internet Explorer 8 but only with Firefox when using the datalogger "Create Web Data View Page" command for creating aspx pages for viewing Web Reports and this error showed: "Sorry, this browser isn't currently supported by ASPxDataEdit control."
This problem was caused by using the devexpress version 7.2 controls which were no longer supported in IE8, and have been replaced with those with version 8.2.
|
|
6398
|
Report Management
|
Movicon would not communicate to the ReportDesigner which user to use with the ODBC link when the Datalogger "View", "Export" and "Print" commands were used. The same commands activated in the Historical Log were not effected by this problem.
|
|
6222
|
Report Management
|
Using the "View report" command for alarms and selecting the "Yesterday or today" period a data selection window appeared instead of a direct view of the Report with the last two filtered days.
|
|
6493
|
Scaling Resource
|
Scaling a variable (using the scaling object or in the variable itself) displayed in a display object which had its Format property set would not get managed correctly by WebClient.
|
|
6208
|
Schedulers Resource
|
The scheduler objects set for being activated "every minute" and "every hour" would stop being activated following certain situations. One of these situations would be that the project was stopped the instant in which the command set in the scheduler activated.
|
|
6098
|
Screen Management
|
The Clicking management on overlapped objects would not work correctly when an "Embedded Screen" or "Tab group" object had their displayed screen changed at runtime and the objects of the new screen then got considered as overlapped objects of those already existing previous screen.
|
|
6313
|
Screen Management
|
The "Level" property would not get displayed when symbol was made public. This property must be unaltered when symbol became public.
|
|
6168
|
Screen Object
|
Opening a screen that contained a Display object that displayed a Float type variable set with the "%s" format, Movicon would go into error if the Float variable obtained a decimal value.
|
|
6056
|
Screen Object
|
The ActiveX of "Flex.cell Grid Control" grids would no longer result compactible with Movicon which would raise and error when the ActiveX's COM interface was released. This problem started happening with the 1052 release.
|
|
6407
|
Screen Objects
|
Ordering by severity in the alarm window would not work correctly.
|
|
6234
|
Screen Objects
|
The change page of a screen containing a Movicon Grid with VB script code which called the "SetFocusTo()" function within the "OnSelChanged" event, closed all the screens and then displayed a grid page. This problem started with the build 1055.
|
|
6469
|
Screen Objects
|
A button set with "Commands on Pressed" mechanics would not work correctly when the variable in the "Command/State Variable" had also been set.
|
|
6297
|
Screen Objects
|
Editing a "Scheduler Window", "Grid" or "Recipe Manager" object's grid cell, the window's title would disappear or appear in the cell that had been edited.
|
|
6292
|
Screen Objects
|
The Alarm blink in the Alarm Window would not work correctly when many alarms with different ON times occurred at the same time.
|
|
6302
|
Screen Objects
|
The ComboBox list would not display the list of items correctly if text alignment was set to the 'Right'.
Note: to avoid texts from being hidden by the vertical and horizontal bars you will need to increase the object's height to fit them in.
|
|
6291
|
Screen Objects
|
Pens in "Trend" or "Data Analysis" objects would not get displayed in grey in the legend if their quality was "bad" only when the "Trend" or the "Data Analysis" were in run mode.
|
|
6088
|
Screen Objects
|
In Meter properties windows the 'Scale settings' options had been put the "Variables" property group by mistake instead of the "Style" property group.
|
|
6323
|
Screen Objects
|
A Trend Pen's graphics would not display in the Trend Area when obtaining a lower scale value to the one originally set.
|
|
6137
|
Screen Objects
|
Descriptions of composed symbols instead of their Names were displayed in windows, such as the Project Explorer, Logic Explorer, Script explorer, etc.
A DWORD type "General->UseGroupDescription" (default "0") system registry value is now available that when set to '0' allows lists of objects to be obtained starting with their Names. this value can be se at '1' to return back to previous behaviour where objects are listed according to their Descriptions.
Incompatibility:
This Modification has enhanced the "SynopticCmdTarget" > "GetSubOject" function compatibility. In the previous build this function would search for the object's name using its description, now it uses the object's actual name. As a consequence, projects that first used this function for returning valid objects, might now return a nothing object.
|
|
6387
|
Screen Objects
|
The Movicon Grid executed a wrong Insert query in cases when a record with a date-time field was inserted without there being any other records present.
|
|
6371
|
Screen Objects
|
High numbers of alarms would slow down use of the alarm window when being loaded or when putting the various columns into order.
|
|
6500
|
Screen Objects
|
Clicking or pressing the F2 on a control with its "Prompt Pad" option activated would display the alphanumeric pad in design mode as well. This problem started with the build 1055.
|
|
6193
|
Screen Objects
|
The image containing PNG information when saved in objects with the "Embed" command would lose its transparency.
|
|
6221
|
Screen Objects
|
If an object displayed shadows, such as displays or List Boxes, etc. it would be grouped in a symbol and if the object was overlapped with another object, the shadow would go into background and therefore no longer displayed.
|
|
6159
|
Screen Objects
|
The "Datalogger window" would not manage datalogger changes using the "DLR" property.
This problem started happening with the Movicon build 1051.
|
|
6013
|
Screen Objects
|
The "Recipe Manager" object displayed certain command buttons in the Web Client that were not meant to be used there. However, when used in the Web Client the command actions would take place in the Server instead. The buttons in question were the "Copy", "Paste" "Import" and "Export" buttons which now, as should have been, are not displayed on the Web Client side where they shall always remain unusable.
|
|
6298
|
Screen Objects
|
Starting up the project the "MoviconRunTime.exe" or "Movicon.exe /R" executables, the "Comment" button from the Alarm window would display even though not activated in design mode.
|
|
6167
|
Screen Objects
|
The "Gradual Filling" color animation used with the "Mixed Color" option would not work correctly if dynamic thresholds had been set instead of static thresholds. The shading was managed by considering the minimum value as 0 and the maximum value as 225, while shaded filling coloring would be inverted in respect to the set start and end colours.
|
|
6490
|
Screen Objects
|
The "icons" library could not be used with Movicon.
|
|
6186
|
Screen Objects
|
Public symbol would not update correctly. For example, when modifying the positions of reference public symbol sub elements, their new positions would not get updated in sub-elements of deriving public symbols.
|
|
6160
|
Screen Objects
|
The background image set in screens resized through the "Background - Advanced - Image width/height" properties would not get displayed correctly in "Tab Group" and "Embedded Screen" objects.
|
|
5941
|
Screen Objects
|
An object's "Background - Gradient colour" property would set to the wrong value "Black (000000)" instead of "(ffffff)" when the object got Copied and Pasted on screen.
|
|
5905
|
Screen Objects
|
When a display was associated with the "OnTextChanged" basic event, and protected by a password set with password level > 0, it no longer became possible to bypass the password request pressing the "Esc" key from the keyboard or the "Cancel" button from the LogIn Box.
|
|
6125
|
Screen Objects
|
The Alarm Banner "Fonts - Item Title Font" property would not keep any modifications carried out through the property window.
|
|
6108
|
Screen Objects
|
The "Closed Polybezier" would not get rotated correctly as only its border and not its background would get rotated.
|
|
6265
|
Screen Objects
|
when enabling a button's 'Show Shortcut' option, if the short cut key had also been associated with the ALT key, the text would appear with a "+" character at the beginning of the shortcut (accelerator) string. This problem would not show for other keys such the "CTRL" and "SHIFT".
|
|
4849
|
Screen Objects
|
an editable display set for displaying variable value statistics would raise and error in Movicon if the variable did not exist in the project.
|
|
6040
|
Setup
|
The "Unknown publisher" message would appear when running the Movicon setup in Window 7.
However, this had no influence on the setup when going ahead with the installation procedures.
|
|
6001
|
Setup
|
After installing Movicon and then directly double clicking on the ".movprj" file to run a project would not always work correctly in certain operating systems.
|
|
4057
|
User Interface
|
The tooltip management would not work properly in grouped symbols. The tooltip options would only refer to the basic shape item of the grouped symbols clicked by the mouse instead of referring to the grouped items as one whole symbol. As a consequence, only the tooltip set in the symbol's base item could only be displayed.
|
|
4330
|
User Interface
|
When setting an object's "Keep Proportions" option, the bitmap would enlarge by one pixel in height and width even though the control hosting it had the same sizes. Therefore, the bitmap would result too big by one pixel for the host control.
Incompatibility:
Use the "OldStretchImageSize" registry key to restore previous behaviour.
|
|
6495
|
User Interface
|
The Movicon service would not terminate upon stop command without runtime license intact due to the fact that the Demo Mode reminder window has not been closed.
|
|
6322
|
User Interface
|
When the "Evaluation Mode" window requesting registration code entry appeared upon opening a project, some of workspace windows would not get refreshed correctly until the ""Evaluation Mode" window got closed.
|
|
6198
|
User Interface
|
Visualizing variables in Dundas Meter objects with quick changing values would slow down or freeze the user interface. A new property, called 'Dundas Gauge Refresh", has been added where users can now set refresh times.
|
|
6457
|
User Interface
|
One or more border lines of a selected object would get hidden if the Screen's "Antialiasing" option was active.
|
|
6063
|
User Interface
|
Movicon would freeze while closing a project. This would happen when a communication driver continued to change values of variables connected to alarms while the project was closing. Now all communication driver go into pause mode during project close phase.
|
|
6414
|
User Interface
|
Using a different look from the "Office 2007" look would bring about problems in the Movicon workspace where certain icons would not get loaded correctly.
|
|
2795
|
Users Management
|
Upon user Logoff, or when setting a "UserCmdTarget" object to "Nothing", the application would generate an error and close. This would only happen if the user logged in, or the user referenced through the basic script, had been updated with new properties while logging off. For example, if the user's properties had been modified with the runtime user editor.
|
|
6191
|
WebClient
|
Java applet called from command line would not give the option to enter the TCP Port parameter.
|
|
6045
|
WinCE
|
A "The program is not compatible with the current operating system and may not run on this device" error message would show on some WinCE panels installed with Windows CE 6.0. while installing a driver. However, if ignoring this message and continuing on with the installation procedures, the driver worked as normal.
|
|
6395
|
WinCE
|
The Alphanumeric Pad would not show in the Scheduler Window when selecting the "value" cell without there being a 'Tag' column in the grid.
|
|
3400
|
WinCE
|
Changing pages became very slow in cases where screen resources had been divided into folders or sub-folders. This problem started happening in Windows CE 6.0 with build 1017.
|
|
6492
|
WinCE
|
System variable members which update every second, such as "ActTimeString" members, would in reality update with a major time.
|
|
6190
|
WinCE
|
Some bitmap images saved in 32 bit would not get displayed correctly. This problem started with the build 1055.
|