PDA

View Full Version : 1.3.4B nits


edmc
05-17-2003, 03:05 PM
Nit 1 - Screen Saver on Sleep

The behavior is that SageTV does it's own Screen Saver as soon as I sleep it. Not what I think most folks had in mind.

Suggestion 1 - Disable the configured Windows Screen Saver (if any) when SageTV is not slept. When put to sleep, re-enable the configured Windows Screen Saver. In other words, let Windows honor my Screen Saver settings (e.g. 3D Pipes only after 5 minutes of inactivity).

Nit 2 - Load at Startup in Taskbar/Full Screen Mode

The behavior is that at LOGIN (i.e. Windows Startup when User Logins are not used), SageTV is started up either in the Taskbar or Full Screen Mode.

Suggestion 2 - Add (or replace these) Options with settings for how I want SageTV to startup however it is started. In other words, if I click the button to startup in Taskbar and then launch SageTV from the desktop Icon, start it up in the Taskbar. I know we've gone back and forth on this before but I think your stuff was in a bit of flux at the time. I'll again check the Registry and hack what I need to hack if possible. I'll let you know...

Nit 3 - Immediately after launch/startup in Full Screen Mode, the keyboard is inactive. The first action has to be a Mouse Movement. Note that this only occurs on SageTV and not the Client oddly enough. It is also some behavior that has changed over the last few versions. 1.3.3B, for instance, didn't exhibit this. It's not major for those w/ mice, but I'm concerned for those using Remote Controls which may try to send Keyboard commands (rather than SendMessage technique in Girder).

edmc
05-18-2003, 11:44 AM
Re Nit 2 - new Nit 4

I thought I'd snoop around in the Registry/StartupDir to see what got set when I selected Load at Startup in Taskbar. Didn't find anything.

Of course, I did this on my laptop where I run SageTVClient. Well, I went back to just make sure my Load at Startup in Taskbar was set - and it wasn't. And no attempt to set it would get it to "stick".

Figures... I'll go look on the Server now :-)

But the Nit (#4 I guess) is that the Load at... options don't seem to "stick" on SageTVClient (they do on the Server however...).

edmc
05-23-2003, 03:10 AM
Re Nit 3 - new Nit 5 - both present in the newly posted 1.3.5B as well

Nit 3 turns out to be a keyboard focus issue. If I simply ALT-TAB, I can then use the keyboard shortcuts. Of course this is indeterminate and, hence, hard to automate. There are tools out there - most notably Girder - which allow one to tell a Process to take the keyboard focus. But, of course, if one is using Girder, they don't have much use for the keyboard.

Nit 5 is obviously related. When bringing up the Capture Card config dialog box from Detailed Setup, the dialog box gets pushed to the back (behind the Full Screen SageTV in my setup). As in the solution to Nit 3, it should be easy enough to not only make sure the Capture Card's Properties Dialog have keyboard focus but also be brought to the forground.

Hope this helps...

Narflex
05-23-2003, 12:57 PM
#3 - Not sure why this is happening, but I've added another focus request command to SageTV's UI startup that should clear it up for the next build.

#5 - I'm going to remove that dialog altogether in the future and put those controls elsewhere. Unfortunately, it's not easy to fix for now because its mixing Java & Windows dialogs that's the problem.