I just thought I would make one more comment. After experimenting with the
postscript-font-scale setting in system-gschemrc, I found a setting of 1.5
to result in near WYSIWIG between display and printer on my system. This
makes 8 or 10 point font symbol text very readable on an A size printou
Mike,
Thanks for the info. I didn't know about the adjustment you mentioned; it
seems to work as you describe. While playing with the adjustment I've
learned a bit more about my situation. All of the symbols I had created
with the old gEDA used a font size of 8. Symbols created with the ne
Hi,
Besides the font anchor point, there's also a fudge-factor adjustment you
can apply in the system-gschemrc. This sets a scaling factor between gschem's
internal units and the font size. This is needed because not all fonts are
created equal. If this does not do the trick for you, can yo
Ben,
Thanks for the response. I may have more than one issue because I haven't
addressed the anchor point issue at all. However, when I compare schematics
printed out before and after the upgrade the text size (not just position)
is significantly smaller for the post upgrade schematic page.
On Mon, Jun 04, 2007 at 09:50:24AM -0600, Ed & Angie S. wrote:
> the text size
> for schematic symbols when printed is much smaller than before the
> upgrade. The problem is very evident for symbols which use a line above
> part of the signal name text to indicate negated because the line is no
>
I recently upgraded gEDA to the 02212007 CD release. I hadn't printed anything
right after the upgrade but noticed today that the text size for schematic
symbols when printed is much smaller than before the upgrade. The problem is
very evident for symbols which use a line above part of the sig
[snip]
>It probably is (I can't get gschem to crash...). But I'm wondering
>why there are toplevels with wid = -1. If I see it on the screen, then
>surely it must have all the associated gtk widgets realized and
>attached... right?
When toplevel's wid is -1 it means that it is a head nod
On Sun, Jun 03, 2007 at 08:58:48PM -0700, Ben Jackson wrote:
> On Sun, Jun 03, 2007 at 11:14:53PM -0400, Ales Hvezda wrote:
> >
> > Please file bugs and or patches so this issue doesn't get lots.
>
> Ok.
>
> I guess it says something that in order to find (well, run into and then
> find) thi
On Sun, Jun 03, 2007 at 10:46:19PM +0100, Peter Clifton wrote:
> On Sun, 2007-06-03 at 13:02 -0700, Ben Jackson wrote:
> > recent_files_add starts at global_window_current and walks back through
> > 'prev' as far as it can. In my crash, global_window_current looks fine,
> > its 'prev' looks fine (
9 matches
Mail list logo
