...
You can edit and remove a configuration by clicking the Edit/Delete icon on the Live Fields configuration page.
| Info |
|---|
| title | Wait! Only one configuration per project or category ? |
|---|
|
Yes, and it was a design decision we had to take. The motivation for this is very simple, it all boils down to performance and predictability. - Launching an interpretor is a complicated task, which we want to avoid doing multiple times, especially when you have to react as fast as possible because you need to hide some fields on the screen
- Imagine you have 2 scripts. Script 1 hides a field, script 2 shows the same field. Sometimes script 1 terminates faster than script 2, sometimes is the other way around. Leaving aside that you would probably have to coordinate this from the client, how do you apply them? Imposing an order would be the same as writing just one script.
We therefore believe that one script is enough; you can use includes to share behavior between different configurations. |
| Info |
|---|
| title | Precedence in applying LiveFields |
|---|
|
Note that a Project LF configuration takes precedence over a Project Category LF configuration, if they happen to overlap. |
...