Oct 16, 2013, 10:25 AM
[CLOSED] TriggerField and "lookup" behavior when disabled
Hello,
I am experiencing an issue that prevents the listeners for any "field" that is disabled or set as readonly.
I created my own "Lookup" control (inheriting a TriggerField) that tracks the "Id" of a record on its "value" field.
2) the user can choose an record finding by name or searching.
3) the user can, clicking on the selection, open the "detail" window for that specific record,... so it does behave like a "link".
Now, all works fine, except case "3" when the control is disabled.
The issue is that ALL the trigger buttons and all the listeners for that field are disabled. This can be seen as "by design", however I wonder what happens if we need to have a "click" listener enabled to "navigate" to that record (case 3 state above) also when the control is actually disabled?
Is there a way to override the way each since trigger is enabled/disabled on a TriggerField control?
Thank you for help,
Cheers
I am experiencing an issue that prevents the listeners for any "field" that is disabled or set as readonly.
I created my own "Lookup" control (inheriting a TriggerField) that tracks the "Id" of a record on its "value" field.
2) the user can choose an record finding by name or searching.
3) the user can, clicking on the selection, open the "detail" window for that specific record,... so it does behave like a "link".
Now, all works fine, except case "3" when the control is disabled.
The issue is that ALL the trigger buttons and all the listeners for that field are disabled. This can be seen as "by design", however I wonder what happens if we need to have a "click" listener enabled to "navigate" to that record (case 3 state above) also when the control is actually disabled?
Is there a way to override the way each since trigger is enabled/disabled on a TriggerField control?
Thank you for help,
Cheers
Last edited by Daniil; Oct 22, 2013 at 2:37 PM.
Reason: [CLOSED]