I'm going to have to go on record as agreeing with Buzz. And with Tom. :-)
>From the practical standpoint of what the mind expects, far models rendering in front of near models is indeed the root "unexpected behavior:" Q: Who is the customer here? A: The developer; the end-user. According to most quality assurance guidelines I've ever worked under, Macromedia and the Director Product Team have not, in this case, met the customer's requirement that models in the 3D environments they create in Director appear in correct apparent distance order. In the strictest of all global terms, THAT is was is defined as a bug. Now, with that said, we turn to the technical side. Tom is correct in saying that, because what is actually happening is not an "unexpected behavior" from the vendor's viewpoint -- that the 3D engine is performing exactly as implemented -- it cannot be classified as a bug. As far as Macromedia's tracking databases are concerned, it shouldn't be. But it should most definitely be logged as a customer requirement not met by the development team, and an issue to be dispositioned in the next release. ��������������������������� Christopher Watson Sr. Software Engineer Interactive Web Media Lightspan, Inc. Tel 858.824.8457 Fax 858.824.8001 ___________________________ -----Original Message----- From: Buzz Kettles [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 2:32 PM To: [EMAIL PROTECTED] Subject: RE: <lingo-l> dear macromedia (bug again) I have to disagree Tom (& I certainly know & understand the semantics involved in labelling something a bug) In this case, however, one of the primary premises of working in 3D space is that nearer objects render in front of further objects This fails that primary premise. my 2 cents -Buzz [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
