There is no ghost in the machine
But you do still need the ParentZone, if you leave it out of the SubZone, only the parameter names display, no values.
Here's an interesting one I'm experimenting with. Using the FXMenu with the FocusedFXNavigator (best of both worlds?)
Here's how:
Code:
Zone FXMenu|1-8
SelectedTrackNavigator
DisplayUpperD| FXNameDisplay |
DisplayLowerD| NoAction
RotaryD NoAction
/ RotaryPushD| GoFXSlot |
RotaryPushD1 Reaper _S&M_SHOWFXCHAIN1
RotaryPushD2 Reaper _S&M_SHOWFXCHAIN2
RotaryPushD3 Reaper _S&M_SHOWFXCHAIN3
RotaryPushD4 Reaper _S&M_SHOWFXCHAIN4
RotaryPushD5 Reaper _S&M_SHOWFXCHAIN5
RotaryPushD6 Reaper _S&M_SHOWFXCHAIN6
RotaryPushD7 Reaper _S&M_SHOWFXCHAIN7
RotaryPushD8 Reaper _S&M_SHOWFXCHAIN8
ZoneEnd
Selecting a track puts up the FXMenu (Auto option checked in prefs), but instead of using GoFXSlot, which won't work with the FocusedFXNavigators in the FX.zon files, it uses the SWS commands to open an FX chain window with the selected FX highlighted.
Advantages are that you get to use the FXMenu and you get a window showing the selected plugin.
I'm currently testing to see how reliably it maps the widgets when the FX chain window opens, although you can still use the PREV/NEXT commands to step through the slots.