1. RE: Selecting Text (Win32Lib bug)
It *is* a bug.
Until it is fixed you can use:
VOID = sendMessage( TheEditText, EM_SETSEL, 0, -1 )
Derek:
In version 0.57.9, line 16321
Why "index -= 1"? For RichEdits maybe?
When I comment out that line, it fixes this issue for
window_family[ id ] = EDIT.
-- Brian
Brian Broker wrote:
> *Should* be the same function as what you'd use for a RichEdit control:
>
> setIndex( TheEditText, {0, -1} )
>
> If this is not the case then I'd call it a bug...
>
> -- Brian
>
> Virtual B wrote:
> > Hi all,
> >
> > Does anyone know if there is a way to select text in and EditText? I
> > know it can be done in a RichEdit, but I can't seem to find a way to do
> > it in an EditText. What I'm trying to do is select the text in the
> > EditText when the user tabs to it, so that the new info can be typed in
> > without having to delete the existing text.
> >
> > Thanks,
> >
> > Virtual B
>
>
2. RE: Selecting Text (Win32Lib bug)
Thanks Brian and Derek. That did the trick.
Virtual B
Derek Parnell wrote:
> ----- Original Message -----
> From: "Brian Broker" <bkb at cnw.com>
> To: "EUforum" <EUforum at topica.com>
> Subject: RE: Selecting Text (Win32Lib bug)
>
>
> > It *is* a bug.
> >
> > Until it is fixed you can use:
> > VOID = sendMessage( TheEditText, EM_SETSEL, 0, -1 )
> >
> > Derek:
> > In version 0.57.9, line 16321
> > Why "index -= 1"? For RichEdits maybe?
> >
> > When I comment out that line, it fixes this issue for
> > window_family[ id ] = EDIT.
> >
>
> Sorry, the bug is in the documentation. Use the following command ...
>
> setIndex(myedit, {1, 0} )
>
> ----------------
> cheers,
> Derek Parnell
>
>
