Key press problems

[imilne]

I have two IScreenPlugin implementations.

The first one is displayed - over video - in response to a PLAYBACK_KEYDOWN event, in this case catching F5.

Once active, it's also designed to respond to an F5 (via OnKeyDown), the idea being that you can go from the initial screen to a further screen of details using the same key.

My problem is that the initial (single) press of F5 seems to get passed right through the chain so that only the second screen appears. The first one is being called, but it instantly responds to the F5 and fires up the second one instead.

Bug? Or just me?

The plan is supposed to be, press F5 once:

[ATTACH=CONFIG]35304[/ATTACH]

Then again while the above is active:

[ATTACH=CONFIG]35305[/ATTACH]

Iain

[mvallevand]

Are you eating the keystroke by returning True or are you still passing it to the base?

Martin

[sub]

The first one is displayed - over video - in response to a PLAYBACK_KEYDOWN event, in this case catching F5.

Anything that is registered to get EventNotifications will get sent all events, including PLAYBACK_KEYDOWN. It sounds like you're handling it in both your IScreenPlugin's, and they're fighting each other.

[imilne]

Yep, I was returning true. sub, what you say makes sense, but PLAYBACK_KEYDOWN was only intercepted in one place. If anything, now that you mention that, I'd have expected the first screen to open on F5, and then the first screen again from a subsequent F5 because PLAYBACK_KEYDOWN is still catching it.

I've attached a stripped to the bone copy of the source if you want to take a look. MediaInfoPlugin is the control class that handles PLAYBACK_KEYDOWN and then the other two classes are the actual screens.

Thinking about it some more, I'll probably try to handle everything in PLAYBACK_KEYDOWN seeing as it catches everything, rather than have one of the screens try to do OnKeyDown too. At least its behaviour is not what you expect so I feel more confident about getting to the bottom of it now. Thanks.

Iain

[mvallevand]

I know when I was rendering too many screens at one time I added this to NeedsRendering()

Code:

if (PluginHelperFactory.GetPluginHelper().ScreenSaverIsActive() || PluginHelperFactory.GetPluginHelper().GetActivePopup() != null)
            {
//                Debug.WriteLine(PluginHelperFactory.GetPluginHelper().GetActivePopup().GetName());
                changed = true;
                return false;
            }

Perhaps you could use this concept in your keyboard handler triggering on the name?

Martin

[imilne]

That's a good idea, but I can't seem to get a handle on the active popup. Even sticking the following into NeedsRendering() of one of my screens prints out null constantly.

Code:

if (PluginHelperFactory.GetPluginHelper().GetActivePopup() == null)
  Logger.Debug("null");

I'm obviously doing something daft here but can't quite put my finger on it...

Iain

[imilne]

I'm also not seeing any action in either Deactivate() or Dispose() when either of the screens are closed. Should I?

Maybe programming while drinking wasn't such a good idea...

Iain

[ACTCMS]

Maybe programming while drinking wasn't such a good idea...

Iain

Of course it is... I write some of my best code after a few beers...

Alex

[imilne]

Of course it is... I write some of my best code after a few beers...

I'm obviously drinking the wrong stuff today...

Iain

[ACTCMS]

I'm obviously drinking the wrong stuff today...

Iain

That would be milk then...?

Alex