I am trying to build a NodeDialog for an optional input data port, but when the data port is not attached, the configuration fails and I get an “Error loading model settings”. I can’t get my NodeDialog to not load Dialog Components when they are not required. How is that done? A longer description of what I am trying to do… I’m building a node that is designed to manipulate data in only a subset of rows. Instead of re-inventing the ‘Row Splitter’ node, my node is designed to sit directly downstream of either a Row Splitter or Row Filter. My NodeDialog has configuration options for Port 0 (required) and similar configuration options for Port 1 (optional). My two configuration panels called “Top Input” and “Bottom Input” allow the user to define the data manipulation they want. The idea is that you can manipulate both halves of your data and then glue it all back together again in a single node. I am using a combination of DialogComponentColumnFilter2 and DialogComponentColumnNameSelection components in both the “Top Input” and “Bottom Input” panels. The user selects the multiple columns they want manipulated, then the individual columns that do the manipulation. Both DialogComponents need to be told which Input Data Port they ought to point to (0 or 1), but as Port 1 is optional and null I’ve been getting errors. My first attempted fix was to add a loadAdditionalSettingsFrom function to check if the optional data was available. My thought was to re-route all of the DialogComponents to Port 0 if Port 1 was not available (and then just ignore it). But I discovered that loadAdditionalSettingsFrom isn’t even triggered unless both Port 0 and Port 1 are connected! I’m stuck. Ideally I would like the “Bottom Input” configuration panel to completely disappear if there is no Port 1 data. But at this stage I’d be happy with any solution that blocked the error message from appearing.

Configuration Dialog for Optional Input Port

Vernalis December 11, 2018, 11:21am 5

Thanks @Edlueze - that’s definitely a limited use case workaround! There are a couple of other gotcha’s with the DialogComponentColumnFilter2 panel (see e.g.

and

), which @gab1one was going to look into - maybe this optional behaviour might also be added to the list…

Steve

1 Like