Feature Request: Interconnect attributes

[charabaruk]

Support for the ICA_TARGET and ICA_MAP attributes on BOOPSI gadget and interconnect classes (e.g. #?.gadget, icclass, modelclass; the latter two not yet supported in ReBuild). This should be presented as a separate form for supported types, similar to how layout child attributes are presented on their own form for each object in a window.

ICA_TARGET requires being able to pick another object in the window. ICA_MAP requires maintaining a tag list of source object attributes to target object attributes. Source attributes need to apply to OM_NOTIFY and target attributes to OM_UPDATE; attributes which don't apply to those messages can still be used but they are not likely to work. Likewise the attributes have to have the same value type or Bad Things(TM) will happen.

If direct support for icclass is added, then target attributes should be from the class of the object that the icclass object itself is targeting, same for any possible subclasses of icclass other than modelclass. For modelclass or any custom subclasses, there should be no restrictions on target attributes as it is expected that the target class will know what to do.

[dmcoles]

it is already possible to include a small number of hard coded connections between components which output the relevant ICA_TARGET and ICA_MAP definitions to the code.

1. An integer control can be linked to a slider.
2. a text editor (or textfield) control can be linked to a scroller.

Its a lot of work to add generic support for ICA_TARGET and ICA_MAP. It would mean adding all of the OM_NOTIFY ad OM_UPDATE attributes for each component and i'm really not sure how many of these would actually ever be useful to connect.

It might be easier to expand out the list above if you can think of any other scenarios where the attributes of two components can usefully be connected.

[charabaruk]

It's exactly generic support that I'm thinking about, especially with an eye towards support for subclasses of modelclass like the BoopsiWizard "Simple Class" template makes. Right now I'm just immediately focusing on generic interconnections though, since there'd be even more work required for supporting custom classes right now.