CSI v3 - Now Includes Auto-FX Mapping -- Use this for Setup Help, Bug Reports, etc.

[creal]

Originally Posted by Funkybot

Creal, try out the attached Faderport2Exp zone folder with the latest CSI Exp build.

Note: LinkLock should work but it's not really doing anything that isn't happening in other zones. I'm open to any/all ideas about what to do with this zone.

Thanks a lot Funkybot. I will test it as soon as possible (maybe at lunch, if not tomorrow). I can share my ideas about what each zone does in my setup.

[Geoff Waddington]

Originally Posted by creal

I agree everyone don't agree on a specific setup. However, I may be wrong, but the fact that Subzone buttons were not exclusive is incoherent from my point of view. I don't talk about what actions buttons do but the core functioning of the unit, which may have not been tested before release (Funkybot said that he doesn't own a FP).

I'm not sure what you mean here.

SubZone activation is mutually exclusive.

The method you used to turn the light on is not mutually exclusive.

Please clarify.

[creal]

Originally Posted by Geoff Waddington

I'm not sure what you mean here.

SubZone activation is mutually exclusive.

The method you used to turn the light on is not mutually exclusive.

Please clarify.

I don't use a personal method. I just use the "factory" files provided with CSI.

What I meant (just an example): pressing "Marker" goes into the "Marker" SubZone, then pressing "Section" does not leave "Marker" SubZone. We have to press "Marker" button again in order to use "Section" SubZone.

[MixMonkey]

Originally Posted by creal

I don't use a personal method. I just use the "factory" files provided with CSI.

You certainly want to use a personal method.

What I meant (just an example): pressing "Marker" goes into the "Marker" SubZone, then pressing "Section" does not leave "Marker" SubZone. We have to press "Marker" button again in order to use "Section" SubZone.

It works this way because that's what the author of the original Zones intended. You have to press the "Marker" button again because in the "Marker" SubZone the "Marker" button is assigned to LeaveSubZone, returning you to the Buttons Zone where another selection can be made.

You want to be able to navigate directly between SubZones and that's fine, but it isn't the way the Zones were written. Just because they don't work the way you want them to doesn't make them "wrong" or "incoherent".

[Geoff Waddington]

Originally Posted by creal

I don't use a personal method. I just use the "factory" files provided with CSI.

What I meant (just an example): pressing "Marker" goes into the "Marker" SubZone, then pressing "Section" does not leave "Marker" SubZone. We have to press "Marker" button again in order to use "Section" SubZone.

Ah, something is wrong there.

If "Marker" and "Section" share the same Parent Zone they should be mutually exclusive.

What is the Parent Zone of "Marker" ?

What is the Parent Zone of "Section" ?

[Geoff Waddington]

Originally Posted by MixMonkey

You certainly want to use a personal method.


It works this way because that's what the author of the original Zones intended. You have to press the "Marker" button again because in the "Marker" SubZone the "Marker" button is assigned to LeaveSubZone, returning you to the Buttons Zone where another selection can be made.

You want to be able to navigate directly between SubZones and that's fine, but it isn't the way the Zones were written. Just because they don't work the way you want them to doesn't make them "wrong" or "incoherent".

Ah, thanks, I was not aware of those Zone definitions.

[Geoff Waddington]

Originally Posted by creal

I don't use a personal method. I just use the "factory" files provided with CSI.

What I meant (just an example): pressing "Marker" goes into the "Marker" SubZone, then pressing "Section" does not leave "Marker" SubZone. We have to press "Marker" button again in order to use "Section" SubZone.

You could assign buttons to GoSubZone within a given subZone to do what you want I think.

Please post the contents of your "Marker" and "Section" zones as well as their Parent Zone.

You don't need to upload them, you can just post them inside tags like this, just substitute the word Code in place of Mode:

[Mode]

You Section Zone contents here

[/Mode]


[Mode]

You Marker Zone contents here

[/Mode]

[Funkybot]

Full disclosure: the Faderport2 files creal is using were setup by me and Pet. They're included in the CSI support files. I'm not a big user of SubZones so it sounds like I could have set those up better.

That said: it's become a moot point since yesterday as the Custom AssociatedZones have advantages over SubZones for that surface. Namely: the button feedback and RGB behavior should just work without hacks, and the navigation is simpler because the toggle is built in.

So my thinking is: funkybot has learned a little about SubZone navigation (have GoSubZone buttons in each SubZone so users don't need to go back to the enclosing zone first), but Custom AssociatedZones are better anyway, so let's just focus on making sure those are working and getting a good stock set of FP2 files using those.

I don't think it makes sense to have creal focus on what was wrong with the SubZones when we're replacing them anyway. Apologies for the headache.

[MixMonkey]

Originally Posted by Geoff Waddington

You could assign buttons to GoSubZone within a given subZone to do what you want I think.

This is how all my FX Zones (that contain SubZones) work. Whilst I haven't tried it, I can't see any reason that it wouldn't work for SubZones of the Buttons Zone.

The parent Zone defines the SubZones and all the Zones carry the navigation definitions that allow you to move between them:

Parent Zone:

Zone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)" "JP-8"
/Primary
/
SubZones
"VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-2"
"VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-3"
"VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-4"
SubZonesEnd
/
Button#1 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)"
Button#2 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-2"
Button#3 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-3"
Button#4 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-4"

SubZone#1:

Zone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-2"
/Sub
/
Button#1 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)"
Button#2 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-2"
Button#3 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-3"
Button#4 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-4"

SubZone#2

Zone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-3"
/Sub
/
Button#1 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)"
Button#2 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-2"
Button#3 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-3"
Button#4 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-4"

SubZone#3

Zone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-4"
/Sub
/
Button#1 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)"
Button#2 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-2"
Button#3 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-3"
Button#4 GoSubZone "VST3i: TAL-J-8 (TAL-Togu Audio Line) (6 out)-4"

...but all of this is now academic with the introduction of Custom Associated Zones (which also take care of the LEDs)

EDIT: @funkybot beat me to it

[creal]

Originally Posted by MixMonkey

You certainly want to use a personal method.

I do (present), but I didn't use (past) a specific method.

Originally Posted by MixMonkey

It works this way because that's what the author of the original Zones intended. You have to press the "Marker" button again because in the "Marker" SubZone the "Marker" button is assigned to LeaveSubZone, returning you to the Buttons Zone where another selection can be made.

You want to be able to navigate directly between SubZones and that's fine, but it isn't the way the Zones were written. Just because they don't work the way you want them to doesn't make them "wrong" or "incoherent".

Don't get me wrong. I'm not saying CSI is bad designed. On the contrary, I'm very grateful for providing such a tool. I'm just saying that when you plug your FP (I'm only talkind about the FP) and want to change SubZone, probably 99% of people expeceted the SubZones to be "muted" when switching frome one to another. I'm pretty sure it's the way it works natively in SO.

[creal]

Originally Posted by Funkybot

Full disclosure: the Faderport2 files creal is using were setup by me and Pet. They're included in the CSI support files. I'm not a big user of SubZones so it sounds like I could have set those up better.

That said: it's become a moot point since yesterday as the Custom AssociatedZones have advantages over SubZones for that surface. Namely: the button feedback and RGB behavior should just work without hacks, and the navigation is simpler because the toggle is built in.

So my thinking is: funkybot has learned a little about SubZone navigation (have GoSubZone buttons in each SubZone so users don't need to go back to the enclosing zone first), but Custom AssociatedZones are better anyway, so let's just focus on making sure those are working and getting a good stock set of FP2 files using those.

I don't think it makes sense to have creal focus on what was wrong with the SubZones when we're replacing them anyway. Apologies for the headache.

Thanks again. I cannot test it for now, but I will do as soon as I find a little time.

[Funkybot]

Originally Posted by creal

Don't get me wrong. I'm not saying CSI is bad designed. On the contrary, I'm very grateful for providing such a tool. I'm just saying that when you plug your FP (I'm only talkind about the FP) and want to change SubZone, probably 99% of people expeceted the SubZones to be "muted" when switching frome one to another. I'm pretty sure it's the way it works natively in SO.

Sounds like I could have setup the original FP2 files to do that a little better, so a big part of that was my bad! But the new Custom AssociatedZones and files I just shared with you, should work like you expect and be even better (lights and colors should work). So just let us know how the new files work!

EDIT:

Originally Posted by creal

Thanks again. I cannot test it for now, but I will do as soon as I find a little time.

No worries! I know how that goes! At work right now myself.

[Geoff Waddington]

Originally Posted by Funkybot

Full disclosure: the Faderport2 files creal is using were setup by me and Pet. They're included in the CSI support files. I'm not a big user of SubZones so it sounds like I could have set those up better.

That said: it's become a moot point since yesterday as the Custom AssociatedZones have advantages over SubZones for that surface. Namely: the button feedback and RGB behavior should just work without hacks, and the navigation is simpler because the toggle is built in.

So my thinking is: funkybot has learned a little about SubZone navigation (have GoSubZone buttons in each SubZone so users don't need to go back to the enclosing zone first), but Custom AssociatedZones are better anyway, so let's just focus on making sure those are working.

I don't think it makes sense to have creal focus on what was wrong with the SubZones when we're replacing them anyway. Apologies for the headache.

Yup, I just had a look at those Zones, it would be trivial to modify them to do what creal wants, and maybe we should do that anyway, even if we use Custom Zones to accommodate his workflow.

Which brings us to...

CSI seems to be fairly stable with the new features, I know, I know, always bugs to swat, but overall just continuing work to do.

I know this is hard, but I think, judging by the traffic on this thread, we should review each and every setup.

I don't know how formal it should be, but at least you, MM, and myself, along with anyone that wants to join in.

The goal is the "best" starting point for each setup, an impossible task, for sure, but I think we can do better with the "stock" Zones than what we have now.

What do you think folks, especially MM and FB ?

[edit] Haha I had to take a call as I was composing this so I missed the latest traffic, looks like everyone is more or less in agreement already

[Geoff Waddington]

On another note, can you folks please verify that Custom Zones work properly within your workflows so that I can promote them to production.

[Funkybot]

Originally Posted by Geoff Waddington

On another note, can you folks please verify that Custom Zones work properly within your workflows so that I can promote them to production.

Will try to get to this later today.

[MixMonkey]

Originally Posted by Geoff Waddington

What do you think folks, especially MM and FB ?

I think the only support files that should come with CSI should be those for the XTouch, XTouchExtender and XTouchOne on the MIDI side and the simple iPhone remote on the OSC side.

All the others should be put in the Stash and either updated or not as the owner sees fit. Support for these surfaces would be better handled in their own, surface specific thread.

Trying to continually update the files for a surface you don't use or have access to is unlikely to produce satisfactory results.

Sorry if this sounds brutal, but I think it's realistic.

[georges]

Originally Posted by Funkybot

georges, if you happen to see this: please post your QCon zone folder too. I just want to see where and how you're mapping the various automap/learn functions.

Will pick this up tomorrow!

Sorry, just seeing this. ZIP file uploaded. For the QCon I'm using the X-Touch files.

[Funkybot]

Originally Posted by MixMonkey

I think the only support files that should come with CSI should be those for the XTouch, XTouchExtender and XTouchOne on the MIDI side and the simple iPhone remote on the OSC side.

All the others should be put in the Stash and either updated or not as the owner sees fit. Support for these surfaces would be better handled in their own, surface specific thread.

Trying to continually update the files for a surface you don't use or have access to is unlikely to produce satisfactory results.

Sorry if this sounds brutal, but I think it's realistic.

The downside is: the main user critique of CSI is that it's too hard to use. Including support files at least gets users up and running. But updating/testing is a bit of a nightmare.

I've contemplated the idea of having a "Surfaces" section on the wiki, then just having pages for each surfaces with example zone files. But it's the same problem as the support files and more work for users.

[TheSoundCamel]

Hi!
First of thank you so much for the work, I think this can be a game changer! I'm just wondering if there is something I'm missing regarding parameter "pick up". When I make adjustments to fx using an absolute knob and then move to another to make adjustments with the same knob, then going back to the first fx it snaps immediately when moving the knob instead of waiting till the knob is at the position corresponding to the setting. Is there something I'm missing or is this simply a limitation?

Thank you!

[Funkybot]

Originally Posted by georges

Sorry, just seeing this. ZIP file uploaded. For the QCon I'm using the X-Touch files.

Will take a look later. It's good you're using the X-Touch Files.

[MixMonkey]

Originally Posted by Funkybot

The downside is: the main user critique of CSI is that it's too hard to use.

That isn't going to change no matter how many support files you include. The simple truth is that the degree of versatility that CSI offers already puts the complexity level above what some people can deal with.

Even if you provide the files for a specific surface, there will be differing opinions on workflow, button choices etc, as we've just seen. Better that those discussions are amongst people that have already bought into that surface and are aware of its pros, cons and workflow limitations.

Providing the files for:
i) An MCU protocol based eight channel surface with expander.
ii) A single fader surface oriented toward SelectedTrack functions.
iii) An extremely simple OSC remote control (in my experience, people struggle most with the connection aspect of OSC)

...will cover the vast majority of surfaces out there and focusing on these will allow the files to stay current with changes to the syntax.

[creal]

Originally Posted by Funkybot

Creal, try out the attached Faderport2Exp zone folder with the latest CSI Exp build.

Note: LinkLock should work but it's not really doing anything that isn't happening in other zones. I'm open to any/all ideas about what to do with this zone.

I just tested quickly.

The "exclusive" behavior works as expected. However there are two problems:
- The buttons aren't lit anymore, except "Channel"
- It now triggers LED glitches with every button (Link, Pan, Channel, Scroll, Marker, Section, Master)

[MixMonkey]

Originally Posted by TheSoundCamel

Hi!
First of thank you so much for the work, I think this can be a game changer! I'm just wondering if there is something I'm missing regarding parameter "pick up". When I make adjustments to fx using an absolute knob and then move to another to make adjustments with the same knob, then going back to the first fx it snaps immediately when moving the knob instead of waiting till the knob is at the position corresponding to the setting. Is there something I'm missing or is this simply a limitation?

Thank you!

You didn't mention what surface you're using. Is there a reason you can't use inc/dec controls instead of absolute?

[creal]

Originally Posted by MixMonkey

That isn't going to change no matter how many support files you include. The simple truth is that the degree of versatility that CSI offers already puts the complexity level above what some people can deal with.

Even if you provide the files for a specific surface, there will be differing opinions on workflow, button choices etc, as we've just seen. Better that those discussions are amongst people that have already bought into that surface and are aware of its pros, cons and workflow limitations.

Providing the files for:
i) An MCU protocol based eight channel surface with expander.
ii) A single fader surface oriented toward SelectedTrack functions.
iii) An extremely simple OSC remote control (in my experience, people struggle most with the connection aspect of OSC)

