IR Server Suite - Version 1.4.2 Test Build 3158/3281 (3 Viewers)

[and-81]

RSykes:

ok, one more attempt is attached... this works for me, but let me ask you this...

Do you have "Start MediaPortal in fullscreen mode" and "Hide taskbar in fullscreen mode" selected in MediaPortal configuration? And do you have UAC on or off?

Cybrmage:

Attached is a console test app version of the Custom HID Receiver.

Cheers,

 

[RSykes]

Tray Launcher Focus

Aaron,

I do have "Start Mediaportal in Fullscreen mode" selected

I also have "Hide Taskbar" selected

UAC is also off.

The option I don't have ticked is "Mediaportal is always on top" this removes the start button from my screen but I can tell MP is not the current focused app as my mouse does not respond in it but the remote works. To get the mouse to respond I have to click on MP and then I can use mouse and keyboard.

I don't know if you have this problem too?

Thanks for the efforts Aaron, being a developer myself I know how difficult it is debugging external problems and recreating them.

 

[and-81]

I'll try to recreate your setup more closely ... I've been using it with UAC on, and Always on Top Off...

I won't bother posting updates until I can reproduce the problem, cos everything I've tried so far has failed

Thanks for your patience.

 

[RSykes]

Tray Launcher Focus

If you need any more information or help Aaron just let me know.

Thanks
RSykes

 

[xxxxxxxxxx]

Thanks for the feedback, I've fixed the Translator bug and attached a new Translator EXE. These NotifyIcon objects are a real pain in the butt... Turns out I was changing it's visibility from a separate thread and this was causing the problem.

You should be able to send App Commands with the Send Windows Message command in Translator, but I've heard of people having trouble with this, so I will make a new command just for sending App Commands.

I'll make sure all your feature requests are addressed after 1.4.2 stable is released.

thank you!

the icon bug is fixed and i successfully managed to send app commands using the window message tab.
i think for an average user it's too hard to find that out:

Message Number = 793
wParam = 0
lParam = (65536 * APPCOMMAND_?)

 

[and-81]

xxxxxxxxxx:

I agree, I'll add a new command just for sending App Commands.

Thanks,

 

[risu]

What it's worth, just telling I've also always had problems with translator not setting focus on MP. Also using vista, I open MP to secondary screen with commandline parameter /screen=1 instead of screenselector on setup (setup option always overrides commandline one and I really need to be able open MP also on primary screen so commanline is the only way).

Sometimes MP starts with focus and sometimes not. Using preview 3 or 4 I think but it's been like that always with previous versions too. Aaron, have you already tried to bring the MP window just to foreground with setforegound? I was getting pretty frustrated because on my HTPC MP navigation is really slideshow if not focused. I was going to write my own little MP starter that would force focus on MP (and which translator would launch so I could get MP started) but I'm happy to see you are now working on the issue.

 

[and-81]

risu:

I've been looking at this problem on and off for a long time now. I'm determined to get it sorted out once and for all but I can't reproduce it on my own PC, which I'm sure you can appreciate makes it difficult to fix.

I've got a second test PC setup now so I'm getting it ready to test this problem too.

Here's what my focus forcing code does in it's latest incarnation:

1. Launch program.
2. Launch monitoring thread to watch the program.
3. While the program is running, every 5 seconds check the foreground window.
4. If the foreground window is not owned by the Launched program then start enumerating all open windows.
5. Once a window that is owned by the launched program is found, give it focus.
6. Goto 3.

The way it gives focus (P/Invoke calls):

1. SetForegroundWindow
2. If 1. doesn't work then:
3. AttachThreadInput
4. SetForegroundWindow again
5. BringWindowToTop
6. SetFocus
7. Undo AttachThreadInput

MediaPortal is a bit different to some other applications in the way it starts up (with the splash screen and all), making it hard to force the focus. But it does work on my PC with the latest versions of IR Server Suite.

I think the best solution to this problem will be to change MediaPortal itself so that it steals focus on launch... Or at least to add an option to do so.

For example, if I launch Paint Shop Pro 10 it starts with a splash screen similar to MediaPortal, and when the app finishes loading in the background it steals focus. I think MediaPortal needs to do this too.

In the meantime I will keep trying. If someone has some fancy focus forcing code they'd like to share then feel free to send it over to me. But I can tell you that the way I'm doing it now works with everything else on my PC (including MediaPortal)... Maybe there is an OS setting that needs to be changed? I know that you can change the "Allow windows to steal focus" setting in tweakui ...

I know there is a util for MediaPortal that works, but it uses AutoIt or AutoHotKey or something like that... I'll look into how it does it too.

I'll make sure that 1.4.2 final has this issue sorted, I promise.

Cheers,

 

[mironicus]

IR Server won't work after second hibernate

I installed IR Server Suite (latest beta) on my system (Vista) with the plugin for Mediaportal. I have an original MCE remote from Microsoft.

After the first hibernate the remote works within Mediaportal, but after the second it won't work anymore!

After exiting Mediaportal and starting the Input Server Configuration and selecting Configure on MCE and then OK it works again.

I start Mediaportal again and let the computer hibernate. After restarting the remote won't work.

I found a solution: Start Input Server Configuration - Advanced - Set process priority to "idle". The default setting was "no change". After this the IR Server Suite won't exit anymore after restarting from hibernate.

 

[and-81]

mironicus:

Very interesting ... I wonder if this is caused by the Input Service trying to reclaim the device before it has been re-initialized after a resume ... I'll do further testing here and may default to Idle priority or try to find a way around it.

Thanks for the feedback!