1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

core workflow improvement

Discussion in 'Feature Suggestions' started by colB, Oct 4, 2011.

  1. colB

    colB NI Product Owner

    Messages:
    3,969
    Often when working in core, I end up with a lot of stuff going on in one window. Periodically, I have to create new marcos to package up sections of code and tidy things up. When given sensible names, these macros really make it easier to understand and debug the module.

    One of the most annoying time consuming parts of this is creating inputs and output for all the existing connections that I have just moved inside a new empty macro.

    My suggestion is to have a drag and drop feature where if you drag a wide from the input of an inner macro and drop it in the vertical input section of its enclosing core macro, an input of the same type and name would be automatically created.

    This suggestion would of course be useful generally when creating any new macro within a core macro that needs to be connected to an input and/or output.

    This would save me loads of time, and should be trivial to implement - I can't think of any major issues where there would be ambiguities to resolve.

    I did suggest this a long time ago in the reaktor6 suggestions, but it quickly got burried, and I think it would be useful to add to the next reaktor5 version.

    cheers

    Col
     
  2. James Nicholl

    James Nicholl Forum Member

    Messages:
    354
    Even better - select a group of macros/modules then ctrl-M or right-click and select "make macro".

    The selected group of macros/modules is then replaced by a macro that contains the selected group of macros/modules, completely wired up, no different in function from the original structure.

    The terminal names could be inherited from the ports on the inside of the macros, where possible. This auto naming wouldn't be perfect, but it would be a good starting point from which the user could name the terminals manually.

    The inverse function shift-ctrl-M "unmake macro" would also be useful.

    Also, simply dragging a module onto a macro could move the module into the macro, automatically wired. Then the inverse to this, a right click option to move the selected group of modules/macros outside of the macro.
     
  3. colB

    colB NI Product Owner

    Messages:
    3,969
    Yes, this would also be another useful addition, but not a replacement for drag and dropping wires into the in and out strips. that can be used at times when you're not macroizing a group of module. Pretty much any module you add to your macro that needs one or more connections to the in or out sections of the macro can be speeded up by the drag and drop idea.

    I would love to be able to macroize a selection though.

    Col