I guess I should say: we don't do anything with rotation right now. It's not clear to me that if we did, that width/height would not be affected by rotation (they are surely _not_ affected by translation). That is, if you had two views that were rotated with respect to each other, it seems to me the contract of getAttributeRelative for width, say, is to ask what distance on my y- axis is the same as the distance target.width on the y-axis of the target view.
On 2006-10-10, at 12:17 EDT, P T Withington wrote: > Yes. > > On 2006-10-10, at 11:51 EDT, Jim Grandy wrote: > >> A side question: does getAttributeRelative understand the >> difference between x,y and width,height, where the first two are >> affected by scaling, rotation & translation but the second two are >> only affected by scaling? >> >> jim >> >> On Oct 10, 2006, at 7:09 AM, Max Carlson wrote: >> >>> What Tucker said is correct. And yes, in DHTML we could scale inner >>> view resources but not text. There's a warning for now. Thanks >>> Phil! >>> >>> -Max >>> >>> P T Withington wrote: >>>> We want what you implemented. These are the LZX semantics and the >>>> correct answer. It is a bug in the DHTML implementation that inner >>>> views are not scaled. You will get a warning to that effect in the >>>> current implementation. [It is my contention that we could use the >>>> portable linkage implementation to correctly scale inner views.] >>>> >>>> On 2006-10-10, at 09:16 EDT, Philip Romanik wrote: >>>> >>>>> Hi Max, >>>>> >>>>> The change I made moves getAttributeRelative() from LzSprite to >>>>> LzView >>>>> because there is no width/height support in the dhtml version. >>>>> Example >>>>> apps such as calendar call getAttributeRelative() with >>>>> x,y,width,height. It sounds like there are two choices when >>>>> someone >>>>> asks for width/height from dhtml: >>>>> >>>>> - Return the view's width/height. >>>>> - Return the same (scaled) width/height for dhtml and swf. >>>>> >>>>> My change is doing the latter. Is the first choice more >>>>> consistent? >>>>> >>>>> Thanks! >>>>> >>>>> Phil >>>>> >>>>> >>>>> >>>>>>> 2) As with .as, I don't think there needs to be any sprite >>>>>>> getAttributeRelative. The portable code already maintains >>>>>>> accurate >>>>>> view >>>>>>> dimensions. [Max: please verify.] >>>>>> >>>>>> Right, except getAttributeRelative() works with height and >>>>>> width in .as, >>>>>> but not .js. This shouldn't be a problem, since width and >>>>>> height can't >>>>>> be transformed/scaled for subviews in .js. The API needs to be >>>>>> consistent and should return something sensible for width/height >>>>>> though... >>>>> >>>> >>> >>> _______________________________________________ >>> Laszlo-dev mailing list >>> [email protected] >>> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev >> > > > _______________________________________________ > Laszlo-dev mailing list > [email protected] > http://www.openlaszlo.org/mailman/listinfo/laszlo-dev _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
