Hi!


See notes below...

>Hi everyone:
>
>(My first UT post...)
>
>I installed 7.0 a few days ago, in great anticipation that some
>of the bugs in 6.0 would now be history. Unfortunately, testing
>revealed that 7.0 still has them. Maybe these are features
>instead of bugs? If anyone can point-out to me why these are
>not bugs, I'd genuinely appreciate it.
>
>Bug / feature #1: Setfocus() doesn't work from Lostfocus().
>In a screen control's Lostfocus() event, doing:
>
>IF (some condition)
> This.Setfocus() && Keep the focus on this control
>ENDIF
>
>...never works, the focus always moves to the next
>control on the form (yes, Valid() will keep the focus
>on the control, but I have various reasons why I
>don't want to have to use Valid()).
>

This was never a bug in VFP. This is default behaviour of all Windows controls - you cannot change focus from the process of losing focus. THere is also a lot of worarounds and dolutions, for example:

IF (some condition)
   <b>nodefault</b>  && Keep the focus on this control
ENDIF

or just use return 0 in the Valid event of control.


>Bug / feature #2: Grid Scrolled event doesn't fire when
>scrolling the grid.
>
>If you use the mouse to scroll grid contents, Scrolled
>fires. If you use the arrow keys or page-up/down,
>Scrolled does not fire even though the grid contents
>are in fact being scrolled!

You can catch this in the AfterRowColChange event.

>If these are bugs, and they seem to be, I guess I'm
>having a little trouble understanding why 7.0 would
>have been released with bugs from 6.0 still not
>fixed...
>

Because only critical bugs are fixed that have no workaround or cause a lot of programming to workaround them. These 2 have simple solutions. There are a lot more of other things to do that are more important for new versions of VFP.

>Any input on this would be appreciated.
>
>Thanks,
>
>Michael Guiraut
>SVAS.
>
>P.S. On a positive note, at least 6.0's textbox
>background color bug seems to be fixed in 7.0.

There are a lot of fixes and improvements, indeed ;)