Re: gEDA-user: Message
Östen Einarsson wrote: > I am very impressed of the gEDA-suit, it contains a lot of advanced > parts and at the same time makes great demands upon the user. It indeed does. Developers are aware of the issues and are working on it. Progress is painfully slow, though. > Then I added this symbol to my scheme but it was impossible to move > the refdes name only because there were no attributes left in the > symbol file. If you post the *.sym file, we may spot the cause more easily. Attach it to the mail, or just copy-paste the contents of the file. > I also got an extra frame around the symbol that was impossible to > remove from the scheme. gschem started from scratch presents a frame that is is deliberately locked. That way, it does not get elected by accident. This is meant a convenience feature. To delete the frame via the GUI you first have to select it. A simple left-click will not work, of course. But you can still select it by dragging a over it and choose unlock from the edit menu. The tutorial mentions how to deal with the title block: http://geda.seul.org/wiki/geda:gsch2pcb_tutorial#create_schematicone.sch Also see the wiki on these topics: http://geda.seul.org/wiki/geda:faq-gschem#how_do_i_unlock_a_locked_component http://geda.seul.org/wiki/geda:faq-gschem#how_can_i_shrink_symbols ---<)kaimartin(>--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message
On 09/22/2010 07:03 AM, Östen Einarsson wrote:
I also got
an extra frame around the symbol that was impossible to remove from the scheme.
For example how to edit file to let title block be deleted:
v 20080110 1
C 39400 51300 1 0 0 title-B-cibolo.sym
{
T 60300 52400 5 10 1 1 0 0 1
file=probe-lp.sch
T 64400 52100 5 10 1 1 0 0 1
drawn-by=John Griessen
T 52300 52100 5 18 1 1 0 0 1
title=probe-lp layout zone
T 60500 52100 5 10 1 1 0 0 1
first-pagenum=1
T 61200 52100 5 10 1 1 0 0 1
last-pagenum=1
T 64600 52400 5 10 1 1 0 0 1
rev=20Jan 2008
T 66200 57500 5 18 1 1 270 0 1
title2=probe-lp layout zone
}
change from:
C 39400 51300 0 0 0 title-B-cibolo.sym
to:
C 39400 51300 1 0 0 title-B-cibolo.sym
then open with gschem.
John
--
Ecosensory Austin TX
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message
On 09/22/2010 08:20 AM, Armin Faltl wrote: Hi Östen, to create a symbol you might start with an empty *.sym file instead of with an empty sheet, that by default will contain a frame. Like all entities, the reference to the frame in the .sym file has a flags section, containing the flag "unselectable" which is set in the case of the fram. By setting the flags to 0x00 or "" on the frame it gets selectable and can be deleted. By this he means edit the file pgnd-1.sym in a text editor, change the frame line or just delete it and save again. John -- Ecosensory Austin TX ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message
Hi Östen, to create a symbol you might start with an empty *.sym file instead of with an empty sheet, that by default will contain a frame. Like all entities, the reference to the frame in the .sym file has a flags section, containing the flag "unselectable" which is set in the case of the fram. By setting the flags to 0x00 or "" on the frame it gets selectable and can be deleted. Selection I think also works, if you select everything with a mouse-rectangle and then unselect the parts you want to keep before deletion. Regards, Armin Östen Einarsson wrote: Message to gEDA-forum ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Message
Message to gEDA-forum Hello boys. Excuse me for my scool-english, but I do my very best. I am very impressed of the gEDA-suit, it contains a lot of advanced parts and at the same time makes great demands upon the user. Now I try to create my own symbol a PGND symbol. I have 3 attributes in the symbol: pinnumber, pinseq and pintype. I have done "Symbol Translate" and saved the symbol in a directory as pgnd-1.sym. Then I added this symbol to my scheme but it was impossible to move the refdes name only because there were no attributes left in the symbol file. I also got an extra frame around the symbol that was impossible to remove from the scheme. Understand that I have done some wrong and hope someone can give a hint about it. Many thanks to all contributors for the work that is done on this powerful program suit. ostene Fedora-12 Gschem 1.6.0.20091004 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Mon, 22 Feb 2010 23:42:32 +, Peter Clifton wrote: > gschem's log window can be persuaded not to appear with this rhune in a > gschemrc. (I have it in ~/.gEDA/gschemrc) > > (log-window "later") I added this to the gschem-FAQ ---<(kaimartin)>--- -- Kai-Martin Knaak Öffentlicher PGP-Schlüssel: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6C0B9F53 ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Wed, Feb 24, 2010 at 12:15 PM, Frank Bergmann wrote: > On Tue, 23 Feb 2010 22:32:20 -0800, Jared Casper wrote: >> The functionality I saw someplace (was it in your repo?) to attach/embed >> the log window to the main window will help out with this problem as >> well I think. > > Maybe it was in this thread: > > http://thread.gmane.org/gmane.comp.cad.geda.user/27394 > > You find the patch(es) in the sf tracker: > > http://sourceforge.net/tracker/?func=detail&aid=2779826&group_id=73743&atid=538813 > Yup, that's what I was thinking of. I think it'd be cool to see this or something like it worked into the mainline. Jared ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Tue, 23 Feb 2010 22:32:20 -0800, Jared Casper wrote: > Maybe add a Warn function along side Message (or something along those > lines), and add a flag to HID.log that says whether or not to bring the > log window to the foreground? Or go all out and add an enum for > severity. It'd be easy to add the plumbing, the hard part would be to > go through and decide what Message()s should be Warn()s, etc. > > I'm sure different severities could be displayed differently in the log > quite easily as well... > > The functionality I saw someplace (was it in your repo?) to attach/embed > the log window to the main window will help out with this problem as > well I think. Maybe it was in this thread: http://thread.gmane.org/gmane.comp.cad.geda.user/27394 You find the patch(es) in the sf tracker: http://sourceforge.net/tracker/?func=detail&aid=2779826&group_id=73743&atid=538813 The second patch displays a little icon in the status bar when the log is not visible to inform the user about new messages. But the patches still lack of some functionality e.g. remembering the last status of the log- gui when the user leaves the application. Later in the thread mentioned above Peter C. suggest gdl (gnome docking library) for such a change. So I spend the last weeks (unfortunately I was very busy with my b-o-t-job) fighting against a bug in the ubuntu libgdl package. Now some things are clearer and I'am planing to rework my patch with libgdl. And the opportunity for different severities (different colors or little icons, filters, ...) are also in my mind. Frank Bergmann. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Tue, 23 Feb 2010 23:53:13 +, Peter Clifton wrote: > I can't help but feel that some log messages are important enough to > bother the user about I suggest, that gschem (and pcb for that matter) stick to the way most unix applications handle this issue: Truely important messages should be presented as pop-up dialogs. All the rest should be emitted on stdout. If there needs to be a log, this log should be written to a file. ---<(kaimartin)>--- -- Kai-Martin Knaak tel: +49-511-762-2895 Universität Hannover, Inst. für Quantenoptik fax: +49-511-762-2211 Welfengarten 1, 30167 Hannover http://www.iqo.uni-hannover.de GPG key:http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Wed, 24 Feb 2010 11:48:14 + Peter TB Brett wrote: > Why not have a bar (in a "warning" colour) that pops up at the top of the > layout window, and disappears after a short interval (say, 2 seconds). > Clicking the bar would bring up the message window. I like this idea, but with one caveat: If the warning/error level that spawned the bar is high enough (i.e. fatal errors such as shorted nets), leave the bar visible until it is clicked, rather than fading it out. -- "There are some things in life worth obsessing over. Most things aren't, and when you learn that, life improves." http://starbase.globalpc.net/~ezekowitz Vanessa Ezekowitz ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
Hi all, > -Original Message- > From: geda-user-boun...@moria.seul.org > [mailto:geda-user-boun...@moria.seul.org] On Behalf Of Peter Clifton > Sent: Wednesday, February 24, 2010 11:30 AM > To: gEDA user mailing list > Subject: Re: gEDA-user: Message and Library windows > > On Tue, 2010-02-23 at 22:32 -0800, Jared Casper wrote: > > On Tue, Feb 23, 2010 at 3:53 PM, Peter Clifton > wrote: > > > I can't help but feel that some log messages are > important enough to > > > bother the user about - and others are not.. we'll have > to see what > > > people actually using it think, I'm not doing any PCB > design work at > > > the moment myself. > > > > > > > Maybe add a Warn function along side Message (or something > along those > > lines), and add a flag to HID.log that says whether or not to bring > > the log window to the foreground? Or go all out and add an > enum for > > severity. It'd be easy to add the plumbing, the hard part > would be to > > go through and decide what Message()s should be Warn()s, etc. > > > > I'm sure different severities could be displayed differently in the > > log quite easily as well... > > Sounds good. gschem has different message warning levels, but > in practice you rarely see them. (Especially as it looses > that info if the message window isn't on-screen when the > message is logged!) > > > The functionality I saw someplace (was it in your repo?) to > > attach/embed the log window to the main window will help > out with this > > problem as well I think. > > Not mine.. I recall the one you're talking about, but I can't > remember the location of it. > Maybe it was the geany app used for coding stuff by some (including me). http://www.geany.org/Documentation/Screenshots Kind regards, Bert Timmerman. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Wed, 2010-02-24 at 11:48 +, Peter TB Brett wrote: > On Wed, 24 Feb 2010 10:30:20 +, Peter Clifton wrote: > > On Tue, 2010-02-23 at 22:32 -0800, Jared Casper wrote: > >> On Tue, Feb 23, 2010 at 3:53 PM, Peter Clifton wrote: > >> > I can't help but feel that some log messages are important enough to > >> > bother the user about - and others are not.. we'll have to see what > >> > people actually using it think, I'm not doing any PCB design work at > >> > the > >> > moment myself. > >> > > >> > >> Maybe add a Warn function along side Message (or something along those > >> lines), and add a flag to HID.log that says whether or not to bring > >> the log window to the foreground? Or go all out and add an enum for > >> severity. It'd be easy to add the plumbing, the hard part would be to > >> go through and decide what Message()s should be Warn()s, etc. > > Why not have a bar (in a "warning" colour) that pops up at the top of the > layout window, and disappears after a short interval (say, 2 seconds). > Clicking the bar would bring up the message window. This is what my phone > (N900, runs Linux) uses for displaying transient warning/notification > messages, and it works really nicely. > > Peter Neat idea.. and also seems to be a growingly common idiom in other apps due to the recognition that focus-stealing and popping up dialogs when the user isn't expecting them is poor interaction design, resulting in bad usability if it happens often. -- 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-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Wed, 24 Feb 2010 10:30:20 +, Peter Clifton wrote: > On Tue, 2010-02-23 at 22:32 -0800, Jared Casper wrote: >> On Tue, Feb 23, 2010 at 3:53 PM, Peter Clifton wrote: >> > I can't help but feel that some log messages are important enough to >> > bother the user about - and others are not.. we'll have to see what >> > people actually using it think, I'm not doing any PCB design work at >> > the >> > moment myself. >> > >> >> Maybe add a Warn function along side Message (or something along those >> lines), and add a flag to HID.log that says whether or not to bring >> the log window to the foreground? Or go all out and add an enum for >> severity. It'd be easy to add the plumbing, the hard part would be to >> go through and decide what Message()s should be Warn()s, etc. Why not have a bar (in a "warning" colour) that pops up at the top of the layout window, and disappears after a short interval (say, 2 seconds). Clicking the bar would bring up the message window. This is what my phone (N900, runs Linux) uses for displaying transient warning/notification messages, and it works really nicely. Peter >> I'm sure different severities could be displayed differently in the >> log quite easily as well... > > Sounds good. gschem has different message warning levels, but in > practice you rarely see them. (Especially as it looses that info if the > message window isn't on-screen when the message is logged!) > >> The functionality I saw someplace (was it in your repo?) to >> attach/embed the log window to the main window will help out with this >> problem as well I think. > > Not mine.. I recall the one you're talking about, but I can't remember > the location of it. -- Peter Brett Remote Sensing Research Group Surrey Space Centre ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Tue, 2010-02-23 at 22:32 -0800, Jared Casper wrote: > On Tue, Feb 23, 2010 at 3:53 PM, Peter Clifton wrote: > > I can't help but feel that some log messages are important enough to > > bother the user about - and others are not.. we'll have to see what > > people actually using it think, I'm not doing any PCB design work at the > > moment myself. > > > > Maybe add a Warn function along side Message (or something along those > lines), and add a flag to HID.log that says whether or not to bring > the log window to the foreground? Or go all out and add an enum for > severity. It'd be easy to add the plumbing, the hard part would be to > go through and decide what Message()s should be Warn()s, etc. > > I'm sure different severities could be displayed differently in the > log quite easily as well... Sounds good. gschem has different message warning levels, but in practice you rarely see them. (Especially as it looses that info if the message window isn't on-screen when the message is logged!) > The functionality I saw someplace (was it in your repo?) to > attach/embed the log window to the main window will help out with this > problem as well I think. Not mine.. I recall the one you're talking about, but I can't remember the location of it. -- 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-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Tue, Feb 23, 2010 at 3:53 PM, Peter Clifton wrote: > I can't help but feel that some log messages are important enough to > bother the user about - and others are not.. we'll have to see what > people actually using it think, I'm not doing any PCB design work at the > moment myself. > Maybe add a Warn function along side Message (or something along those lines), and add a flag to HID.log that says whether or not to bring the log window to the foreground? Or go all out and add an enum for severity. It'd be easy to add the plumbing, the hard part would be to go through and decide what Message()s should be Warn()s, etc. I'm sure different severities could be displayed differently in the log quite easily as well... The functionality I saw someplace (was it in your repo?) to attach/embed the log window to the main window will help out with this problem as well I think. Jared ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Mon, 2010-02-22 at 20:02 -0800, Jared Casper wrote: > On Mon, Feb 22, 2010 at 3:42 PM, Peter Clifton wrote: > > I'm tempted to pay someone a bounty to kill those with fire ;) > > > > (or certainly fix the message window's focus-stealing, attention > > grabbing - behaviour. The same is true of the netlist window when you > > press "F" on a net.) > > > > Patch attached. Here's the commit message (comments welcome): Committed (removing a few minor trailing white-space issues). Thank you for the patch! We'll see how everyone (using git HEAD) finds the new behaviours, and see if we need to adjust it at all. I can't help but feel that some log messages are important enough to bother the user about - and others are not.. we'll have to see what people actually using it think, I'm not doing any PCB design work at the moment myself. Best wishes, -- 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-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Mon, 22 Feb 2010 20:02:43 -0800 Jared Casper wrote: > On Mon, Feb 22, 2010 at 3:42 PM, Peter Clifton wrote: > > I'm tempted to pay someone a bounty to kill those with fire ;) > > > > (or certainly fix the message window's focus-stealing, attention > > grabbing - behaviour. The same is true of the netlist window when you > > press "F" on a net.) > > > > Patch attached. Here's the commit message (comments welcome): /me falls over *wibble* Thanks for the patch. It's a nice change from the old behavior. ;-) -- "There are some things in life worth obsessing over. Most things aren't, and when you learn that, life improves." http://starbase.globalpc.net/~ezekowitz Vanessa Ezekowitz ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Mon, Feb 22, 2010 at 3:42 PM, Peter Clifton wrote:
> I'm tempted to pay someone a bounty to kill those with fire ;)
>
> (or certainly fix the message window's focus-stealing, attention
> grabbing - behaviour. The same is true of the netlist window when you
> press "F" on a net.)
>
Patch attached. Here's the commit message (comments welcome):
Prevent extra windows from showing unnecessarily in GTK HID.
Prevent the library, log, and netlist windows in the GTK HID from
being shown unless explicitely requested. This is done by splitting
ghid_*_window_show into ghid_*_window_create, which creates all the
resources for the window, and ghid_*_window_show, which actually shows
the window (and optionally "presents" it, which pulls it to the
foreground and gives it focus).
Since the NetlistShow action no longer actually shows the netlist
window, but sets the node/net that is shown in the window (if and when
it is visible), this patch also adds NetlistPresent which presents the
netlist window. This can be added to the FindConnections menu item to
restore the behavior of bringing up the netlist window on a find.
Added an action LogShowOnAppend() which can restore the old behavior
that the log window is shown whenever something is appended to it
(currently off by default).
Jared
From d994c124332a25bbb248d4e7dc5ee166dc2ef769 Mon Sep 17 00:00:00 2001
From: Jared Casper
Date: Mon, 22 Feb 2010 19:24:17 -0800
Subject: [PATCH] Prevent extra windows from showing unnecessarily in GTK HID.
Prevent the library, log, and netlist windows in the GTK HID from
being shown unless explicitely requested. This is done by splitting
ghid_*_window_show into ghid_*_window_create, which creates all the
resources for the window, and ghid_*_window_show, which actually shows
the window (and optionally "presents" it, which pulls it to the
foreground and gives it focus).
Since the NetlistShow action no longer actually shows the netlist
window, but sets the node/net that is shown in the window (if and when
it is visible), this patch also adds NetlistPresent which presents the
netlist window. This can be added to the FindConnections menu item to
restore the behavior of bringing up the netlist window on a find.
Added an action LogShowOnAppend() which can restore the old behavior
that the log window is shown whenever something is appended to it
(currently off by default).
---
src/hid/gtk/gtkhid-main.c|4 ++-
src/hid/gtk/gui-library-window.c | 62 ---
src/hid/gtk/gui-log-window.c | 54 ++
src/hid/gtk/gui-netlist-window.c | 66 ++---
src/hid/gtk/gui.h|3 ++
5 files changed, 133 insertions(+), 56 deletions(-)
diff --git a/src/hid/gtk/gtkhid-main.c b/src/hid/gtk/gtkhid-main.c
index cd30221..81f0d77 100644
--- a/src/hid/gtk/gtkhid-main.c
+++ b/src/hid/gtk/gtkhid-main.c
@@ -1289,7 +1289,9 @@ LayerGroupsChanged (int argc, char **argv, int x, int y)
static int
LibraryChanged (int argc, char **argv, int x, int y)
{
- ghid_library_window_show (&ghid_port, FALSE);
+ /* No need to show the library window every time it changes...
+ * ghid_library_window_show (&ghid_port, FALSE);
+ */
return 0;
}
diff --git a/src/hid/gtk/gui-library-window.c b/src/hid/gtk/gui-library-window.c
index 4396d13..8bd0d7b 100644
--- a/src/hid/gtk/gui-library-window.c
+++ b/src/hid/gtk/gui-library-window.c
@@ -139,46 +139,40 @@ library_window_callback_response (GtkDialog * dialog,
}
-/*! \brief Opens a library dialog.
+/*! \brief Creates a library dialog.
* \par Function Description
- * This function opens the library dialog for if it is not already.
- * In this last case, it only raises the dialog.
+ * This function create the library dialog if it is not already created.
+ * It does not show the dialog, use ghid_library_window_show for that.
*
*/
void
-ghid_library_window_show (GHidPort * out, gboolean raise)
+ghid_library_window_create (GHidPort * out)
{
GtkWidget *current_tab, *entry_filter;
GtkNotebook *notebook;
- if (library_window == NULL)
-{
- library_window = g_object_new (GHID_TYPE_LIBRARY_WINDOW, NULL);
+ if (library_window)
+return;
- g_signal_connect (library_window,
- "response",
- G_CALLBACK (library_window_callback_response), NULL);
- g_signal_connect (G_OBJECT (library_window), "configure_event",
- G_CALLBACK (library_window_configure_event_cb), NULL);
- gtk_window_set_default_size (GTK_WINDOW (library_window),
- ghidgui->library_window_width,
- ghidgui->library_window_height);
+ library_window = g_object_new (GHID_TYPE_LIBRARY_WINDOW, NULL);
- gtk_window_set_title (GTK_WINDOW (library_window), _("PCB Library"));
- gtk_window_set_wmclass (GTK_WINDOW (library_window), "PCB_Library",
- "PCB");
+ g_signal_connect (library_window,
+"response",
+G_CALLBACK (library_window_ca
Re: gEDA-user: Message and Library windows
(or certainly fix the message window's focus-stealing, attention grabbing - behaviour. The same is true of the netlist window when you press "F" on a net.) That one burns me often :D ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Message and Library windows
On Mon, 2010-02-22 at 17:03 -0600, Vanessa Ezekowitz wrote: > Is there a way to disable the Message Log and Library windows by > default, in PCB? I'm finding I keep these either hidden or closed a > lot more than I keep them open. I'm tempted to pay someone a bounty to kill those with fire ;) (or certainly fix the message window's focus-stealing, attention grabbing - behaviour. The same is true of the netlist window when you press "F" on a net.) I know it isn't what you asked, but if it is any small consolation, gschem's log window can be persuaded not to appear with this rhune in a gschemrc. (I have it in ~/.gEDA/gschemrc) (log-window "later") -- 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-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Message and Library windows
Is there a way to disable the Message Log and Library windows by default, in PCB? I'm finding I keep these either hidden or closed a lot more than I keep them open. -- "There are some things in life worth obsessing over. Most things aren't, and when you learn that, life improves." http://starbase.globalpc.net/~ezekowitz Vanessa Ezekowitz ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
