44 Version A.05.01.b

44.1 Windows

• New: Microsoft Development Environment .NET 2003 projects have been added to the examples of the IDM version for Windows XP. In the course of this change the Microsoft Developer Studio 6.0 projects were also removed from this version.

  The IDM-Version for Windows NT still contains the Microsoft Developer Studio 6.0 projects.

• New: The text of an image object can now contain more than one line.

  Attention

  When height = 0 the number of text lines for the height adjustment of an image object on the tile resource is not taken into consideration.

• New: The poptext object now supports the automatic sorting of content under Microsoft Windows. The sorting is carried out by Microsoft Windows. The only thing that changes is the presentation of the order; the indexes (.text[I]) remain the same. The attribute .options[opt_sort] determines if the content should be sorted or not. Generally, the attribute is set to false. If sorting is desired, the attribute must be set to true.

  In this way the standard behavior of Microsoft Windows is better supported with respect to a poptext object, which prerequisites an sorted content.

• New: The treeview object now supports the setting of text color (.fgc). As a result, the appearance of existing dialogs can change.
• New: Internal tiles now display the actual background color with the characters "." and " ". If this is not desired, then the desired color can be changed through the attribute .imagebgc on the object image.
• Gnats 9760: During the destruction of a grouping object (groupbox, notepage, etc.), the focus was not forwarded correctly. This error has been corrected.
• New: Gnats 9728: The statictext object (Windows XP version) now also supports Visual Styles. As a result, the background of a static object in the XP version is the same as the background of a notepage father object.
• New: Gnats 9677: The attribute .toolhelp now supports multiline texts.
• The method :getformat() of the edittext object (.options[opt_rtf] = true) returned nothing under the non-unicode capable Microsoft systems. The error existed in idmuni.dll and has been corrected.
• Sometimes it was not possible to use a parameter, that contained a space, for example by the definition for an OLE server.
• The size of a non-optional scrollbar slider was not correctly reset after the size of a window had been interactively changed. One could see, for example, that after the object affected was made visible or invisible the size of the slider had also changed.
• Through an interactive changing of the window size, the maximum size of the window was not taken into consideration.
• The size of maximized MDI children windows was not correctly adjusted when the size of the father window was changed or when toolbar objects were docked or undocked.
• Gnats 8669: The examples have been adapted to run on pidm.exe. They are now executable with a dedicated P-license (porting license).
• Gnats 9760: The focus is now set correctly after the destruction of a grouping object (groupbox, notepage, etc.). In some cases this can be very time consuming in its use.
• Gnats 9741: The method :setformat() on the edittext object (.options[opt_rtf] = true) did not function correctly. This problem was caused by Gnats 9672. Please take note that the setting of a format on the insertion mark (startsel = endsel) can only take place during runtime (.visible = true), and is only temporary. This is a characteristic of a Microsoft Windows object, which unfortunately cannot be avoided. Please also take note of the comment for repairing Gnats 9672, which is noted further on in these release notes.
• Gnats 9733: An Assfail in object/slot 2284 was possible when a poptext object with .style <> poptext had the focus and one of the keys Tab, F4 or Esc was pressed. In addition, a combination of the modifier keys also had to be pressed so that the button was not processed by IDM. In this reported case, this happens for the Tab key and the modifier keys Alt and Ctrl.
• Gnats 9730: When a maximized window was made visible, it possessed the maximized condition (this could be seen on the buttons in the title line), but it obtained the normal size.
• Gnats 9723: The checkbox, radiobutton and statictext objects now use the same background color as the father object when no other background color has been set. Up to now the system background color for 3D objects was used in this case.
• Gnats 9723: Docked toolbar objects were covered from the work area in MDI father windows.

• Gnats 9718: Because the IDM does not support multiple indexed attributes, you have to use methods with parameters to take advantage for OLE properties with multiple indexes.

  Instead of (not valid in the Rule Language!)

  control.Prop["a"]["b"] := "x";

  print control.Prop["a"]["b"];

  the following syntax in the IDM Rule Language must be used:

  control:Prop("a", "b", "x");

  print control:Prop("a", "b");

  Sometimes the method name is altered by a "Set" or "Get" at the beginning:

  control:SetProp("a", "b", "x");

  print control:GetProp("a", "b");

