OS/2 Shareware BBS: 29 Fixes

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Shareware BBS: 29 Fixes_o / 29-Fixes_o.zip / vacppcsd.exe / CTV305.LST < prev next >

Wrap

File List | 1997-01-02 | 53KB | 787 lines

**************************************************************************** * VisualAge C++ For OS/2 Version 3.0 * * Compiler Subcomponent * * Fixes List * **************************************************************************** * * * This fixpak contains fixes that apply only to VisualAge C++ Version 3.0 * * The fixpak must be applied using the provided installation tools. * * * **************************************************************************** Fixpak CTV305 is Informal Corrective Service * **************************************************************************** The following items are new to CTV305 ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------- QI-21112 DAX Installation of CTV303 or higher hangs on Warp4.0. This fixpak does not hang. ------------------------------------------------------------------------------- 8349 VB PIE to Class Editor transition doesn't take place completely on Warp4.0. ------------------------------------------------------------------------------- 8023 VB Out of control VBB growth with Event to code connections problem has been fixed. ------------------------------------------------------------------------------- 8214 VB Add /Ft- support to OS/2 IVB template classes. ------------------------------------------------------------------------------- 5208 VB Cannot use keyboard to turn pages of the PIE. ------------------------------------------------------------------------------- 4898 VB selectedCnrElement attribute of IVBContainerControl does not work. ******************************************************************************* The following items are new to CJV304 ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------------- QI-20524 DAX The select & refresh methods in the generated <class>Manager were slow. Notification has been disabled to speed up these methods. The following items are new to CTV304 ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------------- 20089 DAX An assertion failure occurred when loading a .dax file that contained a class name with an embedded space. ------------------------------------------------------------------------------- 61280 DAX Generated dllname in IDL did not match the filename and the name of the dll that would normally be created from that filename. ------------------------------------------------------------------------------- QI-19943 DAX Invalid class or attribute names were not always detected resulting in generated code that would not compile. ------------------------------------------------------------------------------- QI-20053 DAX The generated asString method was using the old value of an attribute after the attribute had been set to null. It now knows the attribute is null. ------------------------------------------------------------------------------- QI-19266 DAX Keyboard arrow keys did not control the scroll bars correctly on the main screen. ------------------------------------------------------------------------------- QI-19471 DAX Calling the generated setAttrnameToNull with "false" as a parameter resulted in an exception if the column from which the attribute was mapped is non-nullable. No excpetion is now thrown. ------------------------------------------------------------------------------- QI-20055 DAX IVBDatastore did a local log on. It now does not. ------------------------------------------------------------------------------- QI-19960 DAX The generated comparison operators ==, != and < on on the generated persistent object class were incorrect. ------------------------------------------------------------------------------- QI-19356 DAX In the SOM generated code, the release order incorrectly contained inherited methods. ------------------------------------------------------------------------------- QI-20033 DAX Attribute notifications were sent before the values were set, thus there may have been a timing problem. ------------------------------------------------------------------------------- 53555 DAX Some SOM header files were not including somcls.idl. This resulted in compilation errors in the generated code when CTT301 is installed. ------------------------------------------------------------------------------- QI-18740 DAX A long varchar or long vargraphic used as a data identifier resulted in generated code that did not compile. The types are no longer valid data identifiers. ------------------------------------------------------------------------------- QI-20029 DAX Notification for isNull was not sent by the "=" operator. ------------------------------------------------------------------------------- QI-20002 DAX Notification id for the isNull attribute of a data identifier was not generated, causing compilation errors in the generated Visual Builder code. ------------------------------------------------------------------------------- QI-19095 DAX The "clean" option in the generated makefile had an incorrect library name if the dll name is changed. ------------------------------------------------------------------------------- QI-18684 DAX If a non-nullable column was not in the mapping, Data Access Builder trapped. ------------------------------------------------------------------------------- QI-18872 DAX The notification mechanism used by the refresh method in the generated code was very slow. ------------------------------------------------------------------------------- QI-19138 DAX An undocumented exception was thrown when a system timeout occurred. No exception is now thrown. ------------------------------------------------------------------------------- QI-19645 DAX Data Access Builder did not exit gracefully if "Error creating Narc window" is encountered. It now exits gracefully. ------------------------------------------------------------------------------- QI-20022 DAX Use of the copy constructors in the generated code resulted in unpredicatable behaviour. ------------------------------------------------------------------------------- QI-20032 DAX From within the Visual Builder, overriden methods on classes derived from IDatastore could not be be called. ------------------------------------------------------------------------------- 51165 DAX Unrecognized DB2/2 v2.1 types caused incorrect code to be generated. Columns with unrecognized types are no longer in the mapping. ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------------- QI 4620 VB Passing the text of menu items from the primary window to a secondary window via a factory object resulted in generated code that did not compile. ------------------------------------------------------------------------------- QI 4650 VB The client area of a frame window is blank at runtime when a viewport (the client) with a multicell canvas is used. ------------------------------------------------------------------------------- QI 4737 VB If the window Id is specified as a constant on the settings editor of a menu item, then the generated code does not compile (if there is a connection sourced from this menu item). ------------------------------------------------------------------------------- QI 4880 VB The base class LIB file is not included in link step of generated make file. ------------------------------------------------------------------------------- QI 5015 VB Problems with the way contructors and the initializer list for constructors was being generated. ------------------------------------------------------------------------------- QI 5134 VB Code gen: Tear-off attributes were not being initialized. ------------------------------------------------------------------------------- QI 5135 VB Custom logic connection to an objectFactory not generated. ------------------------------------------------------------------------------- QI 5214 VB The IContainerColumn settings editor does not allow specification of attributes that are type 'IPointerHandle' (or other types not in the predefined list). ------------------------------------------------------------------------------- QI 5215 VB The Visual Builder handlers get generated out (new'ed and its events handled) after the user's handler. IOC invokes the handlers in a LIFO order. So, the Visual Builder's handler was getting called before the user's handler which prevents any other handlers from being invoked. ------------------------------------------------------------------------------- QI 5289 VB Variable's THIS attribute doesn't promote correctly from the Part Interface Editor's Promote page. ------------------------------------------------------------------------------- QI 5290 VB Runtime error when changing action in Event->Action connection with parameters. ------------------------------------------------------------------------------- QI 5407 VB Help does not work for third frame window in a chain of three windows that have a help button on each window. ------------------------------------------------------------------------------- QI 5409 VB If there are two paths to opening the same part window via factories, this causes a problem if that window has help associated with it since only one of the window IDs will be used in the help table. ------------------------------------------------------------------------------- QI 5442 VB Because of timing problems, there are times when the minimal size of a canvas is not set soon enough and problems ensue. ------------------------------------------------------------------------------- QI 5493 VB VBPalet.Dat is not pulled from the same directory as it was stored. ------------------------------------------------------------------------------- QI 5534 VB Compile errors when using a menu as part of a menu bar and as a popup with a menu item that has custom logic. ------------------------------------------------------------------------------- QI 5819 VB Runtime error occurs when you 'file-->Save as' and then 'file-->Save & generate'. ------------------------------------------------------------------------------- QI 5823 VB After defining an attribute in the Part Interface Editor, and setting it using the settings editor on the free-form surface, the value is not included in the generated code. ------------------------------------------------------------------------------- QI 5842 VB Cannot connect THIS of frame window to owner of a factory. ------------------------------------------------------------------------------- QI 5944 VB In the .app file if part ctor fails, the iPart pointer is invalid, however it is later referenced in iPart->setAuto.. and show(). ------------------------------------------------------------------------------- QI 6205 VB Notification failure on derived class of IEntryField. Using a part (derived from IEntryField) in another part the notification fails to work on the second instance of the derived part in the compositio editor. ------------------------------------------------------------------------------- QI 6499 VB StartingResourceID and VBBASEWINDOW will not reset (return to default) after turning off the StartingResourceID. ------------------------------------------------------------------------------- QI 6568 VB User .rcv files are included with #rcinclude rather than #include. ------------------------------------------------------------------------------- QI 6655 VB Internal: definingClassName in attribute spec not renamed when the part is renamed. ------------------------------------------------------------------------------- QI 6781 VB Complex notebook page causes msg queue overrun in composition editor. ------------------------------------------------------------------------------- QI 6829 VB Change the actual menu name on the Composition Editor when the menu part name is changed (ie. allow changing 'menu2' to something more meaningful like 'File'). ------------------------------------------------------------------------------- QI 6938 VB Remove "Custom logic" from the Connections pop-up menu ------------------------------------------------------------------------------- QI 7139 VB Invalid (Smalltalk) events are showing up on Preferred page of the Part Interface Editor. ------------------------------------------------------------------------------- QI 7311 VB Paste with Sticky has problems. ------------------------------------------------------------------------------- QI 7475 VB CE: IRange shows as a Smalltalk interface. ------------------------------------------------------------------------------- QI 7512 VB The CE allows dropping a ContainerColumn onto the Container. It shouldn't do this. What happens is no column is visible, and a runtime error occurs. ------------------------------------------------------------------------------- QI 7598 VB Specifying a #xxxxx for the notebook tab text on a notebook page will cause a runtime error. ------------------------------------------------------------------------------- QI 7734 VB The .rcv file in the Doodle sample application needed a #ifndef statement to compile successfully. ------------------------------------------------------------------------------- QI 51522 VB Open parts added from WorkFrame ------------------------------------------------------------------------------- QI 51926 VB Nested template parm on action does not parse. ------------------------------------------------------------------------------- QI 51974 VB VB hangs when defining an operator action in the Part Interface Editor. ------------------------------------------------------------------------------- QI 51974 VB DBCS Fix for DBCS Attribute Types, and DBCS Unknown... ------------------------------------------------------------------------------- The following items are new to CTV303 ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------------- QI 50858 VB In CTV302, VB would report a runtime error ("AbtEventSpec does not understand 'ready'") when generating parts that were created by Project Smarts and had connections to the 'ready' event. ------------------------------------------------------------------------------- QI 50859 VB In CTV302, VB fixed the handling of parameter names when attributes were being treated like actions (see QI 4238) which could result in parameter connections and constant parameter values that were no longer correctly named. CTV303 adds a migration function to automatically update the names so that there will be no breakage of existing parts. ------------------------------------------------------------------------------- QI 50106 VB VB read its saved preferences file (vbopts.dat) and changed the working directory before loading vbbase.vbb and the files from vbload.dat. vbb files kept in the startup directory were then not found because the startup directory was no longer the current directory. ------------------------------------------------------------------------------- QI 49990 VB Specifying DBCS constant parameter values resulted in errors during generation. ------------------------------------------------------------------------------- QI 47450 VB In the settings editors, you could not specify a fixed pitch outline font, ------------------------------------------------------------------------------- QI 5129 VB In CTV302, generation failed for subclasses of template based classes (eg. IVBContainerControl) that had promoted features. ------------------------------------------------------------------------------- ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------------- QI-18378 DAX The generated makefiles did not use the /Sn+ option on DBCS machines. It will now do this. ------------------------------------------------------------------------------- QI-18389 DAX The generated host variables were not static, possibly causing a naming collision at link time if different tables had the same column names and all the code for different tables were being linked together. The host variables are now declared to be static. ------------------------------------------------------------------------------- QI-18021 DAX SDMSCON.IDL did not include SOMCLS.IDL which caused an error in the IR emitter if it is used. SDMSCON.IDL now includes SOMCLS.IDL ------------------------------------------------------------------------------- QI-18387 DAX The SQLPREP WF action did not support .SQX files which are supported by DB2/2 V2.1. It now recognizes .SQX files. This allows you to imbed SQL in C++ source files and integrate them with your applications via workframe. The following items were provided in CTV302. ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------------- QI-17315 DAX DB2/2 V2.1 was not supported. This CSD allows Data Access Builder to work with both DB2/2 V1.2 and V2.1. Generated code compiled with DB2/2 V1.2 runs on DB2/2 V2.1. ------------------------------------------------------------------------------- QI-17360 DAX DBCS was not properly supported: DB2/2 GRAPHICS types was not supported, DBCS characters were displayed as blanks in various places, and DBCS table and column names caused incorrect code to be generated. ------------------------------------------------------------------------------- QI-17502 DAX The generated makefile failed when running SQLPREP from DB2 SDK/2 V1.2 for remote RS/6000 databases. ------------------------------------------------------------------------------- QI-17232 DAX Non-text characters were intermittently embedded in the generated SOM IDL file. ------------------------------------------------------------------------------- QI-17432 DAX The Datastore destructor was disconnecting even if there was no connection. ------------------------------------------------------------------------------- QI-17368 DAX If the class name is changed in the class settings notebook, the "Part method" page of the notebook was not updated. ------------------------------------------------------------------------------- QI-17412 DAX Long varchar attributes were incorrectly truncated when the attribute is set. ------------------------------------------------------------------------------- QI-17399 DAX There was a security problem in that a dump of the control block would have revealed the database userid and password stored in the Datastore class. ------------------------------------------------------------------------------- QI-17525 DAX IDSConnectCanvas had same security problem as QI-17399 in VBDAX.VBB. ------------------------------------------------------------------------------- QI-17404 DAX No exception was thrown when disconnecting without connecting first. ------------------------------------------------------------------------------- QI-17354 DAX The target directory displayed was incorrect when generating code under WorkFrame. ------------------------------------------------------------------------------- QI-17544 DAX Non-nullable columns were not retrieved correctly in code generated for SOM. ------------------------------------------------------------------------------- QI-17544 DAX The IsNull attribute for non-nullable attributes was not initialized in the .cpp generated for SOM. Therefore, it could contain an incorrect value. ------------------------------------------------------------------------------- QI-17323 DAX The database samples would not run under DB2/2 V2.1. There were also various other minor defects with the database samples. ------------------------------------------------------------------------------- QI-17880 DAX The Visual Builder was enhanced in CTV302 requiring the DAX samples to change. ------------------------------------------------------------------------------- QI-17881 DAX The generated code has methods to convert numeric types to IStrings that were not exposed to the Visual Builder even though the Visual Builder works best with IStrings. The generated code now allows the Visual Builder to access these methods. ------------------------------------------------------------------------------- ******************************************************************************* FIX/APAR COMPONENT PROBLEM_DESCRIPTION ------------------------------------------------------------------------------- QI 41981 VB Controls with code strings for labels will now show the code string instead of a very small control. ------------------------------------------------------------------------------- QI 42083 VB Entry Fields whose contents should only be SBCS no longer accept DBCS. ------------------------------------------------------------------------------- QI 42252 VB Mixed DBCS/SBCS directory/file names no longer need to be fully specified. ------------------------------------------------------------------------------- QI 42501 VB VB terminated if a FrameWindow had a code string title. ------------------------------------------------------------------------------- QI 43682 VB VB terminated if intitial text for a MultiLineEditor field was erased in the settings editor. ------------------------------------------------------------------------------- QI 4245 VB Use of IVBDragDropHandler caused an unresolved external because the constructor of IVBDragDropHandler was exported incorrectly in the cpp. ------------------------------------------------------------------------------- QI 4256 VB VB had a runtime error when an invalid DLL was specified on an IBitmap control. ------------------------------------------------------------------------------- QI 4288 VB IVBFlyText threw an exception when the app was closed via the system menu. ------------------------------------------------------------------------------- QI 4299 VB Parameter names are required in member function signatures, but the validation code did not flag cases where the parameter name was missing. ------------------------------------------------------------------------------- QI 4304 VB The IBaseListBox and IBaseComboBox parts were missing the event selectId for the numberOfSelections attribute. ------------------------------------------------------------------------------- QI 4306 VB A slightly downlevel version of VBSAMPLE.VBE was shipped. This version had invalid 'value' attribute definitions for IVBShortPart and IVBUnsignedShortPart. There was no parm on the setter. The VBSAMPLE.VBB file was correct. ------------------------------------------------------------------------------- QI 4385 VB The selectedCnrElement attribute of IVBContainerControl refered to a getter that did not exist. ------------------------------------------------------------------------------- QI 4423 VB If a Bitmap or Icon, or the dll requested for the Bitmap/Icon is not found, VB will now use a default. This is in both on the constructor and in setResourceId. The default bmp/icon is id=15038 in dll=dde4vr30. ------------------------------------------------------------------------------- QI 4453 VB IVBContainerControl was missing a color page in the settings editor. ------------------------------------------------------------------------------- QI 4552 VB When a non-visual part is created inside the visual builder with parts and connections on its composition editor, and another similar non-visual part inherits from that part, the child class's generated initializePart member function should first call its base class's initializePart function and then do it's own initialization. Previously, the call to the base class's initializePart function was left out. ------------------------------------------------------------------------------- QI 4559 VB VB reported a runtime error when QuickBrowse was invoked against a part without a .cpp file. The menu selection will now be disabled. ------------------------------------------------------------------------------- QI 4560 VB The message 'DDE4.GEN.6.e:' had '?' instead of the part name. ------------------------------------------------------------------------------- QI 4568 VB The title in the Composition Editor and other editors was incorrect after the user performed a saveAs. ------------------------------------------------------------------------------- QI 4561 VB SYS3175 with promoted variable attribute. Code was added within connections to promoted variables which checks to see if the target is null before referencing through it. ------------------------------------------------------------------------------- QI 4569 VB Class Interface parts could not be promoted correctly, resulting in compile errors. ------------------------------------------------------------------------------- QI 4565 VB 'actionResult' will no longer be on the connection popup when there is no action return type defined. ------------------------------------------------------------------------------- QI 2871 VB Mnemonics were lost when pushbutton text was updated via direct edit. ------------------------------------------------------------------------------- QI 3394 VB A composite parts size was fixed when added to another part, and did not change when the part was updated. It will now update, unless it has been specifically set where it is being used. ------------------------------------------------------------------------------ QI 4582 VB Empty string tables could be generated in rci files when all strings had been erased, causing resource compile failures. ------------------------------------------------------------------------------- QI 4576 VB If you renamed a part to 'x', then unloaded the part, VB would not let you rename another part to 'x'. ------------------------------------------------------------------------------- QI 3951 VB You could enter invalid part names in the settings editor. ------------------------------------------------------------------------------- QI 4024 VB Source/Target buttons did not enable the Update button in the custom logic dialog. ------------------------------------------------------------------------------- QI 4042 VB Generation will now report an error and stop when it encounters a menu that is not connected to anything. Previously this was reported as a warning, although it caused a subsequent error message that stopped generation ------------------------------------------------------------------------------- QI 4078 VB You can now explicitly set the windowId of a menu item in the settings editor. ------------------------------------------------------------------------------- QI 4101 VB VB kept a write lock on a vbb file after a failed load of the file. ------------------------------------------------------------------------------- QI 4109 VB operator char* was not parsed correctly in member function signatures. ------------------------------------------------------------------------------- QI 4110 VB Subpart .rci files were not always included. They will now be included if the subpart is compilable (has a .cpp, but no lib file specified). ------------------------------------------------------------------------------- QI 4112 VB PIE: Action page- a blank 'Return type' field got filled in with the action function return type on an Update. This results in potential connections to actionResults that will not compile. ------------------------------------------------------------------------------- QI 4116 VB Custom logic connections can now be used to satisfy parameter values of event-action connections. ------------------------------------------------------------------------------- QI 4118 VB The help information was not correctly linked on some settings pages. ------------------------------------------------------------------------------- QI 4122 VB The help information was not correctly linked on some context menu items. ------------------------------------------------------------------------------- QI 4131 VB When VB generates the .mak file, a part's base classes are now searched for libraries to include in the link. ------------------------------------------------------------------------------- QI 4159 VB The generated code for a notebook page that had no control on it (i.e. the canvas put on by default was removed) was invalid. ------------------------------------------------------------------------------- QI 4174 VB An exception occured in loading the accelerator table for windows created from a factory. ------------------------------------------------------------------------------- QI 4175 VB The Help button on a settings editor Styles page was disabled after the Apply button was selected. ------------------------------------------------------------------------------- QI 4178 VB If you deleted the client canvas from a notebook page, and then dropped a Viewport, Set Canvas, or Split Canvas, you were unable to drop anything else on that notebook page until you clicked on some other part of the notebook, such as the tab. ------------------------------------------------------------------------------- QI 4192 VB You could not save a part if Help or How Do I? was active. ------------------------------------------------------------------------------- QI 4202 VB On a multicell canvas, if a change to a part required re-construction, the part did not show. ------------------------------------------------------------------------------- QI 4203 VB Blanking out IResourceId and/or dllname fields in the settings editors resulted in compile errors. ------------------------------------------------------------------------------- QI 4207 VB Tear-off attributes are only supported for types that have default constructors. Attributes of types without default constructors will no longer be shown in the tear-off list. ------------------------------------------------------------------------------- QI 4211 VB Could not specify a help id for cascade menu items. ------------------------------------------------------------------------------- QI 4228 VB VB reports a runtime error during generation of a String ListBox whose initialContents were erased. ------------------------------------------------------------------------------- QI 4238 VB If you made an event-action connection by connecting an event to an attribute, and then tried to set parameter values, the parameter name(s) were not shown on the parameters setting view. (Just the attribute name was shown.) You will now see the parameter names from the set function in this case, and in the connection popup of the event-action connection. (NOTE: the following paragraph is superceded by CTV303) As a result of these changes, any event-to-attribute connections you might have in parts that you built might appear incomplete (dotted) after you install the CSD. Connections to parts shipped with Visual Builder are not affected. If your connection specified a constant parameter, open the settings for the connection and respecify the constant value. Otherwise, redraw the connection. ------------------------------------------------------------------------------- QI 4243 VB Resource Id counts were incorrect for notebook pages that contained composite parts. This could result in duplicate resource ids. ------------------------------------------------------------------------------- QI 4252 VB VB reported a runtime error when Esc was hit on a message message box with a cancel button. ------------------------------------------------------------------------------- QI 4254 VB RC file processing has been changed to use the compiler preprocessor to merge the generated .rci files. The RC compiler does not have sufficient pre-processor support to handle the logic necessary to automatically assign resource ids in some cases, and reports cyclic include errors. This requires you to update BUILD actions in preexisting Visual Builder projects. a. Open the project. b. From the tool bar, select VIEW->TOOL SETUP. c. Modify each BUILD action as follows: 1) Select ACTIONS from the menu bar. 2) Select PROJECT OPTIONS->CHANGE. 3) Select COMPILE::RESOURCE PRECOMPILE. 4) Select the OK push button. If you change a part after installing the CSD, you must regenerate all parts associated with it. This includes any parts that embed the changed part as well as any parts embedded in the changed part. If you used Visual Builder to generate your .mak file, it will also be necessary to regenerate it to include the new resource file extension (.rcx). ------------------------------------------------------------------------------- QI 4268 VB VB reports runtime error when generating a part that has a parameter connection to an action defined using the Part Interface Editor of the part being edited. ------------------------------------------------------------------------------- QI 4273 VB A Frame window with title partially off the screen causes compile error. ------------------------------------------------------------------------------- QI 4276 VB Connecting from an attribute (other than 'this') of a variable, to a factory, results in generation of incorrect code. ------------------------------------------------------------------------------- QI 4278 VB Once an hpp name was entered into the 'Required .hpp' field in the Class Editor, you could not change the include type (ie. "" to <> or back). It showed it changing, but it did not save the change. ------------------------------------------------------------------------------- QI 4287 VB Promoting an event from a variable caused a compile error. ------------------------------------------------------------------------------- QI 4292 VB If you bring up the 'promote part feature' dialog on a factory, the attributes of the part for the factory's type are showing up. The only things that should show up on the factory promote page are the 'new' action and the 'newEvent' event. ------------------------------------------------------------------------------- QI 4294 VB Selecting the Size/Position page on a settings editory for a factory for a composite visual part caused VB to report a runtime error. ------------------------------------------------------------------------------- QI 4311 VB Rename a class, rename it again. VB reported a runtime error. ------------------------------------------------------------------------------- QI 4312 VB Deleting a child control from MultiCell Canvas using the 'Tabbing and Depth Order' dialog caused a VB runtime error. ------------------------------------------------------------------------------- QI 4313 VB Line lengths in generated files are kept shorter than 256 characters, because some editors cannot handle them longer. These files should not be edited, but everyone wants to look at them at least once. ------------------------------------------------------------------------------- QI 4322 VB ResourceIDs in Settings Pages previously required specification of the dll name without the .dll extension. They will be accepted either with or without the .dll now. ------------------------------------------------------------------------------- QI 4334 VB When editting a part based on ICanvas in the Composition Editor, VB reported a runtime error if you hit the TAB key several times. ------------------------------------------------------------------------------- QI 4338 VB Creating a new Class Interface part with no base class resulted in a runtime error. ------------------------------------------------------------------------------- QI 4361 VB If the type of an IVSequence was made to be something like 'const IString' then code generation put out a warning instead of allowing it. ------------------------------------------------------------------------------- QI 4366 VB Some changes made in settings editors were saved even when the user said not to save changes to the part. ------------------------------------------------------------------------------- QI 4368 VB Connecting to a promoted new action or newEvent event from a factory resulted in compile errors. ------------------------------------------------------------------------------- QI 4371 VB The tabbing order of the Attribute page of the Part Interface Editor was not quite right. ------------------------------------------------------------------------------- QI 4374 VB Tabbing through an empty text field in the IMultiLineEdit control, then hitting OK, resulted in VB terminating. ------------------------------------------------------------------------------- QI 4377 VB If the working directory is changed, and it has ever been set before, and no other preference setting was changed, then the working directory change was not saved. ------------------------------------------------------------------------------- QI 4396 VB When specifying the an attribute type in the Part Interface Editor, you will now be able to specify a type that has not been loaded. ------------------------------------------------------------------------------- QI 4400 VB Using layout functions (eg. distribute horizontally) on multiple toolbars caused wierd effects. These will be inhibited. ------------------------------------------------------------------------------- QI 4414 VB On a IMultiCellCanvas where all rows/columns had been deleted, the context menu still showed 'add row after' instead of 'add initial row'. ------------------------------------------------------------------------------- QI 4421 VB The Delete key can now be used to delete selected objects in the Composition Editor. ------------------------------------------------------------------------------- QI 4426 VB Problem with synchronization between IMultiCellCanvas settings and Composition Editor: 1. Bring up the settings editor on a multicell canvas that has some controls on it. 2. Keeping the settings editor up, go to the composition editor and add another control to the multicell. 3. Go back to the settings editor and add a row or column (or both) and hit Ok. You will notice the control that you have added is in a hosed state on the multicell. Any pending settings editor changes will now be invalidated when changes are made on the Composition Editor surface. (PJ20224) ------------------------------------------------------------------------------- QI 4427 VB Create a composite part that inherits from IFrameWindow and then drop this composite part on another composition editor. Next, bring up the settings on this composite part and try to change one of the styles. After hitting Ok, VB reported a runtime error. (PJ20225) ------------------------------------------------------------------------------- QI 4431 VB Connecting a cascade menu back to the root menu that contains it is invalid. This caused a VB runtime error. It will cause an error message during generation. ------------------------------------------------------------------------------- QI 4455 VB New help information has been added in the Part Information Editor on the Action and Promote pages. ------------------------------------------------------------------------------- QI 4463 VB When started from a Workframe project, in a FAT file system, the project name was truncated in the title of the main VB window. ------------------------------------------------------------------------------- QI 4546 VB Settings for style-type parameters will now show up on connection parameter settings views. ------------------------------------------------------------------------------- QI 4549 VB Limited support for user view parts has been added. (See Visual Builder now enables you to drop your own primitive or Composers parts on the free-form surface. When dropped, these parts appear as gray boxes so that you can adjust their placement and attribute values, but they do not otherwise behave like Visual Builder parts. In the compiled application, each gray box is replaced with the part it represented. To define your part, write and import a part information (.vbe) file. This creates the .vbb file needed to use the part in the Composition Editor. Guidelines follow. o The part must have IWindow in its inheritance chain. IWindow does not have to be the part's immediate base class. o You must include a VBComposerInfo statement; examples follow: //VBComposerInfo: visual, 315, dde4vr30, userprimitive //VBComposerInfo: visual,,, usercomposer VISUAL This required keyword indicates a visual part. 315 This specifies a resource ID to be associated with the part. If you do not want to associate a resource with the part, you must include a comma (,) for this value. DDE4VR30 This specifies the DLL that contains the associated icon resource. If you do not want to associate a resource with the part, you must include a comma (,) for this value. USERPRIMITIVE | USERCOMPOSER This required keyword indicates the type of user part. For more information on the VBComposerInfo statement, see "Building VisualAge C++ Parts for Fun and Profit." o If the part's constructor does not take a style flag as an input parameter, you must add VBConstructor and VBAttribute statements. The VBConstructor statement provides an alternative to Visual Build- er's default constructor for visual parts, which includes a style flag. Add the following VBAttribute statement to prevent the Styles settings page from being enabled for the part, which will cause prob- lems at run time: //VBAttribute: style, //VB: "override to remove style from the part" //VB: integer,,,, NOCONNECT NOSETTING The following restrictions also exist: o A Composers part can't require customized code in order to have a child added to it. No function exists within the Composition Editor call such code in the Composers part. o Do not try this on parts shipped with Visual Builder. ------------------------------------------------------------------------------- QI 4550 VB A new action (showCustomized) has been added to IMessageBox that allows the user to customize the message box, such as buttons to use and so on. ------------------------------------------------------------------------------- QI 4749 VB VB reports 'asyncQueueOverrun' errors when trying to open an existing part. -------------------------------------------------------------------------------