Either it's perfect or every one is mad
Announcement: IR V4.0.3 Beta
Moderator: Moderators
-
Capn Trips
- Expert
- Posts: 3989
- Joined: Fri Oct 03, 2003 6:56 am
The latest BETA version is available for download HERE.
PLEASE READ CAREFULLY
This new Beta version of IR has significant enhancements in the area of Notes for Macros, Notes for KeyMoves and a Global note on the general panel. It is also different than the prior IRBeta in that it creates the notes and traditional IR upgrade information in ONE .TXT file, named exactly the same way the production version names files and eliminates the .INI file.
WARNING: If you choose to use it please read the following important information:
1) This version has a significantly different file format to incorporate the notes. If you have an old IR file or one from the prior version of the Beta it will automatically convert the old file and the .INI notes for you. NOTE: It will save the old version of both the IR file and the .INI file with an extension of .OLD just incase you want to go back to the prior version. You would just need to delete the new .TXT file and rename the .OLD files to .TXT and .INI.
2) It is not compatible with the current version of IR so once you create or convert an upgrade with this IRBeta you will not be able to read it with the current version(s) 4.0.2 or older of IR.
3) It is not compatible with the current version of ExtInstall for extender installation. Once you create or convert an upgrade with this IRBeta you will not be able to read it with the current version of ExtInstall. NOTE: See notes below on modifications you can do to make it work. (The owner of this tool has been contacted and is working on revisions)
4) It is not compatible with the current version of IRtoWav. Once you create an upgrade with it you will not be able to read it with the current version of IRtoWav. NOTE: See notes below on modifications you can do to make it work. (The owner of this tool has been contacted and is working on revisions)
Until compatible versions of the ExtInstall and IRtoWav programs are available you can do the following to make the file work with them.
1) Edit the text file with Notepad and:
a) Delete the first line - [Buffer]
b) Delete the notes at the bottom of the file starting at the line with - [General] in it (if they exist)
c) Do a global replace of := (Colon and equal signs) to just the : (Colon sign)
d) Do a "Save As" of the upgrade to whatever name you like to be used as input the ExtInstall and IRtoWav programs
PLEASE READ CAREFULLY
This new Beta version of IR has significant enhancements in the area of Notes for Macros, Notes for KeyMoves and a Global note on the general panel. It is also different than the prior IRBeta in that it creates the notes and traditional IR upgrade information in ONE .TXT file, named exactly the same way the production version names files and eliminates the .INI file.
WARNING: If you choose to use it please read the following important information:
1) This version has a significantly different file format to incorporate the notes. If you have an old IR file or one from the prior version of the Beta it will automatically convert the old file and the .INI notes for you. NOTE: It will save the old version of both the IR file and the .INI file with an extension of .OLD just incase you want to go back to the prior version. You would just need to delete the new .TXT file and rename the .OLD files to .TXT and .INI.
2) It is not compatible with the current version of IR so once you create or convert an upgrade with this IRBeta you will not be able to read it with the current version(s) 4.0.2 or older of IR.
3) It is not compatible with the current version of ExtInstall for extender installation. Once you create or convert an upgrade with this IRBeta you will not be able to read it with the current version of ExtInstall. NOTE: See notes below on modifications you can do to make it work. (The owner of this tool has been contacted and is working on revisions)
4) It is not compatible with the current version of IRtoWav. Once you create an upgrade with it you will not be able to read it with the current version of IRtoWav. NOTE: See notes below on modifications you can do to make it work. (The owner of this tool has been contacted and is working on revisions)
Until compatible versions of the ExtInstall and IRtoWav programs are available you can do the following to make the file work with them.
1) Edit the text file with Notepad and:
a) Delete the first line - [Buffer]
b) Delete the notes at the bottom of the file starting at the line with - [General] in it (if they exist)
c) Do a global replace of := (Colon and equal signs) to just the : (Colon sign)
d) Do a "Save As" of the upgrade to whatever name you like to be used as input the ExtInstall and IRtoWav programs
D/L'ed the new beta. I see you changed the resize mechanism along the lines I had suggested. Thanks. However, it's still not quite right.
Upon opening the SPB dialog, the key-field windows are even longer than before, forcing the OK, etc. buttons out of view - and they won't come back. Enlarging the dialog vertically just makes the keyfields longer. It seems the opening height of the key-field windows, and perhaps other components, must be calculated relative to the opening dialog height. The IR dialog does not exhibit this behaviour.
In the horizontal direction, the dialog cannot be enlarged beyond its opening size (which, as I reported before, is not wide enough). The width of the left-hand window changes when the dialog is resized, but the right hand window remains fixed in place. Since I can't see the right edge, I can't tell whether or not it the right-hand window also is resized. So, it looks like the width of these windows also must be calculated upon opening. As well, the Shift button remains fixed in size, but moves horizontally, while the X-Shift and Unshift remain fixed in place but are both resized. Since I can't see them, I don't know what's happening to the OK and Cancel buttons
On a related topic, I wonder if you couldn't overcome the dual focus problem a number of us commented on some time ago by replacing the two key-field stringgrids with a single, two-column stringgrid and limit the focus at any one time to a single cell. Perhaps something to think about for a future version.
I didn't attempt any further tests.
Don
Upon opening the SPB dialog, the key-field windows are even longer than before, forcing the OK, etc. buttons out of view - and they won't come back. Enlarging the dialog vertically just makes the keyfields longer. It seems the opening height of the key-field windows, and perhaps other components, must be calculated relative to the opening dialog height. The IR dialog does not exhibit this behaviour.
In the horizontal direction, the dialog cannot be enlarged beyond its opening size (which, as I reported before, is not wide enough). The width of the left-hand window changes when the dialog is resized, but the right hand window remains fixed in place. Since I can't see the right edge, I can't tell whether or not it the right-hand window also is resized. So, it looks like the width of these windows also must be calculated upon opening. As well, the Shift button remains fixed in size, but moves horizontally, while the X-Shift and Unshift remain fixed in place but are both resized. Since I can't see them, I don't know what's happening to the OK and Cancel buttons
On a related topic, I wonder if you couldn't overcome the dual focus problem a number of us commented on some time ago by replacing the two key-field stringgrids with a single, two-column stringgrid and limit the focus at any one time to a single cell. Perhaps something to think about for a future version.
I didn't attempt any further tests.
Don
Another little problem worth looking at.
Display a DSM and click on the 8th-13th field. Now cancel the SPB and attempt to display a ToadTog or D/LPK. Error "Cannot focus a disabled or invisible window" results. The error does not occur if the focus for the DSM was in the 1st-7th field.
I also had a situation where only the left-hand key-field window would display for a D/LPK, but I haven't been able to repeat it. I'll keep trying and let you know.
Display a DSM and click on the 8th-13th field. Now cancel the SPB and attempt to display a ToadTog or D/LPK. Error "Cannot focus a disabled or invisible window" results. The error does not occur if the focus for the DSM was in the 1st-7th field.
I also had a situation where only the left-hand key-field window would display for a D/LPK, but I haven't been able to repeat it. I'll keep trying and let you know.
New version loaded.
Took me a while but I found it.Display a DSM and click on the 8th-13th field. Now cancel the SPB and attempt to display a ToadTog or D/LPK. Error "Cannot focus a disabled or invisible window" results. The error does not occur if the focus for the DSM was in the 1st-7th field.
No matter what I can't replicate this. Maybe I'm not doing the same steps.Display a Toadtog or LPK. Reset. Then reduce the vertical size such that the key-field windows are totally eliminated. Close the SPB. Now, reopen SPB and only the left-hand key-field is displayed.
No matter what I can't replicate this. Maybe I'm not doing the same steps.Display a Toadtog or LPK. Reset. Then reduce the vertical size such that the key-field windows are totally eliminated. Close the SPB. Now, reopen SPB and only the left-hand key-field is displayed.
After reset of the SPB dialog, (which clears the key-field windows and eliminates the right-hand window), reduce the vertical size of the SPB dialog so that only the title is displayed. Close the SPB dialog with the Close button. Now, reopen the SPB dialog by clicking on the SPB button in the Keymove dialog and, voila, the right-hand key-field window isn't there. (The left hand window displays correctly.) Works every time for me. The same thing happens if a DSM is displayed, the dialog is resized to just the title bar, both the SPB and Keymove dialogs are closed and the SPB is then reopened to dispaly a Toadtog or D/LPK. If, when the SPB dialog is opened at such a size that no portion of the key-field windows is in view, is the number of required key-field windows determined - which, in this case, would be two, not just one as was the case when the window was last closed.
Re the vertical resize problem, when you calculate the height of the key-field windows, you need to allow more room for the elements (hex display and OK/Cancel buttons) at the bottom of the dialog. Another 30-35 pixels should do it.
Don