Announcement: IR V4.0.3 Beta

bpearse · Post by **bpearse** » Tue Apr 06, 2004 5:06 pm

I love this beta of IR!! I have been creating a separate spread sheet to keep track of what all my key moves mean, and this greatly simplifies things. The only thing I still would need to track separately is the notes for each of the protocols and devices. For example, I use an extender with several extra protocols for special functions. But over time, I may need to delete the protocols not being used to make room for more stuff. It would be great to have some built in way to add notes to protocols and devices to allow me to keep them straight and know which ones I can delete.

But this is a great step forward!! Thanks!!!

Edit: I decided to add all the notes regarding my device and protocol files in the notes field for the macros, since those are pretty self evident and did not need comments. I was able to put in several lines of notes, and they looked just fine in IR. But when I saved, closed IR, and re-opended, only the first line was saved. Does IR support multiple lines in the notes?

Again, thanks and the notes are a big help.

e34m5 · Post by **e34m5** » Tue Apr 06, 2004 6:38 pm

Thanks for the kind words. You could always use the general section for comments. I like your idea for more areas for comments however. Next release.

As far as not saving multiple lines I can't imagine what is happening. That is a piece we have tested extensively. Oh one thing just came to mind, the grid rows are expandable in the vertical so you can see more than one line in the notes. Do the notes show up ok when opening the KM or Macro dialogs???

bpearse · Post by **bpearse** » Tue Apr 06, 2004 6:47 pm

Very odd with the multiple line issue. I had cut and pasted from an excel spreadsheet I was using to document my key moves. Maybe I got a non-viewable character in there or something, but the macro notes area I had pasted it into refuses to save multiple lines. However, I tried another macro code note area, and it worked just fine. So, I am guessing this is pilot error. I must have done something to mess up that 'cell'.

In any case, using the General Notes area is a much better idea (Duh!). I moved my notes for devices and protocols there.

Thanks.

e34m5 · Post by **e34m5** » Wed Apr 07, 2004 7:15 am

New version loaded 4/7/2004 9:12AM

Fix DGG's issues.

bpearse Sometimes Excel and Word have characters that the text file will not recognize when copying and pasting into IR notes. This may be causing the problem with the multiple lines.

DGG · Post by **DGG** » Wed Apr 07, 2004 9:43 am

Well, almost. You've got the "missing key-field" problem, and you've improved the vertical resizing, but I still can't bring the OK/Cancel buttons into view. On my display, all that has happened is that I can now see the full hex-dislpay field where, before, I could only see its upper half.

e34m5 · Post by **e34m5** » Wed Apr 07, 2004 9:45 am

What missing key field...

Resizing is as far as I can take it...

johann83 · Post by **johann83** » Wed Apr 07, 2004 10:50 am

Just had a few minutes to play around with the latest beta...

I think I can see what DGG is saying, although on my system it isn't quite as bad. In the Special Protocols dialog, the OK and Cancel buttons are part way off the bottom of the window, and with the new resizing method, you cannot bring them fully into view. The OK/Cancel buttons of the Key Move dialog are located perfectly (as far as I am concerned) but those on the Macro dialog are too far up (i.e. there is alot of dead space at the bottom of the dialog that you cannot get rid of).

The resizing feature of the Key Move dialog works perfectly (as far as I can tell), but I occasionally see the Windows XP skin is not applying to the title bar anymore. I think I noticed this at times before with the beta, but it never seemed consistent, and it still isn't. Sometimes when I open the window the title bar is messed up, other times it is correctly skinned. I don't suppose its a serious issue, but I have never noticed this with IR 4.02.

I haven't noticed any other issues, but I didn't get that much time to play around with it. Gettting better all the time...

Matt

DGG · Post by **DGG** » Wed Apr 07, 2004 1:13 pm

What missing key field...

Sorry, it's the "missing key-field window" problem, i.e., the one I described yesterday that you had difficulty duplicating.

Resizing is as far as I can take it...

I'm glad to hear, subsequent to your post, that someone else is experiencing similar problems. I second Johann83's comment about the corresponding (resizing) operation of the Keymove dialog being faultless, which suggests that the problem has to be in the new SPB code. Perhaps it's in the area where you calculate how much high to make the key-field windows. If you arbitrarily take 50 pixels off the height of those windows, what happens?) Whatever you did last night helped. But, the SPB feature is still unuseable for me since I can't get the OK button, or any part of it, in view.

