FiveTech Support Forums

Why the cursor don't go to the end of the value when it has entered mask?

When the get has a mask, the cursor goes until after the last character. But when he has some kind of mask, the cursor is always before the last character.

I thought that if I have the new fivewin version, this bug has been fixed but not.

How can I fix it?

Júlio,

I am pretty sure this is the same behavior of Clipper and Harbour has recreated it. With DOS Clipper apps, the font was a fixed size and now we have proportional fonts which also complicates things since each data entry may have a different physical length.

So, this is Harbour faithfully recreating the old behavior of Clipper. Weather or not this is a good thing is questionable.

Maybe Antionio can tell us more.

James

Ok James

We waiting!

Julio,
James,

The problem Julio is mentioning is sometimes enoying. It makes deleting the last character using the backspace impossible. It should be possible to put the cursor in non-insert mode (a line, not a block) just behind the last possible character.

I'm pretty used to is now, but my customers sometimes complain about it.

Regards,

Michel, James, Julio,

Its the way a Clipper GET behaves as James explained.

FiveWin Class TGet uses a Harbour (Clipper) GET in a DATA, and copy the results of its buffer and cursor position into the Windows GET. So what we see is what the Harbour GETs does.

Antonio Linares wrote:Michel, James, Julio,

Its the way a Clipper GET behaves as James explained.

FiveWin Class TGet uses a Harbour (Clipper) GET in a DATA, and copy the results of its buffer and cursor position into the Windows GET. So what we see is what the Harbour GETs does.

Linares, so is necessary to modify the xHarbour (Clipper) GET to get better results for cursor position into the Windows GET?
This prevents a good typing data.

Júlio,

Thats not as easy as it seems

What behavior should we modify ? We need to decide what Clipper behavior to keep and what behaviors to change.

And most important: we have to keep backwards compatibility. Pictures have to work fine, navigation keys, etc.

Antonio Linares wrote:Júlio,

Thats not as easy as it seems

What behavior should we modify ? We need to decide what Clipper behavior to keep and what behaviors to change.

And most important: we have to keep backwards compatibility. Pictures have to work fine, navigation keys, etc.

Linares, I agree with you! 100%!
But, if change the fivewin get class? Exists any way to do it? I think this might be a alternative way to do, but not the correct