• Gnats 9706: When an area within an edittext object, that had an empty format was to be marked from left to right, then the last letter remained unmarked. This problem only happened when the cursor was moved by more than one letter at a time (movement with Shift + Home or Ctrl + Shift + Cursor Left). This problem did not occur when a format (was empty) or no format was set.
• Gnats 9705: When the trace file could not be opened, the application was ended. This lead to the problem that the simulation was not able to be started from the editor when the surrounding variable IDM_TRACEFILE was set to a fixed filename. Now, the application continues to run without tracing after showing an error message. In addition, there is now an additional space holder "%A" for entering the name of the log or the trace file. For additional information please refer to the chapter entitled Core.
• Gnats 9698: The setting of a cursor for the entire application (setup.overridecursor) was not reported to the statusbar and toolbar objects. Due to this, an Assfail in object/slot 2283 occurred in some cases.
• Gnats 9696: Under Windows 95 additional menus can’t be created.

• Gnats 9680: The Microsoft Windows poptext object does not discern between capital and small case letters. Due to this it was possible, that an incorrect entry was displayed when the poptext object contains identical texts which only differs in upper/lower-case characters.

  Note for Windows 95

  This problem can not be avoided in Windows 95.

• Gnats 9673: The treeview object draws a set background color (.bgc) only where no text existed. In order to correct this error comctl32.dll version 4.71 or higher (beginning with Internet Explorer 4.0) is needed.

• Gnats 9672: When the method :setformat is used on an edittext object that has .options[opt_rtf] = true, and when the attributes .startsel and .endsel or the parameters Start and End have the same value, then the edittext object throws out the format setting when a change is made to .endsel. This also happened when one of the methods, which had .options[opt_rtf] = true for an edittext object, was called up with the parameters Start and End. This can now be avoided. The above-mentioned standard behavior of the Windows object remains the same.

  Note

  • Method :setformat()

    A format setting made to the insertion marker (.startsel = .endsel or Start = End) is only temporary. The applied format remains valid up to the point where .endsel is changed. Here, it makes no difference if .endsel is changed by the user or through the dialog script. This is the reason why a format setting where Start = End has no effect when Start <> .startsel and End <> .endsel. In the last mentioned case, the method :setformat() returns a faulty value. In addition, it is important to know that a format setting on the insertion marker is not assumed in the RTF-text and as a result remains ineffective when it is carried out on an object that is invisible at that moment.

  • Attribute .content and Method :gettext()

    The RTF-text is changed by the object itself (not formatted). It exists only logically. In other words, for example, a letter is cursive and bold – but the order of events of a change in format (first cursive and then bold or vice versa) can change.

  • The use of the parameters Start and End

    If one of the following methods :findtext(), :getformat(), :gettext(), :replacetext() and :setformat() is called up with the Start and End parameters, take note, that the marked area remains as it was, but that the insertion marker located to the right of the marked area can be slightly shifted out of place.

• Gnats 9671: When a invalid tile resource, was applied to an attribute, then the attribute was handled incorrectly - as if no tile resource was applied to it. Now the attribute is regarded as being set.

  Example

  The tile resource TInSens refers to the GIF file "NotExisting.gif", which does not exist. This resource is allocated to the attribute .picture[tile_insensitive] of an image object. When this image object is set to insensitive, then the image object will be filled with the background color; previously .picture[tile_default] was indicated.

• Gnats 9652: Filerequester dialogs (filereq object) no longer functioned under Microsoft Windows 98. The problem was, that an incorrect size was set in idmuni.dll.
• Gnats 9639: When a poptext object with .style = edittext contained a number of entries that began with the same characters, then, after opening the list, the first entry and not the entry that corresponded to the active item was marked. Unfortunately, since this is the standard behavior of the poptext objects under Microsoft Windows which cannot be changed. However, an event (select or activate depending upon .options[opt_old_select]) is created when the .activeitem attribute is changed when it is opened. The content of the .content attribute remains the same in this case.

  Note for Windows 95

  This problem cannot be recognized under Windows 95. As a result no event is fired.

44.2 Unix

• The examples in IDM.EXAMPLES now use the pidm, as a result these are also compilable with a P-license (porting license).

  Attention

  Beginning with A.04.01.a, the P-license is only delivered with the pidm and no longer with idm. Now, pidm is a part of every IDM license.

44.3 Motif

