gEDA-bug: [Bug 708388] Re: Select all and deselect actions are too slow

[Peter Clifton <pcjc2@xxxxxxxxx>]

Being a pain, I'd like to see some profiling to further identify the
cause.

A lot of the work I'm hoping to do relies on invalidating objects "just
working", and redraw being fast without any trickery. By invalidating a
big rectangle first of all, I assume GTK will then not add separate
small rectangles when they lie within the already invalidated region.
Our expose event will be called with the big rectangle and we draw once.

In the current case - where oes the time go? Is it spent in GTK adding
the regions to its data-structures? Or is it that GTK hands us an expose
event with lots of small rectangles - and we then spend ages drawing?

Could it be that we're hitting performance issues in cairo when
rendering with a complex clip region?

If the rendering is to blame, we could choose to redraw the entire rect
bounding the damaged regions - without having to fake anything by
explicitly damaging the whole region first.

-- 
You received this bug notification because you are a member of gEDA Bug
Team, which is subscribed to gEDA.
https://bugs.launchpad.net/bugs/708388

Title:
  Select all and deselect actions are too slow

Status in GPL Electronic Design Automation tools:
  In Progress

Bug description:
  Select/deselect actions in gschem take up to 1 second on a moderately
  large schematic (900 lines in saved file).

  This is an annoyance and can hamper usability - the user can start
  repeating keystrokes or mouse clicks due to lack of feedback.




_______________________________________________
geda-bug mailing list
geda-bug@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-bug