Comet32
From CometWiki
Recent Changes
Comet 2009.402
- Implemented a Comet32 error log. errorlog.csv will be created in the COS directory.
- Implemented document archives (for DocMgr).
- Corrected a problem that was causing Windows message events to sometimes be dropped.
- Added a color square on the right side of the status line of the Comet window indicating whether the current program object was compiled with Comet16 or Comet32. The indicator is blue for Comet16 objects and green for Comet32 objects.
Comet 2009.401:
- Implemented CURPOS.
- Implemented support for contiguous files.
- Implemented NOVA / SNOVA functionality.
- Recoded the str function for Comet32 so it emulates the Comet16 one.
- Implemented the shortpath DOSMS function.
- Implemented the CometAnywhere update mechanism.
Comet 2009.400:
- Improved printer functionality including pdf printers.
- Improvements in the functionality of dialog-based programs. Try DlgDemo.
- Improvements in GDI operations such as wallpaper.
Known Problems that We Plan to Consider and/or Address
- Currently an error messagebox saying "Server Busy" will display when compiling for Comet32. If you click the RETRY button your compile will continue.
- A WinSock driver has not been implemented. -- Justin
- XAP has not been implemented. -- Justin
- Some features of DbMgr, ViewMgr, and DBX do not run. -- Barb
- ODBC is not supported. Perhaps replace with SQL interface. -- Justin
- Serial Gateway is not supported. -- Brian
- The Comet logo and Document Manager bit map do not display in DocMgr. -- Brian
- When Comet32 loads for the first time, the screen colors are way off. COSW.INI seems to be initialized with incorrect default values.
Functionality that Will Not Be Part of Comet32
- The Spool driver has not been implemented. -- Not needed, replace with DocMgr
- Image file support.
- Q-emulation for QICBASIC objects.
- The SORT driver will not be implemented. We have modified the Reporter (version 9.02) to work without it.
- Invalid character substitution in file names
- QSTARTX.
- Inputting a numeric value from the screen works differently under Comet32 than under Comet16. For example if you declare a variable to be 6.2 and you input its value as "5", under Comet16 that would be interpreted as .05 whereas under Comet32 it would be 5.00.
- Hallelujah, never could get operators to understand the old way.--badge 18:03, 19 May 2009 (UTC)
- Background partitions have not been implemented. You may launch a new foreground session as an alternative. --Forget it
- ACTIVATE and TERMINATE have not been implemented.
- PCOMM and INTERRUPT have not been implemented.
Differences Between Comet16 Objects and Comet32 Objects
It is our intention that your Comet16 objects will run under Comet32 exactly as they do under Comet16. IB has been enhanced for Comet32 so not only will you be able to do more things easier we also may decide to change the functionality of some of the legacy instructions. We welcome your input on these issues as they come up.
- Numeric overflows will generate a runtime error E01 for Comet32 programs. You can trap this with an ERRORTO.See Discussion Page--badge 18:03, 19 May 2009 (UTC)
IB Enhancements for Comet32
- The size of the user buffer (# buffer) has been increased to 8K.
- Strings may be declared up to 64K in length.
- You may declare a dynamic string that will allocate only the memory required for the current length of the data assigned to it. These strings may be up to 4gb in length. For performance, chunks of memory will be allocated in 64k increments. (Arrays may not be dynamic).
- Numbers may include up to 64 digits; 32 integer and 32 fractional.
- An extensive math package has been added including trig functions, factorial, logs, and exponents.
- Editmasks rules regarding the length of the editmask and the length of the number have been relaxed to reduce runtime errors.
- The maximum array size has been increased to 4.2gb.
- User-defined procs have been implemented. For more info see User Defined Procedures in the IB manual or User Defined Procs - Wiki Version.
- New instructions have been implemented:
- InputFile and PrintFile or Input/Print File - Wiki Version
- Call and ProcReturn or Usr Defined Procs - Wiki Version
- GetFormat and PutFormat or Get/Set Format - Wiki Version
- SearchFile or SearchFile - Wiki Version
- NOEXCP has been added as an option to EXCP= on file system statements, NoExcp - Wiki Version
Please Add any other issues you see with this product here
- PDF printer does not return the path the first time it is run (Jims machine only?)