• New: Under Motif1.2, as with Motif2.1, a consistent way for making pop-up menus visible has been established. By activating the menu buttons, the visible pop-up menu (.visible set to true) of the topmost sensitive object is displayed. This is analog to Windows with only one exception: under MS Windows insensitive pop-up menus behave like "invisible" ones.
• Gnats 9764: The predefined value of width and height of a rectangle object is now again 0/0.
• Gnats 9746: The &-character (mnemonic-character) was not handled correctly by the listbox, treeview, poptext and filereq objects.
• Gnats 9740: Maximized windows are now completely visible including all of its decorations.
• Gnats 9737: The initial size of windows with menu bars is now again correct.
• Gnats 9715: Falsly activation of the Notepage below the mouse pointer corrected when pressing ALT-TAB to switching between windows.
• Gnats 9713: When an element of a treeview is activated via the setting of .activeitem now the father element is correctly opened and its activation is guaranteed.

• Gnats 9708: Making a dialogbox visible under certain Window Managers was sometimes delayed. In addition, corrections needed to be made, which also had an effect on the process of the window size/position with respect to the interaction with the Window Manager.

  Peculiarities of the window object under Motif

  The position values (.xleft, .ytop, etc.) refer to the outer coordinates of the window. Window Manager or desktops with panels normally carry out a correction of the position/size themselves in order for the panels to remain visible. This is reflected again in the position - this can be seen in relation to the whole screen. Very few and rare Window Managers, for example TWM, do not allow IDM to determine the position of the window including its decorations. This leads to windows moving when they repeatedly switched from a visible to invisible status.

• Gnats 9620: Attributes .xmargin and .ymargin has been added to the edittext object.

  These attributes (type integer) determine the space between the outside edges and the text in pixels. Changes to the margin values have an effect on the spacing to the upper and left side. When .height = 0 or .width = 0 and .yauto <> 0 or .xauto <> 0, then this can effect the other two sides.

  Please take note, that the default values of these attributes with other WSI's (i.e. Windows) are different. The value range is -127 … +127. The default value for Motif is 5, for Windows 1.

  Windows-WSI supports .xmargin since A.03.07.c, but not .ymargin.

• Gnats 9665: Workaround for Solaris/Motif errors when working together with a different X-display. Pop-up menu now opens itself with Solaris-IDM on a non-Solaris X-display.
• Gnats 9662: Warnings by the creation or selection of notepages in the editor have been removed. Crashes, which occurred when notepages where made invisible under Suse, no longer occur.

44.4 Core

• New: An additional space holder %A has been introduced for using the application name in the log or trace filename.

  %A is replaced by the application name. Under Microsoft Windows the ending ".exe" is removed from the name.

• New: DM_LoadDialog now interprets the character "~" (i.e. "~:" in place of "MOD:"). Now a dialog, which is stored in the same folder as the application, can be found without a problem.
• Gnats 9735: When the format codepage was not UTF8, then no umlaut was displayed in an edittext object with format. Instead two characters were displayed. This error was caused by the correction of Gnats 9695 and has been corrected.
• Gnats 9724: The use of path variables when writing, for example, interface files now functions correctly in version A.04.04. This means if the file is not in the path, then the first path is placed at the beginning of the variable.
• Gnats 9711: Binary writing no longer breaks down in the path resolving over the master import.
• Gnats 9709: When reading dialogs with reposid(), loading isn’t aborted but the reposid information is rather read over.
• Gnats 9697: The start order of modules, which changed after Gnat 9577 was corrected, has also been taken care of.
• Gnats 9695: applyformat() with format string now also works correctly when AppFormatCodepage!=CP_internal.
• Gnats 9658: Setvalue on .content on a poptext is now also possible in a :init-Rule.
• Gnats 8697: A static assignment to a path-ID (forward reference to an object) on a shadow attribute resolves the path-ID now correct.

44.5 Editor

• Gnats 9721: Split areas remember their size even when they are closed for a short period of time.
• Gnats 9719: When selecting objects in the design area the active element within the browser is moved into the visible area.
• Gnats 9716: No more external windows are shown when a window is created in the editor and no default window exists.
• Gnats 9714: The interactive selection of a notepage within the editor makes these active.
• Gnats 9589: Under Microsoft Windows, objects which possessed raster coordinates, were partially shifted when their size was reduced or enlarged. This problem no longer exists.

44.6 Network

• Gnats 9712: The DDM for Java-WSI is now also able to process asynchronous Ext-Events from the server side.

44.7 COBOL Interface

• Gnats 9710: Strings by DMcob functions are correctly interpreted during tracing actions in the correct code page.