3 comments
-
Lee DYDOMITE Dydo It's feasible, but it's thousands of clicks, sub-menus, and opportunities for errors. I would do it in HTML and JavaScript instead.
Also note that BrightSign LLC is dropping support for devices older than series 4, and BrightAuthor:Classic soon. You could still make it work, but it's definitely "swim at your own risk." -
Alastair Thanks for the reply! Yeah, I had a feeling it would quickly become spaghetti-ish if using the author layout - haven't investigated HTML/Javascript yet as I wanted to check there were no other technical restrictions before diving in too deep.
I'm fine if support for the older versions of hardware/software get deprecated, so long as they don't just stop working! (which, as I understand it, there's no reason why they should because everything can be run locally? At least I hope I understood that correctly, because that's a deal-killer!)
-
Brandon EOL software won't support the new hardware which means we can't guarantee it'll work and any new/changed hardware features won't be supported even if an old presentation does work.
Classic BrightAuthor already doesn't support Series 6/newer.
Currently, outstanding issue BCN-13508 makes the BrightSign Author (fka brightAuthor connected fka BrightAuthor:connected) UI unresponsive when you reach the three-digit count of states/events, so definitely best to go with HTML/Javascript to avoid management issues later._________________________________________________________________________
Friendly reminder, the community forum is intended for user-to-user discussion. It is not regularly monitored. For troubleshooting problems and to ensure a timely answer from a BrightSign representative, please submit a support ticket