It would be nice if the columns in the Debug window would be removed for nodes that are unused, either because they are set to be disabled or they are not connected to an output. Otherwise I have to scroll past many “undefined” entries.
Good point!
Should be fairly easy to do, stay tuned.
Try this one.
I have to fix the auto-update of the Debugger when you disconnect/connect nodes, but I have to go out now. Will do it later today.
Genome_MagmaFlow_20120407.zip (71.9 KB)
Whoa, it’s Saturday. You don’t have to do this for me. 
Though I am thinking that I am taking up a disproportionate amount of traffic on the Genome beta. Where did everyone go?
We are on a very aggressive dev./release schedule for 1.0, Release Candidate 1 should be out on Monday.
So anything I can fix now I will fix ASAP. I LOVE the fact you are pushing it and finding all these bugs, please don’t stop!
Cheers,
Bobo
it would be nice if every time I press <> buttons, the width of the columns wouldn’t be reseted. The same for the debugger window position/size, it keeps appearing almost off-screen
also if I highlight for example the first row, the info inside the ops is always from the first iteration regardless of the ‘First’ number
edit- i just realized that the debugger opens under the magma editor with the same width, nice. the problem is that I use it at the bottom of the screen 
Good point, thanks!
EDIT: Fixed internally.
Would it help if you had the option to open it above the Genome editor? Or should I open it depending on how much space there is above/below the Editor?
Cannot reproduce in the latest fix I posted last week. Wait for RC1 and check again.
Something bothering me, for tools with multiple outputs, we can’t distinguish the inputs in the Debug window. We don’t see which column is Position coords vs Barycentric coords vs Mapping coords. Maybe a label in the column, or highlighting the output in the node when the column is selected or something.
That’s a bug 
The values of multiple outputs used to be a single column before the last update.
When we implemented the new interface, I must have put them into multiple columns without noticing.
I can move them together again in a single column as in Krakatoa, or fix the title of the column to have the correct label and do the selection thing.
What do you prefer?
So VertexQuery could have hundreds of values in the same column? That seems a bit nuts.
No, it will only have as many values as it has valid outputs. NearestPoint and IntersectRay would have wider columns to fit all 7 outputs, but Krakatoa Magma does the same. The beauty is that you can resize those columns (now that the width will be preserved) and ignore what you don’t want.
I am going with multiple entries per column instead of multiple columns.
Now is the time to stop me! 
But VertexQuery et al CAN have a hundred valid outputs. Is it easy to find what is what when you have so much data in one column?
I am making it an Option
if possible I prefer the last position used, but based on how much space there is above/below could also work fine.
An option to “debug only selected nodes” it’s easy to implement? could be faster to work with
Cannot do that, because every Genome gets its own editor, and every editor gets its own Debug dialog. So if you open 3 editors, you don’t want 3 Debug dialogs on top of each other. Unless you want me to store the last Debug position in the modifier itself. I could try that, but I am not 100% sure it would be better.
Not easy, but I just finished it. The trouble was that changing the selection has to notify the Debugger to update differently (new columns, new results). Pressing Previous/Next also was getting out of sync if you changed the selection. I got it to work, but it was surprisingly convoluted.
Here is a WIP update:
*Added option to show the multiple outputs of a node as separate columns or within the same column.
*Clicking on the column head will select the node and the socket (if applicable).
*The name of the output socket will be shown in the column when needed.
*Added “Debug Selected Only” option.
I have not done anything about the location of the dialog yet. Have to think about it.
Genome_MagmaFlow_20120409.zip (72.6 KB)
Here is another update.
This one will remember the width of every column based on the Node type and output socket name. In other words, if you resize the NearestPoint column that shows all outputs in one, any other NearestPoint node in the future will use that width from that point on. If you switch to column per output socket, each column will store its own width, and remember it for future columns of this type.
The info is saved under the plugcfg folder, which is usually here:
C:\Users\YOURUSERNAME\AppData\Local\Autodesk\3dsMax\2012 - 64bit\enu\plugcfg\Genome
The file is called “MagmaFlowDebugger_Layout.ini”.
Deleting it will reset all custom column layout changes.
In addition, it will now open the Debugger below the Editor if there are more than 200 pixels left to the edge of the desktop.
If not, it will try to place the Debugger above the Editor (if there are more than 400 pixels left to the top edge of the desktop).
If neither cases are possible, the Debugger will open over the Editor, 100 pixels lower along the Y.
I might add “last position memory” in the future, but for now this should keep the Debugger close to its Editor while allowing multiple Editors with multiple Debuggers to be opened at the same time.
Genome_MagmaFlow_20120409b.zip (72.9 KB)