...will cover the vast majority of surfaces out there and focusing on these will allow the files to stay current with changes to the syntax.

If you provide all the tools (and a user guide) to let the user make their own workflow, it will be fine (even if non-X-Touch users may leave the boat). But until today, for example, the FP2 did not work correctly (I don't only refer to the discussion in this thread but also to another thread that highlighted a bug in the code). So even with tools and a user guide, I would never have managed to run something usable.

[Geoff Waddington]

Originally Posted by creal

I just tested quickly.

The "exclusive" behavior works as expected. However there are two problems:
- The buttons aren't lit anymore, except "Channel"
- It now triggers LED glitches with every button (Link, Pan, Channel, Scroll, Marker, Section, Master)

Just checked the Zone definitions, I see what's wrong.

In the buttons Zone you have:

  Pan	GoAssociatedZone CustomPan { 0 1 8 10 10 255 }

So far so good, but in the CustomPan Zone you have:

 Pan				     GoHome

Remove that line from the CustomPan Zone and things should work.

You will also need to remove the equivalent ones from CustomScroll, CustomSection, etc.

[Funkybot]

Originally Posted by Geoff Waddington

Just checked the Zone definitions, I see what's wrong.

In the buttons Zone you have:

  Pan	GoAssociatedZone CustomPan { 0 1 8 10 10 255 }

So far so good, but in the CustomPan Zone you have:

 Pan				     GoHome

Remove that line from the CustomPan Zone and things should work.

You will also need to remove the equivalent ones from CustomScroll, CustomSection, etc.

Ah, thanks for that Geoff! Would not have caught that as the issue. creal, I can post an updated set after work unless you want to make the change yourself.

[creal]

Originally Posted by Funkybot

Ah, thanks for that Geoff! Would not have caught that as the issue. creal, I can post an updated set after work unless you want to make the change yourself.

I removed the lines.

Every LED works except the "Link" one. By the way, I have to remove "Shift + Link ------> Go Home" from the CustomLinkLock.zon file, not "Link ------> Go Home", as I expected compared to the other files.

In addition, glitches are still present.

[creal]

I also noticed another inconsistency:
When holding the "Click" button, in addition to showing the setting window, it also toggles the metronome.

By the way, where is the duration variable of the "hold" function, please? I'd like to put a lower value because for now, it's (I guess) 1 second, which is too long (300 ms would be enough, or even less).

[Funkybot]

Originally Posted by creal

I also noticed another inconsistency:
When holding the "Click" button, in addition to showing the setting window, it also toggles the metronome.

That's expected and can be changed. CSI doesn't wait before firing off the non-hold action. It fires off the action on press, then if there's a hold, it fires off the second action. To change it: I recommend using other modifiers instead of hold for that one.

[Funkybot]

Originally Posted by creal

In addition, glitches are still present.

Please describe the glitches. We can't see what you do. What kind of glitches? Do they flicker? Are they out of sync? Please be as detailed as possible.

[KuulArt]

Learn mode is not really working. I have @FB setup but after trying to Learn a plugin the save button does not save any mapping data. Here is the automap zone file that was created after doing the SaveParameters function.

Zone "VST3: SP2016 Reverb (Eventide)" "SP2016 Reverb" "Generated by Learn"
	MainDisplay1   TrackNameDisplay
	MainDisplay2   FXMenuNameDisplay
	BankD          RemapAutoZone
	BankDDisplay   FixedTextDisplay "Remap FX"

#Begin auto generated section
#End auto generated section
	OnZoneDeactivation  HideFXSlot
ZoneEnd

I did the mapping on the desktop version of MFTwistter. It showed all parameters on the desktop version and I could control the plugin but after hitting save it created that file and I lost the mapping + the ReMap zone now does not have any parameters showing.

Also - is it possible to reenter learn mode after one "learn" has been done? (I can not get past the first learn now) I would imagine that reentering "learn" mode would really speed up the design of each plugin to knobs. And lastly - how can I learn the push functions from MFTwister?

[Funkybot]

Originally Posted by KuulArt

Learn mode is not really working. I have @FB setup but after trying to Learn a plugin the save button does not save any mapping data. Here is the automap zone file that was created after doing the SaveParameters function.

Zone "VST3: SP2016 Reverb (Eventide)" "SP2016 Reverb" "Generated by Learn"
	MainDisplay1   TrackNameDisplay
	MainDisplay2   FXMenuNameDisplay
	BankD          RemapAutoZone
	BankDDisplay   FixedTextDisplay "Remap FX"

#Begin auto generated section
#End auto generated section
	OnZoneDeactivation  HideFXSlot
ZoneEnd

I did the mapping on the desktop version of MFTwistter. It showed all parameters on the desktop version and I could control the plugin but after hitting save it created that file and I lost the mapping + the ReMap zone now does not have any parameters showing.

Also - is it possible to reenter learn mode after one "learn" has been done? (I can not get past the first learn now) I would imagine that reentering "learn" mode would really speed up the design of each plugin to knobs. And lastly - how can I learn the push functions from MFTwister?

Are you using the same FXTwisterFXZones folder for all surfaces? I'd check that first. When you clicked Save, did you hit Save on the Desktop version?

Also, be sure you're not enabling Learn on other surfaces. If you plan on learning via the desktop, when prompted you want:

1. MFTwister - Learn/Automap/Cancel? Click Cancel.
2. iPad - Learn/Automap/Cancel? Click Cancel.
2. Desktop - Learn/Automap/Cancel? Click Learn.

You will be able to re-enter Learn mode if you want to make tweaks, but we need the files to save correctly first. EDIT: 1) see MM's post below, may be an issue re-entering Learn mode via the local TouchOSC. 2) I've been using the Remap window but you may want to add this so that you can activate an FX and launch Learn (assuming it works)...

