Up and Down (OpenInsight 32-Bit)
At 06 NOV 2006 05:33:03PM W Shepard wrote:
To add Up and Down arrow responses to the Editfield, I have overridden the up and down arrow functions by creating two hidden menu items to respond to the up and down arrow keys. So far so good. Of course, that means I've had to write code to reproduce the functionality of the Up and Down keys for all the other different types of objects, too. Great, no problem, until you get to the Editbox. There is no way to get and set the cursor position in the EditBox, so there is no way to change it based on the up and down arrow keys.
1. Am I wrong? Is there a way to get and set the cursor position in the Edit Box?
2. Is there a way of passing the Up and Down arrow key requests on to the system when it's on a field other than an EditField?
3. Is there a way of giving the EditField Up and Down arrow key responses without interfering with the other object types?
Wayne
At 06 NOV 2006 07:07PM Bob Carten wrote:
I think the SELECTION property will do it
.EditBox_1-]Selection=newpos:@fm:0
At 06 NOV 2006 07:29PM [email protected]'s Don Bakke wrote:
Bad Bob, very bad Bob!
Surely you meant:
Set_Property(@Window:".EDITBOX_1", "SELECTION", newpos:@fm:0)
In the age of commuter modules how dare you post shorthand code!
At 07 NOV 2006 08:33AM Bob Carten wrote:
dang!
Now we have to write a commuter module pre-compiler that converts the set-property arrows without being confused by OLE arrows.
Thanks Don.
At 07 NOV 2006 08:34AM Mike Ruane wrote:
Must be our secret precompiler that handles shorthand in Basic+ programs…or something
At 07 NOV 2006 11:36AM W Shepard wrote:
I am getting freaking sick of testing things and having them not work and then coming on here asking what I should do and having people tell me to do exactly what I was doing and then doing it over and having it work just fine! I'm putting another posting on here and I've checked it with other people and verified that what I'm doing is exactly what's in the documentation and it's not not working because I did something wrong and THIS TIME it better not work tomorrow too!
At 08 NOV 2006 11:22PM Steve Botes wrote:
I just new there had to be an explanation of why that was happening to me too!