Announcement: IR V4.0.3 Beta

DGG · Post by **DGG** » Fri Mar 26, 2004 8:01 pm

Paul, re your post 6 above (it's hard to keep up with the traffic!), as I've noted before, I'm using "Normal" font size with a screen resolution of 1024x768. I don't have any abnormal Windows settings (that I know of). All the other windows/dialogs in IR/IRBeta display normally. The fonts, etc. in the displayed SPB dialog box are the same as for other windows/dialogs. Incidentally, what do you mean by "Standard Windows"? Changing the style to Windows Classic makes no difference (to the SPB display problem).

Is the displayed size for the Keymove dialog I gave you earlier this afternoon correct? If so, what Window's setting would cause a problem only with the SPB dialog? Are you telling me that the full-sized SPB dialog is smaller than the Keymoves dialog? What are the expected dimensions for the SPB dialog using normal fonts and 1024x768 please?

e34m5 · Post by **e34m5** » Fri Mar 26, 2004 8:15 pm

At 1024x768 using Wondows classic on my machine it is 4in wide x 6.25 high.

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Mar 26, 2004 8:20 pm

Paul

Here is my suggestion for how to handle the conditions for SP keymoves

1) If an existing SP keymove is selected/highlighted let the user edit it.

2) If they have selected/highlighted a none SP keymove don't let the user edit it.

3) Only display the SP device number and type for an existing SP keymove on the main keymove dialog and not let them enter it .
ie. gray it out as read only when an SP keymove is highlighted or grayed out blank for none SP.

4) Let them select the bound device and button on the main keymove or the SPB. On the main so they can still create normal keymoves.

5) Clicking ADD goes to the SPB where they could enter everything including the bound device, bound button, type of SP (DSM, LKP, etc.), and the buttons.

I think this will eliminate the confusion some have had

DGG · Post by **DGG** » Fri Mar 26, 2004 8:50 pm

Of course, absolute size doesn't matter since that depends on screen size. I should have realized that earlier.

Windows Classic or XP, resolution 800x600, 1024x768 or 1152x864, big fonts or small - none of it matters. The window sizes get a little bigger or smaller, but the relative situation stays the same. The size of the SPB dialog on opening is about 20% too small on both axes. In the vertical dimension, it's cut off at both top and bottom. Horizontally, only the right side is cut-off. The curious part is, the only window that's a problem is the SPB dialog.

If I'm the only one out here having this difficulty, then I'll have to live with it. Am I the only one having this problem?

By the way, Nils suggested earlier that once I resized the dialog, it should always open at the new size. That's true for the Keymove dialog - even after closing the application, but not for the SPB dialog. Does Windows have some strange rules about nested dialog boxes?

Post by **The Robman** » Fri Mar 26, 2004 9:39 pm

e34m5 wrote:Rob:

The notes are saved on a separtae file. Look for an ini that has the name of you file plus _notes.ini

In what folder? The same one as the saved file? I'm not seeing the file there. I am seeing a file called irnotes.ini which is empty. And I'm still seeing the main notes from one file get brought up for other files, but not all other files, it's weird.

And just for the record, the SPB screen looks fine on my PC.

Nils_Ekberg · Post by **Nils_Ekberg** » Fri Mar 26, 2004 10:09 pm

Rob, you should see an ini file that starts with the same name as the upgrade file in the same directory as the upgrade file.

I think the irnotes.ini file is a carry over from and earlier test when he was accidently creating that file.

That's weird that you are seeing notes from one file in another. Once you locate the ini files you can see if the notes are in each one and maybe Paul can figure out how they transferred.

Post by **The Robman** » Sat Mar 27, 2004 12:04 pm

I was expecting the notes.ini file to be in the same folder as the saved IR file, and while this appears to be the case for several other files, I found a file called IR_notes.ini in a seperate folder and this one contains the notes that are being used across remotes.

I notice that IR (beta) is saving a notes file for every IR file that is opened, even if no notes are added for that particular file. I think it would be a better idea to only save a notes file when notes are actually added as this would save cluttering up the folders.

e34m5 · Post by **e34m5** » Sun Mar 28, 2004 8:45 am

The IR_Notes happened when the main file name is empty..I added code to check for this..so you may have had an old one.

Also, if for any reason you touch the KM or Macro notes field I set a flag to indicate that some thing has been revised for notes...then I save the file. So if you had a note and then deleted it you would end up with a notes file.

Mark Pierson · Post by **Mark Pierson** » Sun Mar 28, 2004 11:15 am

e34m5 wrote:Also, if for any reason you touch the KM or Macro notes field I set a flag to indicate that some thing has been revised for notes...then I save the file. So if you had a note and then deleted it you would end up with a notes file.

That makes no sense to me. Why create/save a notes file if the user hasn't saved the main IR file? The flag should be the same one IR uses to determine if its contents are "dirty" and the notes save should be tied to the main file save. Additionally, if ALL notes are deleted, then the notes file should be as well.

What happens if I open "My IR Config.txt" (which contains no notes), add some notes, but decide to change the name (using IR's Save As..) to "My NEW IR Config.txt"? Do I end up with 2 notes files when I only wanted the notes in the revised one?

e34m5 · Post by **e34m5** » Mon Mar 29, 2004 7:04 am

Mark...respectfully I chose to have a notes file all the time. We are talking just a small text file here...has very little bearing on anything else.

The user may have changed notes but not the main IR file. That's why I don't use the same flag.

Post by **The Robman** » Mon Mar 29, 2004 7:40 am

I think Mark's point is that we've come to expect, from all of our software, that nothing gets saved until you personally SAVE it. IMHO, this should also be true of IR. Let's say I open an IR file and change nothing except some notes, this should simply set the flag that something has changed, it shouldn't save a file until I either SAVE it, or I try to exit, in which case I should get the warning.

To use Mark's example, let's say I opened filea.txt and added some notes, changed a few things and then saved it as fileb.txt, would my notes now apply to BOTH filea and fileb? IMO they should only apply to fileb.

e34m5 · Post by **e34m5** » Mon Mar 29, 2004 7:49 am

No prob..I'll put a messsage on not save until you choose. Keep in mind that you will receive two messages then.

One for the buffer as you see today and
Another for the notes

Nils_Ekberg · Post by **Nils_Ekberg** » Mon Mar 29, 2004 8:20 am

I did some quick tests and it works as expected. In other words, open fileA make some notes changes and do a "save as" fileB and the new notes apply to fileB only and file A is unchanged.

Paul, The flag that is set for main IR could also be the same flag used to flag the changes for the Notes. That way, you set the flag if a note is changed or added and the main IR sets it if something in the actual upgrade changes. That way you would only end up with one prompt.

e34m5 · Post by **e34m5** » Mon Mar 29, 2004 8:33 am

Not so easy my friend. In IR there isn't a flag per se. What happens when a file is opened the entire remote file is loaded into an array called Loaded.

During the time you work in IR another array called Buffer stores the all the new values.

When exiting (saving) the contents of the two are compared and if different you see the "Buffer has changed" note.

So because one could change notes w/o changing the IR file I think we need two separate checks.

e34m5 · Post by **e34m5** » Mon Mar 29, 2004 9:23 am

Just uploaded a new build (3/29/2004 10:21AM)

Added more checks to address the concerns from Mark and Rob.

Added checks based on Nils comments on when to show SPB button