The WAF killer, getting myHTPC to go in fron when sage sleeps

[mlbdude]

I think they may want to keep the multiple clients on one PC for some good reasons. I know I use it allot . However, it could be a pain for normal usage. It would probably be best served to require a special cmd line parameter if you DID want it to launch a second instance.

[tangfj]

I think they may want to keep the multiple clients on one PC for some good reasons. I know I use it allot .

mlbdude, just curious, but what do you use multiple clients for? Do you watch more than one show at a time?

[mlbdude]

I can't really explain that without violating my NDA unfortunately. It is something that will be useful for all in the future though which is probably why bug submissions on that would be ignored. I think they would do a special cmd line parameter though to tell it that it is OK to run multiple processes.

[tangfj]

Sorry for my ignorance, but what is NDA?

[Opus4]

Originally posted by mlbdude
I think they may want to keep the multiple clients on one PC for some good reasons. I know I use it allot . However, it could be a pain for normal usage. It would probably be best served to require a special cmd line parameter if you DID want it to launch a second instance.

OK, thanks for the heads-up on that... I'll stop worrying about it for the time being. It came up a while back when someone noticed that trying to wake SageTV brought up SageRecorder instead -- similar issue regarding the window/program ID. I think your comment about requiring a command line parameter for the 'abnormal' case of wanting multiple clients running would be a good one. OR, have a parameter specifying the ID (perhaps 1, 2, 3, etc.) of the client you want to deal with -- that way, it can start that one if it isn't already running or wake it if it is.

Oh, and NDA = New Drug Application. They will have to submit documentation to the FDA since SageTV is expected to be quite addictive. Hmmm... on the other hand, it could also mean Non-Disclosure Agreement, something companies want people to sign saying they won't divulge secrets. (Sorry... that comes from my wife & I never being able to understand each other when we talk about NDAs.)

- Andy

[White94Cobra]

While we're on the subject of Girder I'm now using my MX500 with a USB-IRT through Girder. Everything works great except for one thing... I have a button assigned as HTPC that puts Sage to sleep and brings myHTPC to the foreground (or starts it if it's not running) and disables the Sage commands and enables the myHTPC commands. Unfortuantely I have to hit the button twice for the command switch to work. If I press it once it puts Sage to sleep and brings/runs myHTPC to the foreground, but unless I press it again I don't have control of myHTPC. It isn't a focus issue because if I select the window with the mouse I still don't have control.

I'll post my GML file later if necessary (at work now). But I was wondering if any Girder experts had seen this issue before? I even tried enabling the myHTPC command group as many as three times in a row in the task-switch sequence with no luck. Basically I check to see if Sage is in the foreground, if so put it to sleep, then check to see if myHTPC is running, if not run it, if so set focus to it and disable the Sage command group and enable the myHTPC command group.

I'm hoping the WAF goes way up with my new Girder setup. Everything (Sage, myHTPC, BSPlayer, and Napster) can be controlled/loaded/switched-to with the remote. This double button press issue is a big one for some reason though.

[salsbst]

That GML sounds familiar. Happens to me sometimes, too. Are you sure you can't solve it by using a longer delay? I think I could do so, but I'd rather have the shorter delay and occasionally press the button twice when needed.

BTW, others have said that having Girder send a mouse click to myHTPC helps. Haven't tried that mysefl.

[tangfj]

I have had the same problems with my GML file. What seemed to work for me is when I press my button to sleep Sage and bring focus to myHTPC I just duplicated my SetFocus command a few times.

So my GML command to sleep Sage looks something like this:

sleep Sage
disable SageTV commands
enable myHTPC commands
SetFocus myHTPC
SetFocus myHTPC
SetFocus myHTPC

This works most of the time without a hitch. The only other problem I am having is getting the button in myHTPC for Sage to work all of the time. I've tried using the button with the -awake parameter and without it. Sometimes it doesn't work when I press the button, well, it works, but it doesn't bring Sage to the foreground. When this happens I have to Alt-Tab to switch to it. Any thoughts on this?

[gplasky]

So set it up in Girder like you did for myHTPC and have it setfocus for Sage a couple of times when do it.

Gerry

[salsbst]

The only other problem I am having is getting the button in myHTPC for Sage to work all of the time. I've tried using the button with the -awake parameter and without it. Sometimes it doesn't work when I press the button, well, it works, but it doesn't bring Sage to the foreground. When this happens I have to Alt-Tab to switch to it. Any thoughts on this?

I'll have to check but I think that I use something other than the command line to wake up Sage. Pretty sure its a the SendMessage "Full Screen" command. It works every time with no hitches. I'll post details tonight.

[tangfj]

Well, that is where I have a problem, because I don't know how to use the event.exe function of girder that well. I am also using it right now for a dvd ripping app in girder. Will I be able to use event.exe twice in the same group of girder?

[salsbst]

Ok, looking at my GML (don't have Girder installed at work) it looks like I do this:

SendMessage 231 ("wake up")
WaitForWindow (4 seconds = 4000milliseconds)
SetFocus

Works like a charm.