Watch Node - Can't Resize Dynamo v3.3.3.0

Revit
1

It’s been sort of asked on here before but there seems to be no real solution.

I have watch nodes that get narrow and the resize arrows cease to be available. The only thing I’ve been able to do is delete them and replace them with new watch nodes.

Image 1
Image 11039×1027 38 KB

I appreciate any help and pardon the snarky tone but if someone posts that I should disable add-ons or ‘restart my CPU’: Those are clearly not helpful. For the record, CPU’s are the main processing CHIP inside a computer. :slight_smile:

2

Try editing the name to be something very large and then back and see if that forces the arrow back?

**Edit: **Are you able to reproduce consistently, and without any add-ins or 3rd party components?

  • If so can you give me the steps to do so?
  • If so but 3rd party components are active in either the host application or Dynamo can you disable them to rule them out as the cause?
  • If not, any ideas what causes it?

I believe there is an update in 3.5 or 3.6 which addresses the issue to some extent, but it’s one of those “only sometimes” issues and finding out what causes it is the first step to fixing anything.

3

Thank you for the quick response.

I was super optimistic about the renaming it… Unfortunately: No luck.

Image 3
Image 3969×307 8.21 KB

  • I can’t say what causes some of them to get narrow – I will see if I can spot them as they happen.
  • I have a coterie of add-ins like PyRevit et al. I’m not sure how any of those would affect seemingly random Watch windows in the Dynamo sandbox.
  • As mentioned, if anything, they seem to get narrow either after a run or possibly when opened.

Thank you again!

4

By loading a different version of the WPF library before Dynamo does. Windows application development can only load a single version of a library - you can’t use the Revit 2025.1 and 2025.4 in the same instance. WPF is the component which allows Dynamo to dispaly everything you see in the workspace - number sliders are just a WPF component; watch nodes and watch 3d as well. As such you have to rule out the problem isn’t coming from one of those before we can look into the other issues.

That said, if you can’t identify what it takes to reproduce the issue with the add-ins enabled then disabling them now is pre-mature. Figure out what you did if/when it occurs and then move onto resolving it.

If I recall the ‘fix’ which was underway and I think released was providing a single item to the node on the first run, and then a list on the second run without disconnecting the input.

5

Thank you again for the quick response and the thorough explanation.

I will endeavor to trace down what events lead to this happening and if I can reproduce the same results.

Once again, thank you for your help!

1 Like