gEDA-bug: [Bug 845380] Re: text-find in gschem has unpredictable results if invisible text is found

["gpleda.org commit robot" <845380@xxxxxxxxxxxxxxxxxx>]

A commit was made which affects this bug
git master commit bd7a0be7431df1a2a03027edb96cfde558256cb1
http://git.gpleda.org/?p=gaf.git;a=commit;h=bd7a0be7431df1a2a03027edb96cfde558256cb1

commit bd7a0be7431df1a2a03027edb96cfde558256cb1
Author: Dima Kogan <dima@xxxxxxxxxxxxxxx>
Commit: Peter TB Brett <peter@xxxxxxxxxxxxx>

    gschem: Update optional debug printing to work with the latest code
    
    Signed-off-by: Dima Kogan <dima@xxxxxxxxxxxxxxx>
    Reviewed-by: Peter TB Brett <peter@xxxxxxxxxxxxx>
    Affects-bug: lp-845380

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

Title:
  text-find in gschem has unpredictable results if invisible text is
  found

Status in GPL Electronic Design Automation tools:
  Fix Committed

Bug description:
  When doing "Find specific text" in gschem, if a hidden text string
  matches, gschem produces unpredictable behavior. This is because it
  acts on uninitialized data (world_get_single_object_bounds() does
  nothing since the text is hidden, but its output is used anyway).
  Patches attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geda/+bug/845380/+subscriptions


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