[Bug 205043] Review Request: geda-gattrib - Attribute editor for gEDA

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: geda-gattrib - Attribute editor for gEDA


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=205043


sdb at cloud9.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |sdb at cloud9.net




------- Additional Comments From sdb at cloud9.net  2006-09-05 09:49 EST -------
I am the author of this program.

  Well...

  [tasaka1 at dhcp151 geda-gattrib]$ gattrib
  /usr/share/gEDA/examples/RF_Amp/RF_Amp/MSA-2643.sch
  gEDA/gattrib version 20060824
  gEDA/gattrib comes with ABSOLUTELY NO WARRANTY; see COPYING for more details.
  This is free software, and you are welcome to redistribute it under certain
  conditions; please see the COPYING file for more details.
  Loading file [/usr/share/gEDA/examples/RF_Amp]
  Couldn't load schematic [/usr/share/gEDA/examples/RF_Amp]
  No components found in entire design!
  Do you have refdeses on your components?  
  Exiting. . . .

  What does this mean?

This is the correct behavior.  You tried loading a non-existant file.  The 
path "/usr/share/gEDA/examples/RF_Amp/RF_Amp/MSA-2643.sch" probably doesn't 
exist.  You probably want "/usr/share/gEDA/examples/RF_Amp/MSA-2643.sch" 
(remove one RF_Amp from diretory list).  

In general, gattrib will try to open your .sch file and look for valid 
components.  If it can't find then, it will bail out with the above error 
message.

I agree that the error message might be improved to say "file not found" in 
this case.  I can add that to the list of improvements I intend to do.

Stuart Brorson


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.