On Dropping into panel Win vs Mac

Bugs
1

Hi!
2023.12370 Win/Mac

There is a different panel values behavior between Mac and Windows when dropping into the COMP panel.
Also, there is different panel values and callbacks behavior when dropping TD items (like OPs, parameters, etc.) vs. external files.

Here is a side-by-side video for Windows/Mac:
download for easier scrubbing

or watch:

Here are the differences in behavior I’ve noticed:

  • Blue – expected values
  • Red – wrong values when dropping TD items
  • Yellow – wrong values when dropping external files

Screenshot (305)
Screenshot (305)1386×1126 102 KB

Project file used for this:
onDropToCOMP.toe (6.6 KB)
Top left corner - callbacks log and time frame
Top right corner - panel value changed and time frame
Press 1 to clear log

The most frustrating part is that it’s impossible to track panel UV values when hovering external files on Windows now and hard to track hover start external file on both Mac and Win

Best,
Alex

2

Also:
2025.30960 has the same isues and additionaly onHoverEnd callback does not happen at all (windows at least)

Best,
Alex

3

Hi @letsius,

thanks for reporting this, we are having a look.

cheers
Markus

1 Like
4

Hi @snaut ,

Here is an update for 2025.32280:
Noticed that panel values and callbacks also differs when hover/drop into panel opened inside network editor (viewer active flag) vs separate window (RMB→ openviewer)
Here is a table with all differences I’ve noticed for mac/win and editor/separate window and td items/external files

Hope this will help.

I realize this may look like a lot of work (and a lot of edge-cases), and I totally understand if it can’t all be addressed quickly. But even if you could spare a bit of time to unify just the onHoverStartGetAccept and onHoverEnd callbacks (so they behave consistently across Network Editor viewer-active vs a separate Open Viewer window, and across platforms), that alone would make a huge difference on my side.

It would honestly be a massive quality-of-life improvement for my workflow, and I’d be infinitely grateful.

Cheers,
Alex