[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

gEDA-bug: [Bug 698578] Re: error messages in status window should be more explicit



Hi KaiMartin,

I've just committed some changes to unstable which:

- Modify all libgeda-using apps other than gschem to print errors on stderr and exit with non-zero status if they encounter errors while loading initial configuration files.
- Modify gschem to show error dialogs for any errors loading initial configuration files.

Please test them, and give me feedback.  Note that there will still not
be exit errors/error dialogs for per directory configuration file errors
found while loading schematics, as those unfortunately use a rather
different codepath which is going to be quite difficult to refactor in a
"nice" way.

I'm going to move onto other issues for now; this bug should be
revisited sometime in the future, at which time local configuration
should be factored out of f_open_flags() and applications updated as
necessary. Lowering importance to medium, since most serious aspects of
bug have been fixed.

** Changed in: geda
   Importance: High => Medium

** Changed in: geda
       Status: In Progress => Triaged

** Changed in: geda
     Assignee: Peter TB Brett (peter-b) => (unassigned)

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

Title:
  error messages in status window should be more explicit

Status in GPL Electronic Design Automation tools:
  Triaged

Bug description:
  If gschem encounters a line in a config file it does not understand,
  the message sent to the status window lacks the keywords "error" or
  "warning". Subsequently, gschem quits parsing the resource file at the
  offending line and resumes the start-up procedure. This may result in
  unexpected behavior.

  Suggestion: 
  The message might read: "gschem encountered a problem while reading <filename>, line <line number>. The rest of the file remains unread."
  This message should go to stdout, too. 

  ---<(kaimartin)>---




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