September 21Sep 21 Moving this from a prior public post to here…I like all the new functionality for programs- haven't started building/modifying programs in the eISY UI yet though but excited with how it looks. While reviewing, I thought of a helpful feature to speed program debugging- showing true/false status line by line in the program conditions and whether or not the then or else clause is evaluating to true. This should be doable as on the program list you can see true/false status and on the variable pages you can see their values. That would be a big visual clue as to the error in your logic or confirming it's working as intended. Otherwise you have to open multiple browser windows or flip back and forth between pages to step through a program.
September 22Sep 22 We are investigation commenting out lines, status per line could be very confusing.
September 22Sep 22 @Javi ,Agree status per line could be confusing all the time, it would be useful in a debug/test mode. You are writing a program and you save. Turn on the test/debug, it gives you colour by line. Saves running back to nodes and variables as you test a recent program. This would just be the program you have selected. Turns off as you move away. I could have used this last night. I was using UD Mobile & two web tabs to check out all the sources of data which affected the program. Just a thought, this would match how you use debuggers when writing code (which is another approach to this, allow the programmer to put watches on vars, nodes , progs, on a screen as you debug).
September 22Sep 22 The issue is eisy is event driven. Some things are not calculated unless the program is run or the event is received. So it would report the last status which could be incorrect, or would always be false in the case of events. Commenting lines then trigger would work better as it removes the confusing always false and allows reevaluation.
Create an account or sign in to comment