On Tue, 2008-09-30 at 17:28 -0400, DJ Delorie wrote:
> > Yep - thats how I tested it. I have the code to do that as a separate
> > patch in case I needed to do any more testing again later.
> 
> I would be amenable to checking that patch in also, with an #if 0
> around it, for the next time we need to debug that.

Now pushed to CVS (although the commit messages have gone AWOL thanks to
Sourceforge's general brokenness).

>From my git repository instead:

commit 2ef14a9182d881de4b336a8ba909477cb2dd9244
Author: Peter Clifton <[EMAIL PROTECTED]>
Date:   Tue Sep 30 23:49:10 2008 +0100

    Don't bother unsubtracting complex polygons when doing incremental updates
    
    Since the polygon is re-cleared against any objects existing within the
    bounding box of the update region, there is no point wasting CPU cycles
    intersecting a more complex polygon than necessary. Just take the UNION
    of the polygon being unsubtracted, and the bounding box of the hole to
    be filed in.

commit f454cda52b23b4184d9045b7ed0bf8a547b264ce
Author: Peter Clifton <[EMAIL PROTECTED]>
Date:   Tue Sep 30 23:49:09 2008 +0100

    Fix text bounds to include the area cleared into a polygon
    
    Fixes re-clearing the polygon when a closely touching object is
    incrementally updated.

commit 066e73da1408716d33d76127925b5dc6ff440e55
Author: Peter Clifton <[EMAIL PROTECTED]>
Date:   Tue Sep 30 23:49:08 2008 +0100

    Ensure "Gathering" mode is set after painting the screen.
    
    In between repaints initiated from the GUI, with this flag set, all
    Draw{object_type} operations just update a dirtied bounds. A final
    Draw() call then calls the HID to invalidate the bounds gathered.
    
    Setting "Gathering = True" after an expose event callback ensures
    subsequent drawing is batched up for the next screen update.

commit b55853e3af23a3eac82bb73a4ea89d11eb93d017
Author: Peter Clifton <[EMAIL PROTECTED]>
Date:   Tue Sep 30 23:49:07 2008 +0100

    Add debugging code to visually check a pad's bounding box
    
    Proved useful in fixing the pad bounding box update routine.
    Disabled with #if 0 block.

commit 903269956fdacd45b17e34a9193cc3cc7edf5091
Author: Peter Clifton <[EMAIL PROTECTED]>
Date:   Tue Sep 30 23:49:05 2008 +0100

    Fix bounding boxes for rotated square ended pads.
    
    Bounding box compution only worked for round ended pads before.
    In addition, the "move" code previously called SetLineBoundingBox
    for pads, which computes the wrong result.

commit 64cae26e9248e0eac4927d53a42f9577aa269e5d
Author: Peter Clifton <[EMAIL PROTECTED]>
Date:   Tue Sep 30 23:49:04 2008 +0100

    GTK HID: Make double clicking on a footprint library expand / contract it
    
    Usability improvement.


 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)



_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to