ORDA – Constructor and touched event – Detailed behaviour through a network
In this previous blog post, you discovered that ORDA entities can now have a constructor, allowing entity instantiation to follow a complete object-oriented approach.
And that’s not all — another blog post introduced the first ORDA data event in a full series: the touched event.
Want to know exactly WHEN and WHERE the constructor and the touched event are triggered while actions move back and forth between a client application and the server? This blogpost is for you.
Keep reading to learn all the details and explore a live demo!
ORDA – Get started with the touched event
ORDA is a core long-term feature that opens up a world of new possibilities in 4D.
We keep enhancing ORDA to help you write powerful code. As a result, your apps become easier to develop and maintain — and most importantly, they are optimized for great performance for your end users.
That’s why we’re excited to introduce a new feature in 4D 20 R10: in-memory data events.
In a typical user journey, the required data by the user is loaded into memory, modified according to user actions, and finally saved when the user clicks a Save button.
What if you could automatically trigger business logic when in-memory data changes? It’s now possible to format or prepare data as early as possible, so it’s ready to save when needed.
This is made possible by the new ORDA touched event on data — and the benefits are considerable.
Want to learn more? Keep reading!
Ease your developer’s life with list boxes
New 4D View Pro form events
As of 4D v18, a new set of 4D View Pro form events are available. They return special information that can be accessed with the new FORM Event command, introduced in this blog post. Say hello to: “On Column Resize”, “On Row Resize”, “On Clicked”, “On Double Clicked”, “On Header Click”, “On Selection Change”, and “On After Edit”.
Expanding the abilities of the Form event command
As you may already know, the Form event command identifies the type of form event that has just occurred. It’s typically used within a form or object method.
Some changes have been made in 4D v18, but it’s all good. Here’s what you need to know: