Re: gEDA-user: pcb+gl minor polygons glitch

2011-05-12 Thread Peter Clifton
On Wed, 2011-05-11 at 22:39 +0100, Thomas Oldbury wrote:
> On my ThinkPad X201, I am encountering a minor issue with PCB+GL... Not
>a show stopper, but a bit annoying. I notice that when I move the
>cursor, occasionally a random triangle extending from the middle of the
>board to the outer edge will be highlighted. I'm using Ubuntu 10.10 and
>the GPU is an Intel of some sort, not sure exactly which one. There
>seems to be no definite pattern... is this a confirmed bug with PCB+GL
>or just a glitch with my laptop/software combination?

It would be worth re-fetching again now, and checking if this still
occurs with the latest fixes I've applied. It is just possible that the
incorrect state I had set which resulted in missing crosshair attached
objects caused a problem.

Could you send me the contents of the output of the command:

glxinfo

and a copy of your /var/log/Xorg.0.log

This is to identify exactly what graphics card and driver you are using.

I have certainly heard (and seen) reports of a similar sounding artefact
from one other Intel GPU based machine. I don't see it here on mine, but
I'd love to get to the bottom of it.

Since I can get physical access to the other laptop this was reported
on, if you could send a video to confirm we're looking at the same kind
of bug, I might be able to do some tracing and debug work here - perhaps
enough to send the Intel driver developers a clueful bug report to get
their driver fixed (assuming it is a driver issue).

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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)


signature.asc
Description: This is a digitally signed message part


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: Adding inner polygons to a plane

2011-05-12 Thread Peter Clifton
On Thu, 2011-05-12 at 14:05 +0100, Robert Spanton wrote:
> On Wed, 2011-05-11 at 19:19 +0100, Peter Clifton wrote:
> > Perhaps it would be possible to support a flag on the "smaller",
> > clippiING polygon which makes it "bully" other polygons away from it,
> 
> EAGLE does this by allowing the user to assign a numeric priority to a
> polygon.  Polygons with higher priority get to "bully".
> 
> > but again - it is not clear what to do in the case where two polygons
> > with this flag touch each other. (Just short with each other I guess).
> 
> I suspect that shorting the polygons together would be the exact
> opposite of what the user wanted most of the time.

They would soon learn to stop drawing overlapping polygons though ;)

> Perhaps it should create a DRC violation, with neither of the polygons
> rendering until the user has fixed the problem (with some kind of visual
> indicator to show that this is happening!).  It seems to me that this
> would result in the behaviour of least surprise and fewer broken PCBs.

Shorting is not going to break anyone's PCB - its just one of many ways
we "could" operate, and would influence how the user draws their
geometry.

Perhaps a simple Z-Order (perhaps file location based) would suffice,
and we could add "bring to front" / "send to back" commands somewhere.

Top-most polygons clip and bully lower polygons etc..

I can't recall exactly why, but I recall being partly opposed to
Z-ordering within a single layer before. It might be because it would
tend to produce big diffs in the PCB file for Z-ordering changes.

Assigning numbers is another way to do it, but you do have to ensure
numbers aren't duplicated, and ideally - don't have gaps.. Hmm..

-- 
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!)
Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me)


signature.asc
Description: This is a digitally signed message part


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: autocrop.c vs. pcb (git head)

2011-05-12 Thread Kovacs Levente
On Thu, 12 May 2011 02:32:00 +0100
Peter Clifton  wrote:

> Edit autocrop.c and change "ClearAndRedrawOutput ();" to "Redraw ();"

Thanks.
 
> In general, you need to rebuild every plugin when you build a new
> version of PCB from git. plugins poke internal APIs and
> data-structures, which do change from time to time.

That is good to know.

Levente

-- 
Kovacs Levente 
Voice: +36705071002




___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: minipack-result -- gschem

2011-05-12 Thread Peter TB Brett
On Thursday 12 May 2011 17:06:01 Kai-Martin Knaak wrote:
> [snip]
>
> Now I get a decent gschem GUI :-)

Great!

> [snip]
>
> What would be the HOME in windows. Or alternatively, how would I give
> a full windows path that includes backslashes and the drive letter?

Just like that, I think (you may need to write "\" as "\\", but note that it 
is actually valid to use "/" characters in a Windows path). The build-path 
Scheme function is (intentionally) portable.

> By the way, should the lines of the config files be terminated unix style,
> or DOS style?

Doesn't make any difference either way.

Peter

-- 
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: minipack-result -- gschem

2011-05-12 Thread Kai-Martin Knaak
Duncan Drennan wrote:

> I have the following environment variables set in Windows Vista,
> 
> GEDABIN=D:\Program Files\gEDA\bin
> GEDADATA=D:\Program Files\gEDA\share\gEDA
> GUILE_LOAD_PATH=D:\Program Files\gEDA\share\guile\1.8
> 
Thanks!
Now I get a decent gschem GUI :-)
Next step: How do I configure gschem to find my local library?
On my linux box I have these lines in ~/.gEDA/gafrc :

--
; Allow to source symbols from the current working directory
(component-library ".")
; Allow to source symbols from the loacl repository
(define symbolspath (build-path (getenv "HOME") "geda" "symbols"))
(component-library (build-path symbolspath "titleblock"))
(component-library (build-path symbolspath "power"))
(component-library (build-path symbolspath "misc"))
...
---

What would be the HOME in windows. Or alternatively, how would I give 
a full windows path that includes backslashes and the drive letter? 

By the way, should the lines of the config files be terminated unix style, 
or DOS style?

---<)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: Adding inner polygons to a plane

2011-05-12 Thread Robert Spanton
On Wed, 2011-05-11 at 19:19 +0100, Peter Clifton wrote:
> Perhaps it would be possible to support a flag on the "smaller",
> clippiING polygon which makes it "bully" other polygons away from it,

EAGLE does this by allowing the user to assign a numeric priority to a
polygon.  Polygons with higher priority get to "bully".

> but again - it is not clear what to do in the case where two polygons
> with this flag touch each other. (Just short with each other I guess).

I suspect that shorting the polygons together would be the exact
opposite of what the user wanted most of the time.

Perhaps it should create a DRC violation, with neither of the polygons
rendering until the user has fixed the problem (with some kind of visual
indicator to show that this is happening!).  It seems to me that this
would result in the behaviour of least surprise and fewer broken PCBs.

Cheers,

Rob


signature.asc
Description: This is a digitally signed message part


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user


Re: gEDA-user: pcb: Track routing strategies and tips

2011-05-12 Thread gene glick


The schematic should be 
as readable as possible.


Clearly you do not work where I do :)

(or as some folks say "there you go, making sense again")

> Preferred signal direction is left to right,
top to bottom. 


Me too, whenever possible.


___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user