| Issue | Description | Status |
|---|---|---|
| Installer Issues | ||
| 1 | The Imaginate installer repairs the Imaginate installation by adding back files that users have deleted manually. | Open. There are some settings set at distribution time in Installshield that claim to "enable support for advanced Windows Installer functionality" (which are set on by default), but the repair functionality can be turned off on the user's machine. It puts data into a folder [WindowsFolder]\Downloaded Installations to help it do the repairs. |
| 2 | The Imaginate install has been reported as not working in a networked environment. | Open. Cannot reproduce (no networked environment is available to test). Found nothing in the Installshield documentation to indicate that network installs would be a problem. |
| 3 | The installer doesn't add a shortcut or icons for the program anywhere. | Open. |
| 4 | The installer does not launch the program after install (despite the claim on the last page of the install wizard). This is repeatable on both Win98 and WinXP. | Open. |
| 5 | The uninstall doesn't remove the settings.xml file nor the folder in 'Program Files'. | Open. |
| 6 | On a stock installation of Windows XP Pro, a user received an error message
during install: Imaginate Installer Information Error 1931: The Windows Installer service cannot update the system file C:\Windows\System32\hhctrl.ocx because the file is protected by Windows. You may need to update your operating system for this program to work correctly. |
Open. The file hhctrl.ocx is a support file for Windows HTML Help. Windows XP has a later version of this file already installed in the operating system. If a user receives this error message, they can ignore it. |
| Inform | ||
| 7 | Imaginate does not work correctly with the French Inform libraries. In the Build/Settings/Options/LanguageName, you can put French, but in the Include Files "English.h" still appears (instead of "French.h"), while "frenchG.h" is ok. | Open. |
| 8 | In Inform mode, sometimes objects show up as [No Name], even though they have
both an identifier and an object name. By "object name," I mean a name given in
quotation marks in the object's header: Object example "object name"; |
Fixed in source. |
| 9 | In Inform mode, the property explorer incorrectly reports the object name as "short_name." An object name is not the same as a short_name property. In fact, it is not a true property at all. | Fixed in source. |
| 10 | Imaginate needs updating to take account of the changes to Inform with the release of the v.6.3 compiler. | Open. For a list of new features in Inform 6.3 see: http://www.inform-fiction.org/inform63/RelNotes.pdf |
| TADS 2 | ||
| 11 | 1. Using TADS2 formatting, create a new name.t file by adding an include line
in one of the existing source files. Save that file and Imaginate will create a
blank text file after confirming where you want that file to be saved.
2. Edit that new text file, but don't save it. 3. Go back to the file in which you added the #include <name.t> and delete the entire line, "#include <name.t>" 4. When you then attempt to save all files, Imaginate stops responding. |
Fixed in source. |
| Alan | ||
| 12 | Imaginate should be updated to support ALAN 3 | Open. |
| 13 | When saving an ALAN 3 source file (from the Alan 3 demo game "Saviour"), a "subscript out of range" error message occurs. | Open. Note that Imaginate 1.5 is not designed to function correctly with Alan version 3 (see issue 12). |
| TADS 3 | ||
| 14 | Instead of using .IMP project files, TADS 3 should use TADS 3 make files (.T3M) compatible with the TADS 3 compiler and TADS 3 Workbench. | Open. Partially fixed in source (Imaginate now reads from T3M but does not yet write back to it). |
| 15 | Imaginate does not support TADS 3 projects with multiple source files. | Open. Eric Eve has suggested a temporary workaround of creating a dummy "master" source file and adding #include lines to it to include all the required source files. Fixed in source (Imaginate now supports projects with multiple source files, and understands TADS 3 library file syntax, though it does not take account of the options to exclude individual source files from libraries within the T3M file, nor does it yet allow addition of source files to the project once created). |
| 16 | In TADS 3, using an #include statement on the dummy master file (see the workaround to issue 15) to create a new source file, a "subscript out of range" error occurs when saving. | Open. Cannot reproduce this issue in source. The fix to issue 15 has presumably eliminated it. |
| 16 | In TADS 3, using an #include statement on the dummy master file (see the workaround to issue 15) to create a new source file, a "subscript out of range" error occurs when saving. | Open. Cannot reproduce this issue in source. The fix to issue 15 has presumably eliminated it. |
| 17 | When editing TADS 3 projects, the class browser should support template syntax, and all the other features of TADS 3 that it does not currently handle. | Open. Imaginate 1.5 release simply uses the same parsing algorithm for TADS 2 code to handle the TADS 3 code. This is obviously not ideal. This issue is partially fixed in source. A new algorithm has been constructed to pick out the classes, objects, etc. within TADS 3 code. It does not currently to a satisfactory level, because the use of macros in TADS 3 source is confusing it. |
| 18 | A user reported that they have been unable to get the TADS 3 Workbench to use Imaginate as an editor. Despite setting Imaginate as the default text editor (and trying the -f parameter as well as the 'autoconfig' of Workbench) anytime Imaginate opens when called from Workbench it just shows the New Project wizard instead of openning the file passed to it. | Open. It is not clear if this is an Imaginate problem, or an issue with Workbench 3.0.7. To be investigated further. |
| User Interface Issues | ||
| 19 | The file menu flickers before appearing. | Fixed in source. |
| 20 | Imaginate is differing from Windows in that the OK button in dialogs is only enabled when there are changes that can be made. It should be made consistent with the operating system by having the OK button enabled all the time. | Fixed in source. |
| 21 | When using Windows XP the menu appearance is incorrect - some of the items that shouldn't be available (like File | Print) appear to be available. But when you roll the mouse over the menu item it then dims. | Open. The vbAccelerator menu control used by Imaginate does not draw correctly in Windows XP. |
| 22 | It has been reported that on Win98, when right-clicking in the source code window, the menu draws once, then animates on top of what is drawn. | Open. Cannot be reproduced (no Windows 98 environment available for testing). |
| 23 | The Ctrl-S menu shortcut does not work. | Fixed in source. |
| 24 | When cancelling New Project and open an existing one, the dialog always opens in ...Imaginate\Projects, rather than the location defined for the chosen language, or the location where the user last worked on a project. | Fixed in source. |
| Miscellaneous | ||
| 25 | On some occasions, #included files don't show up in the Project Explorer, which leaves no way to access them within Imaginate. | Fixed in source. |
| 26 | After moving an #include statement and saving (via the menu), it is possible in some circumstances for Imaginate to get stuck in an infinite loop. | Fixed in source. |
| 27 | After moving an #include statement and saving (via the menu), it is possible in some circumstances for Imaginate to get stuck in an infinite loop. | Fixed in source. |
| 28 | Imaginate should have a mechanism for allowing users to open source files that are not part of the current project. | Open. |
| 29 | Imaginate should have a built in file browser to make it easier for users that work with individual files (see issue 28) to find and open those files. | Open. |