Hi Bruce, I was offline for a few days.
My request maybe too esoteric, but you understood well. I don't see a separate mapping function helping me much. Since I'm using ratios, it is pretty easy. x: using screen rectangle (l1,t1,r1,b1) xNew2: using screen rectangle (l2,t3,r2,b2) xNew2= x*((r2-l2)*10 +5)/(r1-l1)/10 +offset The above avoids floating calcs. The offset allow windows to overlap each other and the screen. I never thought about allowing the user to enter the ending rectangle, maybe a benefit to placing windows inside other windows or maybe a benefit to dual monitor systems; however, my script is already very ugly, allowing too many options. > In looking at this, it seems that the rect and points work > better if I use the convention: left top right bottom Okay with me, but I've gotten use to that this function is ordered differently than the others. Easy for me either way. Thanks anyway for giving it some thought. Ted --- In [email protected], "brucexs" wrote: > > > ... > > Win.Pos1000(han, x, y, w, h). > > ... > > > I think it is better to separate out the mapping of points from > the changing of window size or position. > > ... > and similarly for ynew. Better to do this in float. I can > implement in win plug as > ... Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
