|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
5437
|
Screen Objects
|
Closing a screen opened in modal mode would send the Movicon application into error if running in a Tablet-PC with Windows VISTA.
|
|
5447
|
Screen Objects
|
The INSERT or UPDATE command of a grid object failed to work if the table's name included a space.
|
|
4299
|
Report Management
|
Movicon would raise and error and close when executing a "Textual Report" command. This problem would only show if certain formats were used that were invalid for the values recovered from a data logger or historical log.
|
|
4542
|
Basic Scripts
|
Un basic script would go into error if executed at project startup and contained the basic code '#uses' instruction, used for using the code of another of the project's basic script resources.
|
|
5265
|
Users Management
|
The wizard used for creating "Win32" projects would block the Movicon application in computers connected to a domain. This problem would not occur when the option for retrieving users from the local domain had not been set. In addition, the problem which made it impossible to use the "<UserName>@<DomainName>" syntax in project logon windows has been fixed.
|
|
5630
|
Screen Objects
|
The ActiveX objects which used "ComCtl32.dll" 5.x versions, would not get managed correctly in runtime, because Movicon would only instantiate the "ComCtl32.dll" 6.x. versions. This problem started happening with the Movicon build 11.0.1017.
|
|
5480
|
Tools
|
The print margins set in the printer's selection dialog window (parameter -d), would not get used if the tool was called from Windows CE.
|
|
5484
|
Design
|
Setting the option for encrypting project resources, would not crypt them until they were modified. This problem started happening with the Movicon 11.0.1017 and 11.1.1053 builds.
|
|
5485
|
ODBC
|
Recording through the ODBC would cut off string values to 255 characters even though the limit had been increased to a higher value in the project object's properties.
NOTE: Some DBMS (see MS Access) may however have a limit of 255 character bytes for "nvarchar" fields that Movicon creates.
|
|
5500
|
ODBC
|
Reading string type data through the ODBC would get limited to a max of 2048 character bytes. Now this limit can be increased by modifying the "ODBCMaxReadingChars" DWORD value in the "General" key of the Windows configuration registry.
|
|
5541
|
Screen Objects
|
The "light" objects with Clickable properties would use up memory upon each click.
|
|
5641
|
User Interface
|
A project would startup with a blank screen in Windows VISTA, or higher. This problem would occur when project was sent directly into run mode and did not use the option for adapting screen to Movicon window.
|
|
5648
|
OPC Communication
|
Reconnecting to an OPC Server DA would fail. Each item that had to be reconnected showed the following message in the output window:
A duplication of the "x" item has been found for the "X" variable"
This problem starting happening with the Movicon build 11.0.1017.
|
|
5699
|
License
|
The software key management would occupy CPU equal to 100%. This problem would show in computers configured as ELM Servers. The components that occupied 100% of the CPU were visible in the Windows task manager window with the "crp32002 ngn" name.
|
|
5736
|
Screen Objects
|
The trend or data analysis object print command, contained always in memory within the screen and enabled with the adapt to window size option, would cause a graphical problem with viewing the trend object, when the screen was re-displayed for a second time where the trend's sizes would not tally with the screen sizes.
|
|
5751
|
Screen Objects
|
Polygons within an embedded screen object would not always get positioned correctly when the screen containing them got readapted.
|
|
5732
|
Screen Objects
|
When selecting a row in the Alarm window, it would turn blue with black text, making it very difficult for the user to read the alarm/message text.
|
|
5678
|
Screen Objects
|
When displaying a pen, the data represented by the trend would not tally with the time filter in use. This problem would occur if the analysis was initially carried out without the pen displayed but displayed afterwards.
|
|
3283
|
Design
|
When Movicon launched an external executable in Windows Vista with the UAC enabled, Windows PCA (Program Compatibility Assistance) would intervene impeding the tool's execution. This resulted generated message would mislead the user to believe that the file hand not been found when in fact this was not the case.
|
|
3515
|
Networking
|
When a project network server was started up as service, it became impossible to use the local protocol for connecting client projects. This problem only occurred in Windows VISTA or Windows 7.
|
|
4391
|
WebClient
|
Publishing a data logger on data web pages with the appropriate command, a problem would occur with the data filter selection controls when using a browser that was not of the Internet Explorer's. Data could be selected, but that last bit of data chosen would not get displayed in the control.
|
|
5357
|
WinCE OS
|
In a "Textual Report" command, the data field format would not produce valid values when the separation character of the data set in the international options was a point (i.e. German).
|
|
5373
|
Documentation
|
the Movicon tutorial file in German had an English heading.
|
|
5259
|
License
|
A delay in reading the USB hardware key in Windows 64 bit operating systems would make Movicon take a long time in starting up.
|
|
5799
|
Design
|
Selecting a menu in a control or command list, would not always set the command using the menu's original name if menu had been renamed beforehand.
|