JP1 Remotes

Bump...no comments

I either I made every one mad or it's perfect

The driver still doesn't load for me under the newest version. I do think Dabbith is on the right track, as Service Control Manager and Admin Rights sound NT related. A couple other fixes I would hope to see before a release would be:
1. Fixing the Insert Shift and Add Shift buttons on the Scan/Fav tab.
2. Fixing the Maximized/10 pixels low/resize issue Capn Trips mentioned.

Speaking of window resizing and scroll bars, on the general tab two-thirds of my screen is unused gray. I have to scroll down to see items past #8 for both Device Settings (15) and Other Settings (10). Could these be made resizable or bigger? (I would selfishly suggest showing at least 15 items )

Does anyone have a suggestion as to how I can get MISC/1107 to show up with a custom name like the other special protocols?

Keep up the great work!

mikemcgo wrote:The driver still doesn't load for me under the newest version. I do think Dabbith is on the right track, as Service Control Manager and Admin Rights sound NT related. A couple other fixes I would hope to see before a release would be:
1. Fixing the Insert Shift and Add Shift buttons on the Scan/Fav tab.
2. Fixing the Maximized/10 pixels low/resize issue Capn Trips mentioned.

1. Out of scope..but i will look into it

2. Not sure which one you are referring to

Speaking of window resizing and scroll bars, on the general tab two-thirds of my screen is unused gray. I have to scroll down to see items past #8 for both Device Settings (15) and Other Settings (10). Could these be made resizable or bigger? (I would selfishly suggest showing at least 15 items )[/quote/]

Same as above...out of scope but I'll look into it

Does anyone have a suggestion as to how I can get MISC/1107 to show up with a custom name like the other special protocols?

What is the name for this and I will added to the constants list

Can you send me your beta code? I have access to a WindowsME machine that should exhibit the problem behavior. I'll see if I can trace out what's happening.

P.S. I like the new error handling, but would like to see the "Cannot decode a keymove without function values." error removed as it doesn't cause any problems if it were ignored.

mikemcgo wrote:The driver still doesn't load for me under the newest version. I do think Dabbith is on the right track, as Service Control Manager and Admin Rights sound NT related. A couple other fixes I would hope to see before a release would be:

I hope Paul can figure this one out.. Maybe Mark will have some suggestions....

mikemcgo wrote:1. Fixing the Insert Shift and Add Shift buttons on the Scan/Fav tab.

Mike, what is wrong with these. They seem to work fine for me.

mikemcgo wrote:2. Fixing the Maximized/10 pixels low/resize issue Capn Trips mentioned.

Paul, this is an old problem where if you maxmize IR, get out and back in the screen is shifted down.

mikemcgo wrote:Speaking of window resizing and scroll bars, on the general tab two-thirds of my screen is unused gray. I have to scroll down to see items past #8 for both Device Settings (15) and Other Settings (10). Could these be made resizable or bigger? (I would selfishly suggest showing at least 15 items )

This needs to go on a wish list since it is not related to what Paul volunteered to work on (Special Protocol Dialog). I would like that myself.

mikemcgo wrote:Does anyone have a suggestion as to how I can get MISC/1107 to show up with a custom name like the other special protocols?

If I remember correctly, 1107 is the LCD display option specific to the 2116/2117 called "Custom Mode Name" where you can change the device display name. Would LCD/CMN suffice as a name on the grid?

Ok...I'll remove the Cannot message

and the LCD name

I didn't realize that this update was specific to certain areas. Sorry for sidetracking things.

1. For me, the Add Shift and Insert Shift buttons on the Scan/Fav tab always add/insert "Key0" instead of the selected key(shifted).

2. When I launch IRbeta it is maximized, and the driver error immediately comes up. At this point the window is correctly aligned. As soon as I click on OK to clear the error, the window drops about 10 pixels. If I click on the middle icon (I think it's called Restore) the window becomes smaller. If I then click on the Maximize icon it goes back to full size and is aligned correctly. I never ran into the problem in IR4.02, so maybe once the driver error is fixed I won't see it in IR4.03.

3. As for Misc/1107, I had been calling it Modename, but LCD/CMN is good.

Thanks.

mikemcgo wrote:I didn't realize that this update was specific to certain areas. Sorry for sidetracking things.

1. For me, the Add Shift and Insert Shift buttons on the Scan/Fav tab always add/insert "Key0" instead of the selected key(shifted).

2. When I launch IRbeta it is maximized, and the driver error immediately comes up. At this point the window is correctly aligned. As soon as I click on OK to clear the error, the window drops about 10 pixels. If I click on the middle icon (I think it's called Restore) the window becomes smaller. If I then click on the Maximize icon it goes back to full size and is aligned correctly. I never ran into the problem in IR4.02, so maybe once the driver error is fixed I won't see it in IR4.03.

3. As for Misc/1107, I had been calling it Modename, but LCD/CMN is good.

Thanks.

No problem..I think I can fix the Key0 thing...I have an idea of what may be happening.

I need to make sure that when I compile the exe that I have the windows at the correct size otherwise you will experience what you describe. Odly though I do not have any such issues as some have described...

Paul


The two primary things being discussed are also in 4.0.2.

1) the key0 thing
2) the maximize problem. With the maximize thing all you need to do is open IR, maximize the window, then close IR. When you reopen IR it will remember to maximize but will not properly fill the window until you restore the window and maximize it again. When you first open it you will see part of the screen below the taskbar

Oh yeah, don't forget the driver problem on WinME

Good news...the Key0 was a simple matter of changing an AND to an OR....

The driver..well that's another whole ball game...

Ok new one uploaded (3/25/2004 8:45AM)

Fixed Key0

Added as many protocol names as I could find (this is only for display not for protocol building)

Removed unnecessary message about funtion values

All that's left is the Driver thing and Dabbith is helping research that one

Ok, driver issue fixed. I just gave bad directions. To remove the DEV directive, you need to click the ... after Conditional Defines. Then choose the directive and click delete. You'll need to add it back when you want to debug anything in Delphi. I tried it on a WinME machine that exhibited the problem before and with that change it doesn't do it anymore.

New load with DEV conditional removed...

I hope this is it....

TX Dabbith

I'll test the driver issue when I get home.

New build 12:54PM

I made one tiny change to the name of the notes file so it's more readable.

The format now is xxxx_notes.ini

If you have a current notes file just rename it using the above convention.

I think this is all I going to do for this unless there is something really major.