Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
BUG: one page on a PageFrame is
Message
De
21/06/2004 23:15:37
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Visual FoxPro Beta
Divers
Thread ID:
00915585
Message ID:
00915904
Vues:
17
David,

Just to finish off my end of this...

I **DID** take it up with you directly.
I acknowledge, and did so also in the post to DavidS to which you replied here, that you denied such.

I expressed that it still looks otherwise despite the denail. And, to me (and seemingly a few others) it STILL looks so.

Enjoy your beta testing and keep those bug reports flowing to MS.

good night,
Jim

>Jim,
>
>If you have an axe to grind with me do it directly.
>
>I stand completely by my labeling the initial bug report in this thread as "useless" based on the standard bug report that Microsoft wants. If you don't like, well that's just tough and just another thing that you and I disagree on.
>
>Fabio is using the UT to post Europa beta bugs. Fabio has also stated in several messages over the last few days that he is not posting them to the normal bug report system. Fabio has been pointed to the bug posting standards that Microsoft wants to optimize their time dealing with the bug report. My simple little post has been blown vastly out of proportion here by you. And now I'm done wasting my time on you on this thread, I'd rather be doing productive beta testing on Europa.
>
>>David,
>>
>>Who said that FabioL was writing a "bug report" in the first place?... not FabioL.
>>
>>I'd say FabioL was "reporting a bug on the UT" and that it was DavidF's incorrect assertion that FabioL's report was "useless".
>>
>>I've seen people ask for help on bugs where they provide far less detail than FabioL does and I haven't seen DavidF wirting to them when their requests are in fact useless!
>>
>>I'm sure that FabioL knows full well the officially prescribed Microsoft 'format" for a "bug report". My guess on the matter is two-fold:
>>1) MS does pick bugs up here where the format is NOT as prescribed.
>>2) Why send something to a black hole where, if there was some problem reproducing the anomoly it gets killed with you being informed anyway???
>>
>>I think it's pretty clear to most, despite denials, that DavidF does have some axe to grind about FabioL's posts here. Which is unfortunate for DavidF and which I earnestly hope will not deter FabioL from cintinuing his fine work of isolating bugs in VFP.
>>
>>cheers
>>
>>>Grigore,
>>>
>>>>I won't interfere in the harsh talk I see here. I just want to point that Fabio in his form added two arrows - one on the left side of the tab (wich is a vertical line, btw), and one on the right side (which as an offset). I needed 2 seconds to figure what he want to show.
>>>>
>>>>If it wasn't hard for me, I bet it isn't for others, including Microsoft team that surveilles these treads.
>>>
>>>There is a reason that Microsoft's recommended format for bug reports includes data about the tester's version of VFP and OS, plus:
>>>
>>>
  • Steps to Repro

  • >>>
  • Expected Behavior

  • >>>
  • Observed Behavior

  • >>>
  • Comments

>>>Bug reports should be very detailed and very specific so the person processing the report can easily repro it, see and confirm the "observed behavior" and get the bug into the system. If the bug report is not specific enough to say just what the problem is, it's a waste of time for the VFP bug report team.
>>>
>>>Nothing personal against anyone in particular -- that's just the way it works most effectively and with the least confusion.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform