Print

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

[Myron]

Since I've been using NetRemote to control MC for a while now, I'm pretty happy with the way things work with one exception.  Any time a error dialog window pops up MC stops responding untill the window is dismissed.  So if I'm out on the deck listening to an internet stream and decide to switch to another one that's not working at the moment, everything is stalled untill I go inside to my office, power my monitor back up and dismiss the window.  An accidental hit of the play button with an empty Playing Now can cause the same thing.

So I'm asking if there's anything that can be done in MC 12 to improve this.  Having an option to automatically dismiss error windows after some short delay would do the trick.  Or having error messages pop up in a status bar instead of opening a new window and halting.

Any comments?

[Rob L]

Yep, that'd be nice - I've just started using NetRemote, and I'm getting to the stage where I really couldn't live without it, but every now and again I do something stupid, cause an error in MC, and then regret it...

[Mastiff]

I have a program called "PTFB" - Press the Phreakin' Button - that takes care of that. When all those annoying pop-up boxes has been learnt into the system it just sits there waiting for them and closes them within a second. Unfortunately it's not free anymore, like it was when I downloaded it a few years ago. Maybe you can still find the free version somewhere out there?

[Myron]

Tor,

Thanks for the tip!  This could be good solution.  I assume you need to re-learn the popups if they change.  I don't know how often MC's pupups change, but I see this as a drawback.

I think the best solution is to handle this at the source, in MC.

[richard.e.morton]

yeah! thanks for the tip.

It would be much nicer if it was coded in though - such as if the error came up in a dialog box (ie but not over the top of a fullscreen display, of an image, for instance), wrote the error to a log file for review and after a predetermined time closed the log but somewhere made it obvious that an error had occurred (indicator light on the main screen for instance)

R