Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make the "Test" function dialog a separate exe, and/or be able to open it from xSchedule #5042

Open
DoctorWiz opened this issue Dec 9, 2024 · 2 comments
Labels
Enhancement Unlikely To Be Implemented Either very rare use case or the overhead/complexity so great it is unlikely to be implemented.

Comments

@DoctorWiz
Copy link

Is your feature request related to a problem? Please describe.
On my 'player' machine that runs xSchedule, I often need to pull up the "Test" function (from the Sequencer Tools menu) to check that something is working and is assigned to the correct controller, port, or DMX address. Currently, I need to open the Sequencer only to get to the test dialog. But xSchedule is already running, so if I could just get to it from there...

Describe the solution you'd like
To be able to run the Test feature independently, without having to open (and wait for) the Scheduler, or to be able to access it from xSchedule.

@cybercop23
Copy link
Collaborator

You can always use FPP.

@DoctorWiz
Copy link
Author

No, want to use the most excellent xSchedule on one of the many old klunker Windoze machines I have without having to convert it to linux (NOT bashing linux) or shell out for a Raspberry Pi. Not to mention using that same (player) machine to make last minute tweaks to the layout and/or sequences.
Not bashing the most excellent FPP either, but xSchedule is far more convenient for my setup. And my shop/office is 200ft away thru 3 gates.

@cybercop23 cybercop23 added Controllers Unlikely To Be Implemented Either very rare use case or the overhead/complexity so great it is unlikely to be implemented. and removed Controllers labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Unlikely To Be Implemented Either very rare use case or the overhead/complexity so great it is unlikely to be implemented.
Projects
None yet
Development

No branches or pull requests

2 participants