A few other thoughts...

[gurulogic]

I haven't really thought these all out all that well so probably there is already easy solutions for some...?

1-I would like to have additional midi input and output modules (like the addional audio inputs and outputs) This would provide for easier and greater flexibility in routing multiple midi devices to and from a single track.

2-Would it make sense for midi remote out to only send out to one specific port for any specific control? I am thinking this must cause an increase of cpu and possible audio interruption, especially when sending a large burst of midi CC values during a preset change? Or does this not make any difference?
Of course you would then want to be able to select a specific midi port from the Remote (send out) menu... maybe a stupid thought?

3-ok,so I'm lazy but if an interface control item can send midi remote why not make it so that it can send midi cc data without having to learn midi or go through a create midi module? I think all it would take is the ability to manually edit the Control type in the remote editor? Everything else is there already...

4-A "swap value module" would seem to be usefull. Two input pins whos values are able to be swapped at the two output pins when the swap inlet is triggered. This is patchable but I haven't found a super simple goto method?

5-show hide module to control visibility of top parent patch in ib

6-the ability to set the two output values for the toggle module

7-output a value of 1 if input value is between values A and B module

8-same as above but output a value of 1 if input value is outside values A and B

9-an if A=Y? then B= Because module... (kidding)

There's a few more but I don't remember right now....I always forget to take notes when I'm deep in patching and have ideas that I think would make my life a little easier .

Edits:----------------

10-module to control toolbar locations ( current position snapshot and scroll)

11-global interface resize to scale an interface to fit any screen resolution!

---------------
12-Vertical Text Field

-----------------
13- XY position inlets for containers to set position of container in parent container or interface builder (I wouldn't be staring blankly at my screen right now wondering what to do if USine had this...! )

[senso]

many interesting suggestions.

[gurulogic]

many interesting suggestions.

probably too many to absorb at once, lol

here's another one...

-freeze new value for X amount of time then resume previous value, so say original value is 0 and then 1 is received, 1 will be the frozen value for the duration of the timer, then 0 would be sent when the timer expires.
Perhaps just some better facilities in general for setting duration of events and when they should happen?
For example, being able to send a value if nothing has changed for X amount of time, or perhaps a midi note when triggered will last an exact amount of time?

I suppose I should try patchingf this before asking too many favors...