Suggest pop-up message on scene test

[apostolakisl]

This sort of came up in the forums, but I thought it would be better to repeat it here.

 

When you do a scene test you need to disable any programs that have anything to do with the scene or it messes it up. I spent quite a lot of time trying to figure out why my scene test failed until that fact was posted in the forum.

 

I suggest that when you click to do a scene test that a message is included that tells you to shut off your programs relating to devices in that scene.

 

This would be very simple and would save a great deal of frustration. If you wanted to get fancy you could have it automatically shut down the programs while the scene test runs.

[Michel Kohanim]

Hello apostolakisl,

 

Excellent idea ... my only concern is additional mouse clicks.

 

What do others think?

 

With kind regards,

Michel

[TJF1960]

How about the ISY automatically suspending/delaying all program runs until the scene test is complete? Maybe with a pop up info window indicating the programs are delayed while the scene test is running.

 

Thanks,

Tim

[apostolakisl]

Ideally it automatically shuts down programs. That would require writing significant code I am sure and I am sure you have more pressing matters. I think that you should make that a long term goal.

 

In the short term, as far as the pop up message, it doesn't have to be a separate box that you click to get rid of, it could just be a message in the "choose scene" box.

 

"Please disable all programs and turn scene on before running this test" is all you need. Put it below the "choose scene" title bar and above all the other content.

 

Or, if you hover over the "?" or click on it, the message could come up.

[oberkc]

What do others think?

 

I can tell you that I have spent a lot of time troubleshooting failed scene tests, only to find out that they failed because of programs. An extra mouse click seems a small price to pay to avoid this.

[Michel Kohanim]

Hello all, thanks so very much for your input.

 

Tim, suspending program execution is probably going to be an overkill. I like apostolakisl's idea to put the warning in the same dialog.

 

In short, consider it done and thanks so very much!

 

With kind regards,

Michel

[apostolakisl]

What do others think?

 

I can tell you that I have spent a lot of time troubleshooting failed scene tests, only to find out that they failed because of programs. An extra mouse click seems a small price to pay to avoid this.

 

Ditto on that. If one person doesn't waste the hour or two that I spent trying to figure out why the tests were failing until someone pointed out the issue on this forum, it is success. Plus the time of the other people who read my posts and were kind enough to inform me.

[Michel Kohanim]

Thank you all.

 

This is done and will be in the next drop.

 

We had to use a dialog since you can now do a scene test by right mouse clicking on the node itself.

 

Furthermore, we now turn on the scene first (wait 200ms x the number of devices in the scene) and then turn it off. This should remove one step.

 

Thanks again and with kind regards,

Michel

[apostolakisl]

Great, I see it there now under right click, diagnostics. I think you will be pleased to avoid the new user questions with those additions (as will the new users who don't have to wonder).

 

Thanks

Lou