![]() Might be January 1, might be January 31 or even later, no one knows but West Side Systems. Lightwright Touch is expecting to hit the App store early 2011. That is a $10 USD savings over the price of the app when it hits the iTunes App Store. How awesome right? Well, why not give your favorite lighting design/tech the gift of Lightwright Touch this holiday season? Bad news, Lightwright Touch will not be released in time…WAIT, don’t leave yet!!!Īs of right now, there is an introductory price of $49.99 USD if you pre-order right now, you pay $39.99. With your lighting data literally at your fingertips, you’ll glide through your paperwork using the Lightwright functions you know in the iPad interface you love. Lightwright Touch is a companion app to Lightwright 5, and enables viewing and editing of your Lightwright worksheet on a mobile device. When you read that headline, did you get overly excited? I did too! You may have heard this before, like around LDI that West Side Systems, an iOS developer, has been working with John McKernon, the developer of Lightwright, to create Lightwright Touch for the iPad! (Adding AutoPatch to an existing driver is a simple matter, requiring a couple of hours of development/coding, at most.Give The Gift of Lightwright Touch This Holiday Season However, perhaps if those who don't yet support AutoPatch receive enough requests for it from their customers, they will go ahead and add it. CAST Software does not enforce the implementation of this Protocol-the implementation of features beyond basic connectivity is left entirely at the manufacturer's discretion. A few such manufacturers (Compulite and ChamSys among them) have implemented this Protocol, but others (such as MA Lighting and High End Systems) have not. Was the reason for your request (of implementing this Protocol) to simply eliminate the need to create the patch on the console in addition to having to do it in WYSIWYG? If so, please note that all console manufacturers who are "connected to WYSIWYG" via our Registered WYSIWYG Developer Program have-and have always had, since the year 2003-the ability to implement our AutoPatch Protocol, which essentially enables users to upload the patch from a. * My interpretation of your request was that you were simply asking for the addition of ASCII text encoding to files that WYSIWYG exports in text format from DATA mode's Spreadsheets (i.e.CSV files), because for some reason, the current UNICODE encoding was not compatible with the spreadsheet application that you were using (or whatever other purpose you had for exporting from WYSIWYG). given its age, is it something that's still in use and current? Can you tell me which modern consoles support this Protocol? To my recollection, we have never had a request for this, and, to be perfectly honest, this is the first time many of us here at CAST have ever heard of this Protocol. (We can continue this discussion here, or you can just email me as usual.)Īre you, by chance, referring to adding the "ASCII Text Representation for Lighting Console Data" Protocol,, defined by USITT twenty-four years ago, in 1992? If so, this is something completely different than your initial request (or at least what I believed* was your request), and much more involved. naturally, if it was possible, we'd like to be able to offer a solution to export to the required format and encoding directly, without having to go any of the above-mentioned workarounds. ![]() May I ask what you require this for, though-what you intend to do with the resulting ASCII-encoded file, and why you specifically need a file encoded as such? Having that information will help us determine how we can make WYSIWYG's export functionality more useful. CSV from DATA, import the resulting file into Excel, and then export from there to any format and encoding you like. Another option you have, of course, is to export to. CSV format from the dropdown below).įor a future version of WYSIWYG, we will try to add the option to export ASCII-encoded files directly from DATA mode. ![]() To export a Spreadsheet from DATA mode as such, simply export it to a Worksheet (DATA mode File menu > Export to Worksheet), then go to PRES mode's Worksheets tab, access the Worksheet you just created and export from there (File menu > Export > Worksheet > select the. You can already export an ASCII-encoded file from WYSIWYG, by exporting a Worksheet to.
0 Comments
Leave a Reply. |