Zone FXPrologue

MainDisplay1   TrackNameDisplay
MainDisplay2   FXMenuNameDisplay
/
BankC          LearnFXParams
BankCDisplay   FixedTextDisplay "LearnFXParams"
/
BankD          RemapAutoZone
BankDDisplay   FixedTextDisplay "Remap FX"
/
ZoneEnd

You can learn the push buttons if they're exclusive to a Cell. For example: you can Learn a push on A1 by just pressing the A1 button. But you can't Learn a Rotary on A1, AND a push on A1. To do that, you need to go to the remap window.

[MixMonkey]

Originally Posted by MixMonkey

When running the BCR2000_iPad .tosc patch on the computer @ 127.0.0.1, you can’t re-enter Learn mode (after having previously created a map using Learn mode via the dialog box, using the same setup). The Learn button on the TouchOSC patch does nothing, despite the message being received by CSI.

This is going to be a significant issue for people trying to use Learn mode with surfaces that don't have displays and want to use the computer screen to that end.

The potential exists to greatly increase the usefulness of Learn for smaller/cheaper surfaces (the XTouch Mini springs to mind) but only if it's possible to re-enter Learn mode from the computer screen.

[KuulArt]

Originally Posted by Funkybot

Are you using the same FXTwisterFXZones folder for all surfaces? I'd check that first. When you clicked Save, did you hit Save on the Desktop version?

