Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wish: Hard Refresh or "Recompute All" #3273

Closed
archinate opened this issue Nov 26, 2014 · 7 comments
Closed

Wish: Hard Refresh or "Recompute All" #3273

archinate opened this issue Nov 26, 2014 · 7 comments
Assignees

Comments

@archinate
Copy link

Every now and then, I find myself needing to do a "hard" refresh of a definition... meaning to force all nodes to recompute. Is there a way to do this currently?

The work around always seems to be to re-wire the front of the definition or provide some toggle to make Dynamo "think" it needs to refresh.... but it would be preferable to have a "Recompute All" or "Refresh All" feature.

@mjkkirschner
Copy link
Member

I find I need this a lot as well, if you build a debug version of Dynamo there will be a debug menu with this option.

@ikeough
Copy link
Contributor

ikeough commented Dec 9, 2014

Yes, as @holyjewsus said, if you build Dynamo in debug, there's a "Force Re-execute" option. We don't want to make this available to the user yet, so we've put it in this debug menu.

@archinate Are you using this for debugging, or are you suggesting this would be a worthwhile user-facing feature?

@archinate
Copy link
Author

User facing would be greatly preferred. All too often a problem a user is
having with a definition refreshing could be remedied with a "hard refresh"
option instead of explaining that they need to find a node, disconnect, and
reconnect it to force it to update.

Sometimes it's like getting a teenager to get out of bed at a decent hour
on a Saturday. I want the ability to give my definition a kick in the
pants from time to time.

-Nate

On Tuesday, December 9, 2014, Ian Keough notifications@github.com wrote:

Yes, as @holyjewsus https://github.com/holyjewsus said, if you build
Dynamo in debug, there's a "Force Re-execute" option. We don't want to make
this available to the user yet, so we've put it in this debug menu.

@archinate https://github.com/archinate Are you using this for
debugging, or are you suggesting this would be a worthwhile user-facing
feature?


Reply to this email directly or view it on GitHub
#3273 (comment).

Nathan Miller
Associate Partner
Director of Architecture & Engineering Solutions
M: +1.402.709.6677 O: +1.212.255.5483
Omaha, NE

case 5912 MAPLE STREET, OMAHA, NE 68104 / CASE-INC.COM http://case-inc.com

@andydandy74
Copy link
Contributor

I wholeheartedly agree with making this available to the users. In a class room setting, the part about about disconnecting nodes always makes for strange facial expressions. And I like the teenager analogy. :-)

@ajudd11
Copy link

ajudd11 commented Dec 11, 2014

I agree with @archinate. Using some tools such as his Lunchbox Revit Element Collectors it would be very nice to have a way to "Recompute All" when the Revit model changes and have those changes reflected in the definition. I am sure there are many other scenarios where this would be a very useful feature as well.

@mjkkirschner
Copy link
Member

@scottmitchell - I think you can consider this when you are thinking about the profiler UX.

@Amoursol
Copy link
Contributor

Amoursol commented Apr 1, 2020

This has now been implemented in the TuneUp extension, available from Dynamo 2.5 onwards. All nodes can be marked dirty and recomputed using the Force Re-execute button.

@Amoursol Amoursol closed this as completed Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants