I am using a UltraTextEditor bound to a db field to feed the value to an UltraListView which will use the value to manipulate the SelectedItems collection. As I scroll through records and the value of the TextEditor changes I update the UltraListView SelectedItems collection accordingly. This works just fine until I set the UltraTextEditor:Visible property to FALSE. Once I do this neither the Textchanged or ValueChange event fires any longer. Is this working by design?
I was not able to reproduce the behavior you describe here with a simple test. When bound via the DataBindings collection, the UltraTextEditor's TextChanged and ValueChanged events fired as expected when the current record changed, even when the it's Visible property was set to false. You might want to log an incident with Developer Support so you can attach a test project that demonstrates this behavior.
Is the texteditor.Visible property initialized to TRUE? If so it will work as it does here. What I am seeing is if the Visible property is initialized to FALSE then the event will never fire. However, if it initializes to TRUE and then you set to FALSE via code it will fire.
No, I hadn't tried setting it to false at design time; in your original post you didn't stipulate that so I didn't think to try it. I do see now, however, that this issue exists for a standard TextBox as well, indicating that the behavior is inherited from the Control class, which we have no control over. Given that setting it to false at runtime instead of design time solves the problem, it would seem a simple workaround exists.
Correct, in my first post I did not stipulate that. After you said you could not see the behavior I knew there had to be something different between yours and mine and that is when I tracked it back to Visible = FLASE at design time. I have implemented the workaround where Visible = TRUE at design time and the set it to FALSE at runtime.
Thanks for the help.