Also, be sure you're not enabling Learn on other surfaces. If you plan on learning via the desktop, when prompted you want:

1. MFTwister - Learn/Automap/Cancel? Click Cancel.
2. iPad - Learn/Automap/Cancel? Click Cancel.
2. Desktop - Learn/Automap/Cancel? Click Learn.

You will be able to re-enter Learn mode if you want to make tweaks, but we need the files to save correctly first.

You can learn the push buttons if they're exclusive to a Cell. For example: you can Learn a push on A1 by just pressing the A1 button. But you can't Learn a Rotary on A1, AND a push on A1. To do that, you need to go to the remap window.

I got it to save by only learning on the desktop version. That was the problem. But how do I reenter the learn mode?

[Funkybot]

Originally Posted by KuulArt

I got it to save by only learning on the desktop version. That was the problem. But how do I reenter the learn mode?

See my EDIT to the post above. We were typing at the same time.

[Geoff Waddington]

I wonder if we should try to design a safety interlock mechanism.

Something along the lines of -- If you enter Learn mode and start learning on a Surface that shares its FX zone folder with other Surfaces, those other Surfaces are locked out from learning and saving.

Any ideas ?

[MixMonkey]

Originally Posted by Geoff Waddington

I wonder if we should try to design a safety interlock mechanism.

