Page 2 of 2
Re: Very Old Date problem
Posted:
Wed Apr 27, 2016 12:40 am
by nageswaragunupudi
Mr Antonio
Try to block one or two characters with mouse and then type.
In case of character variable, the typed character replaces the blocked characters. In case of Date this gives unexpected results.
Re: Very Old Date problem
Posted:
Wed Apr 27, 2016 12:16 pm
by Rick Lipkin
Antonio
Adding Set( 29, .T. ) has no effect ... the trick to the error is to set your cursor directly over and hi-lite the last digit 6 of the year and type over it with a different number like 7 .. you will see how the date becomes invalid.
I have seen this where data entry people make a mistake in entering a date 04/27/2016 and meant to enter 2015 as the year .. they go back and ONLY hi-light the 6 ( not the entire date ) and change it to ( something else ) 5 .. and that is where the date resolves as invalid.
Thanks
Rick Lipkin
Re: Very Old Date problem
Posted:
Wed Apr 27, 2016 3:00 pm
by James Bott
Rick,
OK, now I see the problem. Before I was assuming the cursor was in the overtype mode, and I also tried insert mode. I didn't think to try highlighting the last character. I would ever do it that way, but with many users, someone is going to do just about every possibility.
It does seem to be a bug. I'm guessing in xHarbour, since that is where the old Clipper GET code is.
James
Re: Very Old Date problem
Posted:
Wed Apr 27, 2016 3:20 pm
by nageswaragunupudi
I think the fix is required in fwh code only.
We are looking into it.
Re: Very Old Date problem
Posted:
Wed Apr 27, 2016 4:11 pm
by Rick Lipkin
Rao
Thank you !!!
Rick Lipkin
Re: Very Old Date problem
Posted:
Thu May 12, 2016 12:08 pm
by Rick Lipkin
To All
Wanted to keep this on the radar scope .. Thanks
Rick Lipkin
Re: Very Old Date problem
Posted:
Thu May 12, 2016 12:19 pm
by nageswaragunupudi
Not yet solved.
But I too have it on top of my mind.
Most likely in fwh 16.05
Re: Very Old Date problem
Posted:
Thu May 12, 2016 7:18 pm
by Rick Lipkin
Rao .. thanks
Re: Very Old Date problem
Posted:
Thu Aug 11, 2016 5:49 pm
by Rick Lipkin
To All
Wanted to once again put this back on the radar scope..
Thanks
Rick Lipkin
Re: Very Old Date problem
Posted:
Sun Oct 23, 2016 8:40 am
by Antonio Linares
It seems as the bug is related with method GetDelSel()
If I comment its call from here (class TGet)
- Code: Select all Expand view
::GetSelPos( @nLo, @nHi )
// Delete selection
if nHi != nLo
// ::GetDelSel( nLo, nHi )
::EditUpdate()
endif
then I can block the latest digit from the year and I can properly replace it
Re: Very Old Date problem
Posted:
Sun Oct 23, 2016 9:30 am
by Antonio Linares
Please discard my previous message. It looks to me more as an ::oGet:Insert() and ::oGet:OverStrike() issue
going to do some more tests
Re: Very Old Date problem
Posted:
Sun Oct 23, 2016 9:53 am
by Antonio Linares
I think this is a very good solution
- Code: Select all Expand view
METHOD KeyChar( nKey, nFlags ) CLASS TGet
...
case nKey >= 32 .and. nKey < 256
...
::GetSelPos( @nLo, @nHi )
// Delete selection
if nHi != nLo
if ::oGet:Type != "D" // new
::GetDelSel( nLo, nHi )
::EditUpdate()
else
::SetPos( nLo + 1 ) // new
endif
endif
...
Here it seems to work very well
We do appreciate your tests and feedback
Re: Very Old Date problem
Posted:
Sun Oct 23, 2016 10:13 am
by Antonio Linares
Changes included for next FWH 16.09
it is working nicely
Re: Very Old Date problem
Posted:
Sun Oct 23, 2016 4:12 pm
by Rick Lipkin
Antonio
Awesome .. and Very Grateful !!
Thank You
Rick Lipkin
Re: Very Old Date problem
Posted:
Mon Oct 24, 2016 3:21 pm
by Massimo Linossi
Thanks a lot Antonio
Massimo