|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
6017
|
Setup
|
The Windows CE 11.1 version setup would not install the version updated by the EditUsr.exe tool.
|
|
6006
|
Tools
|
Even though the "CFR21-Part 11" option had been activated, it became impossible to save two users with the same description using the runtime users editor. The Movicon application would not authorize the user in read if user's description had already been used.
|
|
5987
|
WebClient
|
The "Failed to load Main-Class manifest attribute from..." error would show when running the applet java from a command line with the "-noverify" option.
|
|
6002
|
User Management
|
When Movicon read a runtime user, it would always reset the user's original password read from the runtime users file. Therefore if user had changed their password when original expired, this would not be taken into consideration.
|
|
6003
|
Design
|
Movicon would raise an error after the name of a variable or the name of a structure prototype associated to that variable had been changed with the intellisense enabled. This error would show when trying to access an object's script code using the "Script Explorer" or opening a basic script resource's script code. In addition, there were a few other minor problems causing the variable list in the intellisense not to update with the project's variables accordingly.
|
|
6027
|
Screen Objects
|
Buttons in Movicon built-in objects which were hidden in runtime because not usable in the context active at that moment (i.e. Windows CE or Web Client), apparently could be still clicked with the mouse. These buttons are actually designed in an area outside the object's border but are not visible on screen when out of context, so when this area was clicked on the associated button command would activate.
|
|
5972
|
User Interface
|
The "Capture and Print" command would freeze the project's user interface when using a printer requiring parameter settings (i.e. the "Adobe PDFWrite" printer).
|
|
5947
|
ODBC
|
The ODBC "MySQL" plugin could not recreate the ODBC DSN connection if database already existed. This problem would only show when the name of the project contained a space.
|
|
5996
|
Design
|
Movicon would raise an error when closing a project. This problem would show only when the screen navigator editor had been opened and closed in runtime beforehand.
|
|
5943
|
Screen Objects
|
In order to restore the timeout condition of a "Scheduler Window" object, the page containing it had to be reloaded beforehand. You are now allowed to exist from timeout mode with the Server when carrying out operations in this object type.
|
|
3504
|
Screen Objects
|
Some of the Movicon objects (Alarm Window, Data Logger Window, TraceDB Window, Chart, Trned and Data Analysis) would not show the correct time when connected to a Network Server, or when opened by Web Client, and when under DST (i.e. 10 April 2008). The conversion for UTC time to local time would not take into account any differences made by local DST in act.
|
|
3452
|
Design
|
The refactoring window would also report dynamic variables such as [DRV], [NET] and [OPC] used in controls as being non-existent variables.
|
|
913
|
ODBC
|
Columns would not get generated in perfect alignment with the variable linked when a creating tables. This problem showed for these type of variables:
-
A word variable with sign mapped with a "smallint" type column (8 bit) instead of a "integer" (16 bit).
-
A dword variable (with or without sign) mapped with a "integer" type column (16 bit) instead of a "bigint" (32 bit).
-
|
|
1955
|
Design
|
Movicon failed to register project file extensions in Window Vista or later versions. this problem arose when the UAC was active.
|
|
5155
|
Screen Objects
|
The "Scheduler Window" object allowed grids to be saved even when values had been set incorrectly. Now, according to the type of variable selected in the "Tag" field, the set value's validity is controlled. The hour plan cannot be saved if the set value results as being invalid.
|
|
4356
|
ODBC
|
Movicon would delete the an ODBC database table at the project startup. This situations would arise when the data logger received the record on variable command immediately upon project startup.
|
|
4005
|
Networking
|
The "Chart" object would not close the connection to the network Server when the screen containing it was closed. This connection would, however, close in the Server when inactivity time expired.
|
|
5400
|
Users Management
|
When the Movicon application was shrunk to an icon while active the options for hiding and disabling the desktop the Start button, the application bar, task manager and ALT+TAB were still active, it became in possible to display the application window in the foreground. Now, any options to access Windows are disabled when a "Administrator" or "developer" level user is logged on and can be reactivated when the project user is changed.
|
|
5405
|
Networking
|
An array or structure variable used in a control through the intellisense syntax (<Variabile>.<Elemento>), would not get exchanged correctly in Client networking mode, if the project had been created with the Parent-Child technique.
|
|
5446
|
Screen Objects
|
When a "Scheduler Window" object was connected to a network server, the variable's minimum and maximum value settings would not get read from the network server but from the local project, therefore the variable would differ and even result non-existent locally.
|
|
5451
|
Networking
|
The quality of a variable would not get handled correctly in networking. In particular the "Update Quality Status" option from the variable's network connection properties would not get handled correctly both on the Client and Server side.
|
|
5640
|
Schedulers Resource
|
The daily plan (every day, every Monday, every Tuesday, etc.) and monthly scheduler activation logic was not completely correct. The logic would only take into account the strictly necessary parts and not the date and time globility of the last command executions. For example one daily plan would not get executed if the year was different to the one of the last execution even though the day had remained the same.
|
|
5642
|
Screen Objects
|
A drawing's "SymbolLoading" event's basic script code would not get executed when the "Embedded Screen" object loaded a screen.
|
|
5638
|
Design
|
Movicon would freeze opening a password protected project when the alphanumeric keypad was called to insert user name and password. This problem would only show in those projects that had customized alphanumeric screen pad properties.
|
|
5664
|
DOM (Document Object Model)
|
The "DrawCmdTarget basic script interface's "BitmapTransparentColor" property would not get handled correctly. It would always return "-1" in read, and would not allow changed to be made to the transparency colour used in write.
|
|
5654
|
Users Management
|
The runtime users list would get loaded into the project even though the project's "Enable Runtime Users" option had been not been checked. This problem would show when the "<project>.rtusers" file was modified while project was running.
|
|
5656
|
Screen Management
|
In projects where the change page activated only when changing an "Embedded Screen" object's screen resource, a continuous increase in memory was occupied (even though modest) at each page change. This increase in memory use was due to references inserted in lists in memory that had not been unloaded when the embedded screen changed the displayed page, but only when the screen that contained the embedded screen was unloaded from memory (this would only happen in certain projects).
|
|
5613
|
Setup
|
The "Movicon.exe" application would not go into automatic mode and the Windows "Windows cannot open this file" error message would show after having installed Movicon and double clicking on the demo's project file.
|
|
5505
|
Tools
|
No message was issued to the user while trying to import or export strings when project was encrypted or zipped. Now, a message appears telling the user that the exporting/importing of string has failed because project is encrypted, zipped or corrupted.
|
|
5597
|
DOM (Document Object Table)
|
The "UIInterface" interface's "LoadPicture" method would fail generating an error in the basic script in which it was used. This problem never happened in version 11.0.
|
|
5598
|
Screen Objects
|
Problems occurred in Window type objects when modifying the order in which columns were displayed in both Design and Runtime mode. The main problem being that when window was refreshed it would not always show the new order that had been previously modified.
|
|
5549
|
Screen Objects
|
An object's "Auto Save File Settings" option would not save all the properties of that object when the project was run with "MoviconRuntime.exe", "MoviconService.exe" or with the runtime for Windows CE.
|
|
5836
|
SofLogic Multiprog
|
The command used for opening the OPC Server KW-Software settings in Movicon's design mode would not work.
|
|
5841
|
ODBC
|
Movicon always recreated a ODBC DSN connection in MS Access if a connection already existed when the one to the database manager failed. This would cause the loss of all custom connection settings in cases where the database manager was momentarily unavailable at project startup.
|
|
5895
|
Screen Objects
|
A variable's engineering data limits were used by the "Scheduler Window" object even when the selected variable had not been enabled with scaling option. This problem would only happen when the "Show Pad" option was being used.
|
|
5925
|
Design
|
Movicon would crash when selecting a variable form a child project from the "Tag Browser" window. This problem happened only with structure type variables which had been browsed and changed in the "Tag Browser" window before being selected.
|
|
5914
|
Design
|
Browsing variables using the "Project Explorer" window and above all the "Tag Browser" window, took a long time when the project contained lots of variables. This operation has been improved and is now much quicker.
|
|
5906
|
Screen Objects
|
Inserting a string type value con the "Scheduler Window" object was limited to 1000 chars even when the string variable selected had not been set with any limits in its engineering data properties.
|
|
5789
|
Networking
|
Variables that were connected using the local protocol would not get created as the same types of the Server's. For example all the dynamic [NET] type variables used in controls were mainly hit by this problem.
|
|
5771
|
Design
|
A screen resource could be checked with save marked when simply opened and closed in edit mode without being modified. This problem would arise if the screen resource contained an embedded screen object that contained an window type object with it's 'Auto Column Layout' option disabled.
|
|
5782
|
Design
|
When returning to design mode, the screen that was displayed before going into run mode with the project, would display completely empty. This problem would only occur when the following conditions exist:
-
The screen was open in edit mode before running project.
-
The tree node relating to the screen had been expanded (even by just one level) in the "Project Explorer" window.
-
An item relating to the screen (i.e. local screen variable list) had been selected in the "Project Explorer" window.
-
|
|
5741
|
DOM (Document Object Table)
|
The management which consents the non-activation of numerous commands, when numerous objects are overlapping each other, would not take into account that the tabulation order of the drawing objects may have been changed in runtime with the "DrawCmdTarget" basic interface functions.
|
|
5727
|
Web Client
|
Running the midlet in a java phone device and setting the "Compression" option would accidentally set the "Encryption" option as well.
|
|
5733
|
Design
|
Movicon would crash when using the "Cancel" or "Restore" commands in window type objects that had been enabled with the "Show Control Window" option.
|
|
5720
|
DOM (Document Object Table)
|
The negative result of returned values belonging to some Movicon functions that returned "true/false" values, would not always be consistent. This problem would arise with the following functions:
-
The "DBVariableCmdTarget" interface's "GetVariableValue" method.
-
The "DBVarObjCmdTarget" interface's "Value" property.
-
The "DBVarObjCmdTarget" interface's "StatisticDataMinValue" property.
-
The "DBVarObjCmdTarget" interface's "StatisticDataMaxValue" property.
-
The "DBVarObjCmdTarget" interface's "StatisticDataAverage" property.
-
The "DLRColumnCmdTarget" interface's "StatisticMinValue" property.
-
The "DLRColumnCmdTarget" interface's "StatisticMaxValue" property.
-
The "DLRColumnCmdTarget" interface's "StatisticAverageValue" property.
|
|
5724
|
Networking
|
A Client project created with the "Parent-Child" techniques would sometimes zero some of the variables in the Server when put into runtime mode. This problem started happening with the 11.1 version.
|
|
5725
|
Screen Objects
|
Messages relating to incorrect entries in the "Scheduler Window" would not be subject to language change using the project's string table.
|
|
5723
|
Screen Objects
|
A light button would not light up for "Command/State" variable values exceeding 255.
|
|
5711
|
Networking
|
A structure variable with many members with enabled statistics, would take a long time to connect to the Server. This problem started happening in the 11.1 version following modifications to save structure variable statistical data in the retentivity file.
Incompatibility:
Running a project after having updated runtime, will reset statistical data for structure type variables.
|
|
5714
|
Design
|
Some drawing objects could be exported correctly in vectorial format. The exported file displayed a dot instead of the drawing when opened with an another software. This problem usually happened when the "Pipe", "Polybezier" and "Text" objects were not specified with the .emf extension, would get created in a file with the Windows Meta File (.wmf) format and therefore the wrong format needed for these objects.
|
|
5747
|
Screen Objects
|
When a "Recipe Manager Window" object was connected to a network Server, any changes to the recipe's data on the Client would not get updated on the Server until the recipe lost focus. This problem happened only when the "Show Control Window" option was enabled (set to "true").
|
|
5748
|
Screen Objects
|
The "Recipe Manager" object's "Read" command set cell values with the "-1" value for bit type variables.
|
|
5788
|
DOM (Document Object Model)
|
There were problems modifying the network Server name used for connecting to window type objects in runtime. This problem involved the "NetworkServerName" property of these objects' various basic script interfaces.
|
|
5791
|
Windows CE
|
The "Recipe Manager" would print an error message without any text in the system log. This problem would arise when an object connected to an IMDB data logger with set command variables. This message is now correctly printed indicating that it is not possible to use these commands in write with the current configuration.
|
|
5810
|
Design
|
A number of different problems have been fixed in the renamed variables and resources management which arose when working in design mode. These problems involved parent-child projects and project in which local screen variables were used.
|
|
5926
|
Screen Objects
|
Data scrolling buttons used in the "Data Analysis" objects would not always show the right results as expected.
|
|
5910
|
Design
|
The "Dynamic Property Inspector" window would not manage renamed variables in the project when the renaming manager was active.
|
|
5850
|
Design
|
The original name of a variable would get lost if the variable was moved to another variable group or removed and then reinserted.
|
|
5550
|
Basic Script
|
The "OnPreSymbolLoading" event would get executed first for the container and then for the sub-symbols, contrary to the "SymbolLoading" event. Now both events execute the code of sub-symbols before that of the container.
|
|
5555
|
User Interface
|
Not all the PNG images would display correctly. Apparently the problem arose in those images which used transparency values differing in pixel settings.
|
|
5542
|
WinCE OS
|
The change language command activated through a modal screen, would take the focus away from the screen giving to another application that was not MovCE.exe (i.e. a shell launched upon panel startup).
|
|
5545
|
WinCE OS
|
the PNG images were displayed without taking into consideration transparency. Now the image transparency is managed in two different ways:
-
By using the "AlphaBlend" function if found in the WindowsCE image's "Core.dll" dll.
-
With an internal algorithm if the "AlphaBlend" function cannot be found.
Note: The first method performs much better then the second method. A message will appear in the application's initialization window at MovCE.exe startup when the "AlphaBlend" function is found and ready for use.
|
|
5546
|
User Management
|
Alarm notifications to a user group would only get sent to users configured in design mode and not those added in runtime.
|
|
5508
|
Design
|
The zoom would not get applied to image contents of screen drawings if the "Streatch Image" had been enabled. Now, the images are adapted to the new screen sizes only when printing the screen or when editing it.
|
|
5503
|
Tools
|
Exporting strings would fail if the project's active language got changed while the "String Import/Export" tool was still opened.
|
|
5504
|
Tools
|
The tool used for importing/exporting project strings would not alert the user if a string already existed during the import phase and would always overwrite it. Now, a dialog window appears where the user can choose whether to or not to overwrite existing strings and whether to or not to continue to overwrite any other successive existing strings when found.
|
|
5558
|
WindCE OS
|
The language change and the commands used for going to the next and previous screen pages failed to work if the path containing the project had a dot character.
|
|
5570
|
Alarm Management
|
No alarm alerts were sounded in 64 bit operating systems. Now alerts are sounded using the audio card.
|
|
5639
|
Design
|
The same developer user name as the one recovered from the domain could be entered when creating new projects with the "Win32 Platform" wizard. Now, the 'Developer' user can only be entered if not already existing in the dominion user list to be added to the project.
|
|
5643
|
Design
|
The variable group copy&paste would create a new group always using the same predefined name in the project's variable database's root. Now groups are created in the position in which the "Paste" command is activated and the name does not get changed unless another group already exists with the same name at that level.
|
|
5647
|
Design
|
The properties window would display in collapsed mode when opening Movicon instead of being in the one before existing from Movicon. This problem started happening the 11.1 version.
|
|
5649
|
Design
|
The icons to be associated to the various project files would not get recorded correctly. As a consequence, the Windows resource explorer would display the standard icon for each project file.
|
|
5688
|
Design
|
When closing a project a Movicon application error would get generated if a variable group had been deleted using the "Cancel" command.
|
|
5693
|
Screen Management
|
The screen print command would not print the contents of a Trend object.
|
|
5421
|
DOM (Document Object Model)
|
The methods for handling external configuration files were missing from the "DisplayEditCmdTarget" and "ListBoxCmdTarget" basic interfaces. These methods have now been added:
-
ExtFileSettings
-
LoadExtSettings
-
SaveExtSettings
|
|
5355
|
Screen Objects
|
The "Edge-Text Color" animation in Display objects would not work properly. When changing the color threshold, the value of the variable displayed in the Display object would disappear and would not show until it changed value again.
|
|
5365
|
User Interface
|
A screen's background image would fade a lot when displayed with sizes different to the ones it was originally set with. This problem happened when the images on screen were set with the "Fit in Window" option or if they had been set with properties to be resized on screen.
|
|
5366
|
Screen Objects
|
The animated movement of an object contained in a symbol would not work correctly if there was animated movement in progress in the symbol container.
|
|
4526
|
WinCE OS
|
The MovCE.exe application would crash when textual report related commands with invalid value formats were used. Now if these commands fail an error message is issued in the application's log.
|
|
5332
|
Real Time DB
|
Data statistics of a structure variable would not get collected from the network Client when the Server connection was set directly in the Client's structure variable. Parent-Child Client projects did not have this problem.
|
|
5339
|
Redundancy
|
Structure variables data statistics would not get read by the primary Server in a redundancy application. As a consequence, when the Primary Server was down, statistical data in the Secondary were not aligned with the primary when taking over.
|
|
5343
|
Screen Objects
|
All the window type objects enabled with the "Show Control Window" option would not update the row selected with the mouse until the mouse moved away from that area of the object.
|
|
2266
|
Screen Management
|
The attempt to load a child project screen with the "_SysVar_:StrobeLoadScreen" system variable would fail in certain circumstances.
|
|
1297
|
Basic Script
|
When using the "Script Explorer" window for exploring screen or drawing VBA code, the object list would not get populated with the ActiveX instantiated with the "WithEvents" clause. For example, a design object and this following line of code:
Dim WithEvents Winsock1 As MSWinsockLib.Winsock
The "Winsock1" object would not appear on the object list. As a consequence it became impossible to automatically retrieve specific events of that object as well.
|
|
141
|
Design
|
When performing a "paste" operation with a different zoom level on screen than the one used to perform the "copy" operation, the pasted object's sizes were out of proportion and positioned in differently to the original. In addition, the control title font size copied while in zoom mode would get immediately resized according to the zoom applied on screen. As a consequence, the text displayed in the copied object was clearly a different size to the original copied text.
|
|
2533
|
Design
|
The Refactoring window would not report all existing errors. In particular, errors would be left undetected when variables had not been defined in the RealTimeDB but had been used in an object's "Dragging" property or in the IL Logic. In addition, errors detected in the communication driver would not report the tasks in question.
|
|
3220
|
Screen Objects
|
The horizontal or vertical scroll bar would not always allow scrolling operations, when an window object type, such as the Alarm Window was not enabled with the "Show Control Window" option.
|
|
3342
|
ODBC
|
Using a parent project which included one or more child projects enabled with "Startable" and "Auto Startable", the parent project's log file would get saved in the LOG folder of the last child project initiated at startup. This would cause problems in Client-Server projects created with the parent-child technique, where the child project was not a local copy in the Client PC but the same Server project in the folder shared in network.
|
|
3500
|
Data Logger Management
|
The following error message would appear upon activating a commend to record a data logger:
"Internal Error in file ".\DBVarStat.cpp" at the line 147. Please contact the Technical Support".
This problem would only happen if bit or string type variables existed in the data logger that had been set to record statistical values not supported by those type of variables.
|
|
3543
|
Screen Objects
|
Window type objects enabled with the "Show Control Window" would not receive focus when an item was selected from their lists. As a consequence, the accelerators set in the object's buttons would not work because the object was not focused even though an item and been selected from its list.
|
|
3767
|
Screen Objects
|
The alarm window connected to a network Server would sort alarms into alphabetical orders even though requested to order into columns by date and time.
|
|
4307
|
Real Time DB
|
The "Transfer Value" command would not work correctly when indexing the start or destination variable. Practically, the whole variable value would get transferred and not the bit indicated by the command.
|
|
5930
|
Real Time DB
|
The daily, weekly, monthly and yearly statistics of a variable would not get zeroed correctly at project startup. Therefore the date statistics of long standing projects still had not been zeroed when run again. The only way to zero these statistics was to wait for midnight to come around.
|
|
5948
|
Screen Objects
|
The "Recipe Manager" object would not retrieve variable engineering data when connected to a network Server.
Note: In order for this object to connect to a network server, the recipe object needs to be present in the host project with connecting variables.
|
|
5977
|
User Interface
|
The timeout time set in the "Run Application" command was mistakenly considered as seconds instead of milliseconds as it should have been.
|
|
5978
|
Desing
|
Inserting a structure type variable in an expression or basic script code using the "Tag Browser" window, the variable would get entered using the point as a separation character between the structure and the member. However when this variable was not enabled with the intellisense option, its syntax was read as an error. Structure variables are now inserted in code or expressions using a normal syntax within square brackets. In addition, variables are inserted using their original names in cases where they have been renamed.
|
|
5933
|
OPC Communication
|
The OPC XML DA Server reconnection would not get managed correctly. As a consequence, when the connection was lost and then recovered, the variables remained in the "not good" state if the OPC XML DA Server did not send information about value change quality. In addition after reconnecting, variables would no longer get updated upon subscription, even though supported by the Server, but when in polling.
|
|
5946
|
Design
|
The refactoring window reported the child project variables used in the parent project's command list as being inexistent.
|
|
3984
|
Screen Objects
|
The shadow of an object within a symbol remained visible on screen when that element was made invisible in runtime.
|
|
3906
|
Real Time DB
|
The Audit Trail window used for inserting comments upon variable value changes would not use the variable engineering settings for formatting the required new value. Only the variable's current value would get displayed in the dialog window in the correct format.
|
|
3922
|
Design
|
The "Tag Browser" window would not display information on "Area Type" and "Address" for variables belonging to variable groups.
|
|
2828
|
Design
|
A variable used in a user's command list (or user group) appeared twice in the variable cross reference list.
|
|
3066
|
Screen Objects
|
An object set with animated movement returned to its original position each time the screen got resized. This would happen when the screen was enabled with its "Fit in window" option.
|
|
3592
|
Screen Management
|
The "close and return back" command would always open the project startup page when activated within a child project screen.
|
|
3711
|
User Interface
|
The Alphanumeric and Numeric Pad used for modifying structure variable members shoed only the name of the member and not the whole name of the variable. This would also happen with custom pads on screen where the name of the screen's "title_" local variable would be filled in with the name of the member only.
|
|
3407
|
Design
|
Setting a array variable in the "Not Shared" area would disable the "Address" field which should only disable for NON array variable types.
|
|
2561
|
Design
|
All the variables used directly in the project would obtain a "1" value instead of a "0" value, when running a basic script debug in design mode.
|
|
528
|
IMDB (InMemoryDB)
|
The XML file created by the InMemoryDB (IMDB) did not have a main root. As a consequence, it could not be opened with programs wanting a well formed file.
|
|
797
|
WinCE OS
|
The "DBVarObjCmdTarget" interface's"StatisticDataNumSamples" property would generate an "ActiveX Automation Error"exception in WinCE.
|
|
1767
|
Design
|
An undo command would reset the screen's currently applied zoom level. This would happened when the undo command was used to undo an operation performed after the current zoom level was applied. The zoom is now memorized for the undo-redo operations.
|
|
1905
|
Design
|
Opening the "Tag Browser" window, and selecting a variable with a right mouse click opens its popup property window. However when changing the variable's name and exiting with OK, the name of the variable in the "Tag Browser" window remained the same as before but changes to the values in its "Type", "Area Type", "Address", "Description" properties were refreshed straight away with the new ones in the "Tag Browser" window upon closure.
|
|
1906
|
Design
|
When selecting an object, the text size format combo box drop down list in the toolbar would not open or would open completely empty.
|
|
2420
|
User Interface
|
The string table could not be managed if the project file name contained the dot character and had the following anomaly:
-
Not all the columns would show when opening the string list even they had been inserted beforehand
-
Not all items would show when scrolling list object
When accessing the string list, the user was asked whether to create a column even though files relating to the columns already existed. When a new column was created, it would not remain permanent when string list was closed and then re-opened.
|
|
5044
|
Design
|
The "Tag Browser" window would display variables in the wrong groups. This problem would show in projects that had complex group structures where the names of some variables coincided with the same of some groups.
|
|
4467
|
WinCE OS
|
The alphanumeric pad '<-' key would not take into account the cursor's position and would always delete the last text character displayed. This problem would only happen when running projects in Windows CE.
|
|
4511
|
Design
|
The "Get Connected Device Screen Size" command would not ask if they wanted to scale the proportions of the objects to the new screen sizes.
|
|
5389
|
WinCE OS
|
Window type objects would always show the horizontal bar even when not necessary when displayed in Windows CE.
|
|
5414
|
Design
|
Associating an alarm to a symbol in the library, the variable set in the alarm threshold "Command-Status Variable" field did not get recorded in the library's template. As a consequence, this variable would not get added to the variable database, when the symbol was withdrawn from the library and inserted in a project.
|
|
5422
|
Screen Objects
|
The numeric and alphanumeric pad would display twice in cascade mode on screen in "Scheduler Window", "Recipe Manager" and "Grid" objects. This problem happened when the "Show Control Window" and "Prompt Pad" options were both enabled and the cell was edited using the keyboard and not the mouse click.
|
|
5440
|
DOM (Document Object Model)
|
The "PromptPad" property for reading or modifying the "Prompt Pad" option value of "Scheduler Window" objects was missing from the "HourSelectorCmdTarget" interface.
|
|
5474
|
Web Client
|
The Web Client would not support password style input data. As a consequence, when the a Movicon object was set to hide the edited value (i.e. a display "Password Style" option), the Web Client would display the inserted value instead of hiding it.
|
|
5475
|
DOM (Document Object Model)
|
It was impossible to find out whether the Variable TraceDB used the InMemoryDB (IMDB) or a ODBC connection. To remedy this problem a TraceUseIMDB" property has been added to the "DBVariableCmdTarget" interface as already exists for data logger and historical log basic interfaces.
|
|
5677
|
Screen Objects
|
An editable display set with a "Double (64 Bit double precision)" variable would only accept values limited to float (32 Bit single precision).
|
|
5624
|
Design
|
Setting a value that was not within the 1-100 limits in a screen's "WebClient quality" field would generate the wrong error message which had nothing to do with this value limit error but apparently referred to the project constraints instead.
|
|
5544
|
Design
|
Opening a project in design mode whose "AllowGradientFill" constraints had been set with the "false" value, all the properties concerning the Gradient management in objects or screens were hidden in the properties window when they should have been shown. All attempts to select gradient indexes by user failed.
|
|
5846
|
Design
|
The "Refactoring" window indicated any variable set in a screen "Screen Layer Variable" as missing.
|
|
5827
|
Design
|
The Cross Reference list did not list variables used in code, when the script used the "Uses" command for loading code from a public script.
|
|
5869
|
Basic Script
|
Not all of the expressions using a structure variable were considered valid by the expressions manager. This problem would arise when the structure variable's name or a member's name contained the underscore character, which was used in the syntax for defining which variable structure member to use.
|
|
5862
|
Design
|
The menu resource did not get marked for saving when modifying the title of a menu item directly from the project explorer window. As a consequence modifications would get lost when saving the project.
|
|
5885
|
Design
|
The Movicon message window "Don't ask me again" option did not work properly. This problem would happen when the message window asked for operation confirmation with "Yes" or "No". In this case when setting the "Don't ask me again" option" and confirming with "Yes", the "No" would get memorized instead. As a consequence, the confirm message window would no longer show for all following operations of the same type and the command would not get executed.
|
|
5929
|
ODBC
|
Creating the database would fail if the name of the project contained a space. This problem would happen when using "SQL Server", "MySQL" and "Oracle" ODBC Plugins.
|
|
5924
|
Design
|
The "Template Project" project creating wizard would not define some of the screen object font xml attributes. As a consequence, when running the project, some of the objects' texts would get displayed incorrectly (i.e. with letters rotated 90 degrees).
|
|
5716
|
Design
|
A vectorial drawing exported from Movicon then imported again would get drawn incorrectly. This problem would happen if the vectorial drawing was exported when the screen had its antialiasing active.
|