Something along the lines of -- If you enter Learn mode and start learning on a Surface that shares its FX zone folder with other Surfaces, those other Surfaces are locked out from learning and saving.

Any ideas ?

That sounds good It would be nice to get rid of the unnecessary dialog boxes, particularly as your response to them determines the success of the Learn process.

[Funkybot]

Makes sense to me.

[Geoff Waddington]

Originally Posted by MixMonkey

That sounds good It would be nice to get rid of the unnecessary dialog boxes, particularly as your response to them determines the success of the Learn process.

As you well know, I dislike modal dialogs, A LOT !!

Let's rethink Learn/AutoMap.

The simple way is to make Learn and AutoMap Surface specific only, no Broadcast/Listen.


Example workflow 1:

X-Touch presents FXMenu with FX names displayed.

User presses GoFXSlot.

X-Touch broadcasts GoFXSlot to SCE24.

If there is No Map, "NoMap" displays on SCE24.

Geoff ducks incoming projectiles from FB

User can now either press AutoMap or Learn on the SCE24.


Example workflow 2:

X-Touch presents FXMenu with FX names displayed.

User presses GoFXSlot.

If there is No Map, "NoMap" displays on X-Touch.

Geoff ducks incoming projectiles from FB

User can now either press AutoMap or Learn on the X-Touch.



No dialogs, at the expense of bringing back "NoMap", but slightly differently, "NoMap" only displays when the user presses GoFXSlot.

Ok, that's a starting point for the discussion, have at 'er folks

[creal]

Originally Posted by Funkybot

That's expected and can be changed. CSI doesn't wait before firing off the non-hold action. It fires off the action on press, then if there's a hold, it fires off the second action. To change it: I recommend using other modifiers instead of hold for that one.

Okay. If I understand correctly, that design cannot be changed?

I found it very smart, btw.