Quote:
Originally Posted by mschnell
Does the "Learn" feature use additional files for saving it's result or does it allow to corrupt the normal straight-forward configuration files ?
IMHO it would make a lot of sense to keep these bits of information separate.
In fact I think it usually would be useful to have the "normal" configuration global but the "learned" stuff (supposedly mostly plugin assignments) per project.
OTOH allowing to use either configuration method to dedicatedly do as well global as project specific settings might be nice, too.
-Michael
|
It doesn't "corrupt" anything
It's just an alternative to a text editor -- another way to edit the same files we're all used to.
When complete, it will also have the advantage of being real-time -- make change -- test change -- save change.
Mapping a plugin will consist of these steps:
Focus Plugin
Open Learn Window
Click "New" button for a new file - since there is a focused Plugin, CSI guesses you want to map it, and sets up the filename and Plugin Zone name automatically.
Press OK
Move a control on your surface -- it is selected in the left window and displayed in the edit box
Select an Action in the right window
Press "Add To Zone"
Test -- in real time
Repeat for as many parameters as you want mapped
Press "Save" -- saves .zon file
Close Learn Window
Back to what you were doing.
As far as per project, CSI explicitly disallows per project settings, to keep it more predictable and portable.
It is fundamental to the design.
Have you got a project specific use case in mind ?