From: Leif W <war...@us...> - 2005-08-20 19:12:44
|
> From: <do...@cr...> > Sent: 2005 August 12 Friday 10:31 > > Okay.. instead of inserting the background layer the way you are now, > What I > do is have a div in my html at the location i want my layer, then > onload, i > use the Inline extension to pull out the position of the relative div > in the > document, and position my layer accordingly. I tried various combinations of addChild and insert to no avail. The outermost layer gets positioned incorrectly. I'll have to try the inline feature. But I'd really like to understand the problem. I don't think it's doing anything that shouldn't be possible with a fully dynamic layer. Maybe it's a usage thing. But as I'm still learning the API, I can't spot it off hand. > I can't help but wonder if adding the layer to the dynapi.document > (which > inserts it in the browser's DOM) then inserting it a second time with > your > inset call.. try using the FireFox dom inspector (i think it's > included, but > you may want to DL it from the FF extensions page) once you page is > loaded, > you can browse through the document's objects to see if your layer is > there twice. Using Firefox, I saw only one instance of the DIV. I'm wondering perhaps if adding the child and inserting it messes with the box model stuff. I seemed to get a few pixels difference (from 7-20), which might be some CSS border widths of DIV and IMG tags. > P.S. Sample code that exhibits the error would be great.. make it much > easier > to deterine the issue at hand :-) Well, yeah. But without any further input from the user, I can only guess by the erroneous behaviour I see in my test code based upon the user's initial incomplete example. Please note that I did create a bug entry for this so that I would not forget. [ 1257263 ] Events send wrong X/Y coords to relative layers. http://sourceforge.net/tracker/index.php?func=detail&aid=1257263&group_id=5757&atid=105757 |