We've turned on a search before post feature in the LabVIEW Idea Exchange. This new feature will help cut down on the number of duplicate ideas in this space!

The NI Idea Exchange is a product feedback forum where NI R&D and users work together to submit ideas, collaborate on their development, and vote for the ones they like best. View all of the NI Idea Exchanges to post an idea or add your opinion on an existing one today!

defering Panel updates is both useful and a bit tedious. You have to
fetch the Panel reference, and while you are doing your presumably
time-consuming operation, the entire panel is stuck. I suggest that
Deferring Updates should be a property of an individual object and not
just the entire panel. Wrap your operation with a pair of property nodes to
start and stop deferring and you are all set.

I don't have a problem using Defer Panel Updates Property for Panels i.e. I don't think its tedious to get to the reference as per the original post.

I support this Idea as I do have a problem when e.g. I wan't to defer updates because a method running on a heavy UI object (e.g. Update Tree) takes a lot of time and deferring updates means that I can't e.g. provide a status update in another object. http://bit.ly/9wj8dG

I support this Idea as I do have a problem when e.g. I wan't to defer updates because a method running on a heavy UI
object (e.g. Update Tree) takes a lot of time and deferring updates
means that I can't e.g. provide a status update in another object

In the same fashion, when You have multiple object instances (lets say multiple instance of an XControl for example) that need defer panel update concurrently, you have to jump through hoops to make sure one instance does not restore panel updating while another is in the middle of a large refresh that required update to be deferred. So big Kudo to that idea since having this on a per object basis will make that problem go away..