e34m5 · Post by **e34m5** » Wed Apr 07, 2004 2:02 pm

The first problem has been solved "missing key...."

Delphi deals with resizing on it's own. No code is required, it's all a matter of setting the properties on the variuos objects.

Don. Are you using 120dpi fonts? If so that's the problem.

DGG · Post by **DGG** » Wed Apr 07, 2004 2:38 pm

Paul, as I mentioned last week, IR4.0.1 (which is the latest version for which I have seen source code), has a procedure in file "dlgAdvCode.pas" named "PanelFunctionResize" that is devoted to calculating the appropriate size for various components. It is called by an "onResize" statement in file "dlgAdvCode.dfm".

Whether or not this has any bearing on the SPB problem, I don't know (and without access to current source code, I can't find out). But, it does seem to address, specifically, the difficulties currently being experienced by me and others.

Re fonts, I am using default fonts. I'd be happy to check the dpi spec if you or someone else would tell me how. That being said, it seems improbable that the problem is font-related, since the same fonts are used for the keymove dialog which doesn't exhibit the same difficulties.

If further testing on my part is likely to be helpful, please let me know.
Don

e34m5 · Post by **e34m5** » Wed Apr 07, 2004 6:46 pm

Don:

I am at loss why this would only happen in certain environments. I am familiar with the code you mentioned, but it's really not necessary.

The same thing can be accomplished with out it.

Just to make sure I understand. When you open the SPB you can't strecth it far enough in the vertical to make the buttons show up, correct.

I have tested this on several PC's with no issues. I'll keep trying.

What has me stumped is that it doesn't seem to matter whether rezising is available or not since you had this problem before.

BTW, the macro dialog has the same methodolgy as SPB, any problems with that?

DGG · Post by **DGG** » Wed Apr 07, 2004 7:47 pm

Just to make sure I understand. When you open the SPB you can't strecth it far enough in the vertical to make the buttons show up, correct.

Not exactly. I can increase the dialog up to the full height of the display. When resizing the window from only the title bar in view, the controls appear in the following order:
- Bound key group
- protocol group
- hex field
- shift buttons and finally,
- key-field windows which simply keep getting longer.

The OK/Cancel buttons should show up immediately after the hex window, but never do. As well, I just realized the Notes window isn't displayed either.

What has me stumped is that it doesn't seem to matter whether rezising is available or not since you had this problem before

Again, not exactly. The problem I had earlier was that, initially, the dialog wouldn't resize and wasn't opened at a size that would permit display of all the controls. Once you implemented vertical resizing, it was OK, except that the last opened size was not retained and the dialog had to be resized every time it was opened (subsequently fixed) and the key-field windows were much higher than would ever be necessary, thus requiring the dialog to be much taller than really necessary.

BTW, the macro dialog has the same methodolgy as SPB, any problems with that?

Not of the same ilk. As regards the problem of interest, the macro dialog works just fine. But, the OK and Cancel buttons overlap the Notes group border by a small amount - which probably isn't intentional. (Give me that on the SPB dialog and I'll be happy.)

However, in checking the macro dialog, I discovered a tiny new difficulty. As you make the dialog shorter you eventually reach the point where only the Notes window and the OK/Cancel buttons are in view. As you make the dialog even smaller, the Notes window slides out of view but, as it does, the Bound Key group of controls reappears and the OK/Cancel buttons "slide" over top of it.

I'll be away for the next few days, but if you haven't managed to duplicate the problem by the time I return, perhaps there will be something more I can do.

Have a good weekend, all
Don

e34m5 · Post by **e34m5** » Thu Apr 08, 2004 10:41 am

New build uploaded 4/8/2004 12:33PM

At some ones suggestion I added notes for devices and protocols. I did not add any for FAVS/SCAN since these seem self explanatory to me.

I have contacted Don and he and I will work out his GUI concerns directly.

I'd like have a Go/No Go from you guys for every thing else.

As soon as Don and I work out the rest, provided nothing else comes up then we will release.

e34m5 · Post by **e34m5** » Sun Apr 11, 2004 8:04 am

Well since I have not heard from anyone I will assume we are good for launch. (As soon as we work out the GUI stuff).

fichmana2003 · Post by **fichmana2003** » Sun Apr 11, 2004 11:10 am

Just one thing... The changes to this release are too significant, IMHO, to be labeled 4.03. I suggest v. 4.1.