Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[marko]

[FIXED] ~ thanks.

[risingdamp]

So that's why I press T in GF to bring up track info and sometimes nothing happens.

[JimH]

I suppose you've already experimented with display setting changes and with possible third party plug-in interactions.

[GHammer]

I suppose you've already experimented with display setting changes and with possible third party plug-in interactions.

Hmmm, which 3rd party plugin do you suspect of causing the bar to hide and show wherever the mouse pointer is located?

I only have 2 plugins installed and I don't think the DirectX or Audioscrobbler interact with the display at all.

Personally, I'd like to see that display bar disabled.

[Alex B]

It took me a while to actually understand what you mean. Usually when I have G-Force running I don't handle MC menus. I rather sit comfortably on my sofa and enjoy the show. After your last posts I followed your instructions to the letter and found it. Perhaps this picture clarifies it to others:



When the mouse pointer goes down a bit more (over the edge of the display area) the control bar appears and at the same instance the help menu disappears. So the user doesn't have a chance to click what was meant to click.

I would consider this as a minor annoyance, but of course it should be fixed (especially if that makes marko happier  ). The question is who should fix it. MC doesn't have this problem with the integrated display options. So the G-Force developer should fix it in the first place.

However, if fixing it is not possible without turning some bits the other way round in MC then JRiver should gladly help the G-Force developer in this (IMHO). G-Force is a good add-on for MC and I am sure it also brings some added value to MC.

[risingdamp]

I'm running 279 and noticed yesterday that GF will not respond to any keyboard commands at all even if I use the mouse to ensure I have focus.  Is this what's fixed with 280?

[Matt]

This was from Andy about the keyboard issue on 5/14/05:

"Hey Matt...  Thanks for writing and the problem report... Sure enough, I
found the issue and we'll see it fixed in the next release."