Hey Joshua a few recent updates should have taken care of this problem - please let us know if the latest trunk version from the svn fixes it for you!
cheers Rob On Sat, Aug 14, 2010 at 8:18 AM, Joshua Granick <[email protected]>wrote: > Alright, a little more clarification: > > > - I am using two views, layered on top of each other. They both use the > same camera, but using separate view objects lets me render them > individually, which is useful for performance > - The top view has objects which are dragged in 2D. The bottom view has a > flat plane for the floor > - When the floor plane does not have pushfront or ownCanvas set to true, > it catches clicks correctly > - When the floor plane has pushfront and ownCanvas set to true, it doesn't > receive any clicks > - When the floor plane has pushfront false, but ownCanvas is true, it > misses clicks that are near an object in the view above (within the object's > bounding box, I suppose?) > - When the floor plane has pushfront true, but ownCanvas is false, it > catches clicks correctly > > > Having ownCanvas false, but pushfront true, or having both false was > resulting in incorrect rendering, but having them true has been causing > mouse down problems, when it used to work. I think I've found a way around > the rendering issues for now, so I may be okay without ownCanvas, but I > still thought this was worth mentioning > > > > > On Thu, 12 Aug 2010 17:14:54 -0700, Joshua Granick < > [email protected]> wrote: > > A couple more notes about this: >> >> It seems that when ownCanvas is true, mouse clicks will fail ... >> sometimes. Sometimes it won't receive any clicks, and you can move the mouse >> slowly and it will still fail. Then if you shake the mouse a bit more, >> clicking the same spot will work. The scene does not render automatically, >> and does not move with the mouse, so it's the same literal render. >> >> One other thing that may be useful ... the Plane is contained inside an >> ObjectContainer3D >> >> >> On Thu, 12 Aug 2010 16:57:56 -0700, Joshua Granick < >> [email protected]> wrote: >> >> Hey guys, >>> >>> I think I found another regression since Away3D 3.4. >>> >>> I have a simple Plane, that I'm listening to with >>> MouseEvent3D.MOUSE_DOWN. It worked in Away3D 3.4, but I recently realized >>> (since updating this project to Away3D 3.5) that the MOUSE_DOWN event isn't >>> firing any more. I investigated a bit, and discovered that if the plan is >>> set to pushfront or to ownCanvas, it works as expected, but if both these >>> properties are set it no longer fires the MOUSE_DOWN event. This is >>> disappointing, because it is only when both of these properties are true >>> that it appears in front of the grid plane that is behind it. >>> >>> I'll post again if I find a workaround, but until then I thought I'd try >>> and bring some attention to this. Maybe someone has ideas? >>> >>> Thanks! >>> >> > > -- > Joshua Granick > Owner / Lead Developer > [ eclecticdesignstudio ] > P: (916) 889-7306 > -- Rob Bateman Flash Development & Consultancy [email protected] www.infiniteturtles.co.uk www.away3d.com
