Switches?

[Mugsy]

Originally Posted by wnjj

How about posting your batch file so we can take a look? The example shows -W but the section I posted says to use lParam. Maybe try -L instead of -P

My bat file:

SendMessage.exe -c WinClass -N WinName -m 1024 2

("2" for Left arrow.)

I tried several variations as well. All it does is give me a popup window listing the commands and usage, but nothing in terms of explanation.

[Mugsy]

Originally Posted by JustFred

According to the List Of All SageTV Commands, sending Event # 63 jumps to "LiveTV". See Appendix D, and then specifically page 224 in the user manual.

I haven't quite figured out how to send "events".

Using "SageTV.exe -event 63" on the command line or in a bat file fails to launch the program.

[wnjj]

Originally Posted by Mugsy

My bat file:

SendMessage.exe -c WinClass -N WinName -m 1024 2

("2" for Left arrow.)

I tried several variations as well. All it does is give me a popup window listing the commands and usage, but nothing in terms of explanation.

Try:

SendMessage.exe -C SageApp -N SageWin -m 1258 -W 0 2

You needed the app and window names need to be "SageApp" and "SageWin" and the -m setting to be 1258, not 1024.

[wnjj]

Originally Posted by Mugsy

I haven't quite figured out how to send "events".

Using "SageTV.exe -event 63" on the command line or in a bat file fails to launch the program.

Running that shouldn't launch the program. It needs to already be running. After it's running, calling it with the -event 63 option "talks" to the already running instance (basically another SageTV.exe program runs, sends a message then exits). The SendMessage.exe program does the same thing as the -event option but allows for more than one code in sequence.

[tmiranda]

Originally Posted by Mugsy

If you could do that, that would be awesome.

TIA

I'll be traveling this weekend. I'll look at it when I get back.

[Mugsy]

Originally Posted by wnjj

Try:

SendMessage.exe -C SageApp -N SageWin -m 1258 -W 0 2

You needed the app and window names need to be "SageApp" and "SageWin" and the -m setting to be 1258, not 1024.

Thx for the reply. That ALMOST gets me what I want. (Is there a list somewhere of what "m" values do?)

For the bat file to work, SageTV.exe must already be running and on the Main Menu.

I tried adding "SageTV.exe" to the bat file to launch it first, but the "SendMessage" executes too soon.

I need a single bat file (or shortcut) that opens Sage and goes directly to Live TV.

[wnjj]

Originally Posted by Mugsy

Thx for the reply. That ALMOST gets me what I want. (Is there a list somewhere of what "m" values do?)

For the bat file to work, SageTV.exe must already be running and on the Main Menu.

I tried adding "SageTV.exe" to the bat file to launch it first, but the "SendMessage" executes too soon.

I need a single bat file (or shortcut) that opens Sage and goes directly to Live TV.

That 'm' value is specific to sending user event messages to SageTV and is coded into the .exe here: https://github.com/google/sagetv/blo...cher.cpp#L1522

I'm not sure how to wait until the message loop is up and ready. Depending upon how immediate you need it to be, you could put a fixed delay in the batch file between the SageTV.exe call and the SendMessage.exe call. Something like this:

timeout /t 60

This will wait 60 seconds (or you can press a key to skip).

Alternatively there may be a way to detect when SageTV is ready but it may involve something more complex like checking for a logfile timestamp or contents to change. A plugin may be simpler at that point.

[Mugsy]

Originally Posted by wnjj

Something like this:

timeout /t 60

This will wait 60 seconds (or you can press a key to skip).

Thanks. That was a great idea, but... "Windows". Need I say more?

Here is the bat file I created:

SageTV.exe
timeout /t 20
SendMessage.exe -C SageApp -N SageWin -m 1258 -W 0 63

(I decided to go with event "63" instead of Left arrow. More likely to work every time.)

Looks like it would work, no? No. Windows launches SageTV.exe, then waits for it to close before executing the next two lines (I thought "SendMessage" was being sent "too soon", but it's actually being sent too LATE!)

So unless there's a way to do it all in one command, I'm afraid this method just won't work.

[wnjj]

Originally Posted by Mugsy

Thanks. That was a great idea, but... "Windows". Need I say more?

Here is the bat file I created:

SageTV.exe
timeout /t 20
SendMessage.exe -C SageApp -N SageWin -m 1258 -W 0 63

(I decided to go with event "63" instead of Left arrow. More likely to work every time.)

Looks like it would work, no? No. Windows launches SageTV.exe, then waits for it to close before executing the next two lines (I thought "SendMessage" was being sent "too soon", but it's actually being sent too LATE!)

So unless there's a way to do it all in one command, I'm afraid this method just won't work.

Add 'start /b' before SageTV.exe and it won't wait for it to finish.

start /b SageTV.exe
timeout /t 20
SendMessage.exe -C SageApp -N SageWin -m 1258 -W 0 63

[Mugsy]

Originally Posted by wnjj

Add 'start /b' before SageTV.exe and it won't wait for it to finish.

Hey! That worked!

What does the "start /b" do?

[wnjj]

Originally Posted by Mugsy

Hey! That worked!

What does the "start /b" do?

Good deal.

start means run the program without waiting to return to the batch file. The '/b' means run the program without opening another console. You can see this by running "start dir" and "start /b dir" from a CMD prompt to see the difference.