I’ve come with up some alternatives but it would be handy to have it as a native feature if the user could see some icon and message when the inputs changes and the query is running like this one when it’s empty:
I guess there are some limitations on when it applies, but in our project most of the tables are only refreshed when the user changes the inputs and there’s a confusion on whether it’s loading, it’s the same data, or the query returned empty.
Just circling back here - we’ve added this feature to our backlog.
I don’t currently have an estimation of when this will be implemented, but I will let you know when it is!
This feature has not been picked up yet. It looks like it might still need some Design, but other than that it is just waiting for a team to have the time available to bring it in.
A thought on this: Consider providing a generic expression/scripting function that examines a property and returns true if that property’s binding (if any, and one of the asynchronous types) is “busy” in the background.
I believe the current approach is to actually supply a “loading” prop as part of the meta category for every component (it will be locked to system permissions). The loading property will be true if any binding (aside from loading) is still pending a return value. While that property is true, certain components will have their loading appearance in place. It’s not noted in the ticket, but I would expect that once loading becomes false it will not go back to true until the page is refreshed.
My idea would be a bit tricky–there is nothing in existing infrastructure (in either Perspective or Vision, like a propertyChange) that would signal such a monitor (as an expression) to go from false to true. ):
Actually in looking at Carl’s comments it appears that the field would actually be an int which denotes the number of active bindings waiting to evaluate. It would be up to the user to then supply indicators that a component is waiting on bindings to evaluate. I left notes in the ticket to consider some way to indicate when a “driving” property of a component is waiting on a binding (like props.data).
Horray! Some of my DB bindings take a few seconds to load (its our ERP, so I have little ability to optimize further) so this would solve a lot of user issues related to waiting for data to load.
The internal ticket went backwards. It’s now in the incubation phase, meaning it is waiting for design work to be done, or a clarification on how it should be implemented. I would not expect this feature anytime soon.