Kevin Long
Well Known Member
I've been diving deep into the latest release of Logic Extensions (LEX) lately, and I must say, I'm impressed by the progress they've made over the past couple of years. The new features like accepting and returning arrays, along with aggregation, have made this tool much more versatile. It allows for functionality that isn't possible with a Named Event Rule (NER). Moreover, the ability to interact with controls on the form adds another layer of intrigue. Though still somewhat limited, I'm eagerly anticipating future iterations of this User Defined Object (UDO) and where it'll go next. With that in mind, I'd like to offer a few suggestions for future improvements:
- As the LEX becomes more complex, it's necessary to zoom in to view individual steps. However, when you edit a step and return to the Logic tab, the zoom resets, requiring you to zoom back in. It would be ideal if, upon returning to the main page, you'd be at the same spot where you left off—same zoom level and position in the logic.
- It would be immensely helpful to have the ability to press a button on a form. If I could hide an existing button like the Exit button and add my own replacement button with custom logic, then trigger the hidden button from my LEX, it would significantly enhance the tool's utility.
- When a LEX encounters an error, it should be treated as an error by the form. Admittedly, this suggestion is still in its early stages, and I haven't fully explored its implications. However, it seems that an error raised by a LEX should be more than just an FYI for the user. While the previous suggestion could mitigate this issue to some extent, I'm putting this idea out there to gather thoughts on both sides.