Unregistered
December 12, 2002, 18:24:15
Support,
I don't know if this is a bug, or if multiple commands present the same, but think I should pass it on, just in case.
We are not at the point that we are manipulating in any way the TX control. We are still working on our framework, with the fundamental functions: creating controls, opening, saving, user options, routing menu and keyboard commands, etc.
What we noticed though is if in our FileOpen procedure we end it by setting the input position with Selection.Start = 0 the control loses focus. (We needed to do this in working with v8, else the caret didn't show, though such is unnessary in v10 net.) No m_ActiveTX.Focus, or any other commands seems to be able to get the focus back.
Thought you might want to test this before the final release. (Sorry we don't have more scenarios to give.)
This message was originally posted by Vann Joe in the old TX Text Control Support Forum.
I don't know if this is a bug, or if multiple commands present the same, but think I should pass it on, just in case.
We are not at the point that we are manipulating in any way the TX control. We are still working on our framework, with the fundamental functions: creating controls, opening, saving, user options, routing menu and keyboard commands, etc.
What we noticed though is if in our FileOpen procedure we end it by setting the input position with Selection.Start = 0 the control loses focus. (We needed to do this in working with v8, else the caret didn't show, though such is unnessary in v10 net.) No m_ActiveTX.Focus, or any other commands seems to be able to get the focus back.
Thought you might want to test this before the final release. (Sorry we don't have more scenarios to give.)
This message was originally posted by Vann Joe in the old TX Text Control Support Forum.