Thanks Russ and Dennis for your replies If I'm not able to find a solution to the scrolling problem on Windows soon, I'll test it on a PowerPC Tiger Mac to see if the project is unaffected by the RB5.5.5 to RB2006R4 move.
Russ mentioned:
I suspect you have developed a scrolling logic based on the object's parent association with the canvas. Maybe some of your objects are not moving because their parent is not the canvas?
The canvas I use in scrolling is called "Canvas1". It contains a control array canvas named DrawEq1 that is on Canvas1. It's super class is the DrawEq canvas that is in the project window (so its super class isn't on Canvas1). I set up a third basic test project two hours ago to mimic the same structure to see if scrolling works and it still does so I'm yet to find an RB bug. Something may have changed in RB that is interacting with the ability to scroll the control array canvases, perhaps relating to drawing to those canvases. When I comment out the scrolling code, I observe the exact same effect in that no scrolling occurs and each new control array canvas is positioned in the same top-left hand corner as the older control array canvases. I have set break points at the point of scrolling, to make sure that the line is executed but no visible effect occurs. Returning to my second last paragraph, I think I'll try to move all properties of the super class DrawEq to the control array canvas DrawEq1 to see if this makes any difference. Paul On 11/20/06, Russ Van Bert <[EMAIL PROTECTED]> wrote:
Hi Paul, When I upgraded a project from RB 3.5 to 2006r2, I noticed that some of my objects would scroll twice as far as the others. This was caused by the objects getting associated to an object that had already been moved by me. That "Parent" property RB added in 4.0 or 2005? I fixed it by checking the parent of the object I was moving before I tried to move it. I suspect you have developed a scrolling logic based on the object's parent association with the canvas. Maybe some of your objects are not moving because their parent is not the canvas? ' for i = 0 to nNumberControls ' obj = Control(i) ' if ((obj isa StaticText) and (StaticText(obj).Parent isa Canvas)) then I have no idea how to correctly associate the parent dynamically other than ensuring the bounds of the new control definitely are within the bounds of the canvas when you create it. Does that help? Regards, Russ
_______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
