Re: gEDA-user: cutout in plane
Yes, I've done that before too. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: cutout in plane
DJ Delorie wrote: How does the git head feature work? I haven't had a chance to play with it yet. It's ok to do it peace meal, isn't it? Make an island, whatever shape. The surround it with other rectangles, for example, until there's a desired gap. My power plane is going to be made up of a bunch of polygons, looking like a big ole quilt :D But I think it works. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: cutout in plane
> How does the git head feature work? I haven't had a chance to play with it yet. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: cutout in plane
hey, maybe I should look back at my emails :D I see a bunch of stuff there about this very thing - doh! ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: cutout in plane
DJ Delorie wrote: You can either get the git head PCB which has true hole support, or draw a "C" shaped polygon where the two arms touch to make a pseudo-hole. Hi DJ, Yep, that seems to work. How does the git head feature work? ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: cutout in plane
You can either get the git head PCB which has true hole support, or draw a "C" shaped polygon where the two arms touch to make a pseudo-hole. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: cutout in plane
Best method to put a hole in a plane? I tried the zero width line with clearance of 15 mil which sort of works, but leaves behind a small 0.1 mil line. It's visible on the gerber. Basically, I want a power plane (+3.3V) with a small power island in the middle (+1.2V). thanks gene ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git HEAD PCB now supports user-defined holes in polygons
Kai-Martin Knaak wrote: On Tue, 08 Jun 2010 10:51:10 -0400, Jim wrote: Oh, please make that change configurable without recompiling! It is already configurable without recompiling. This is how: 1) locate the file gpcb-menu.res on your box. 2) copy the file to $HOME/.pcb 3) edit to your needs, save 4) on start-up, pcb will read this localised copy. This will overwrite whatever settings were made by the system gpcb-menu.res ---<)kaimartin(>--- Thanks, that'll help a lot if they do change default behavior. Jim. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Garbage drawn outside of pcb board area
On Tue, Jun 08, 2010 at 09:14:12PM +0100, Peter Clifton wrote: > > You were right - it seems the driver is at fault... It wasn't always > > like that so I'll try to track down what change broke the rendering. > > It might not be the driver's fault if I'm doing evil things like making > GL calls out of valid context setup. (Which I was). You were right, I have to retract the statement about the driver's fault. I got the hint from this FAQ: http://www.opengl.org/resources/faq/technical/clipping.htm#0080 The attached patch fixes the issue for me. Best regards, -- Krzysztof Kościuszkiewicz "Simplicity is the ultimate sophistication" -- Leonardo da Vinci diff --git a/src/hid/gtk/gui-output-events.c b/src/hid/gtk/gui-output-events.c index 1fa2640..2bf934d 100644 --- a/src/hid/gtk/gui-output-events.c +++ b/src/hid/gtk/gui-output-events.c @@ -1802,7 +1802,9 @@ ghid_port_drawing_area_expose_event_cb (GtkWidget * widget, glStencilMask (~0); glClearStencil (0); + glDisable (GL_SCISSOR_TEST); glClear (GL_COLOR_BUFFER_BIT | GL_STENCIL_BUFFER_BIT); + glEnable (GL_SCISSOR_TEST); hidgl_reset_stencil_usage (); /* Disable the stencil test until we need it - otherwise it gets dirty */ ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git HEAD PCB now supports user-defined holes in polygons
On Wed, 09 Jun 2010 13:56:42 +0200, Armin Faltl wrote: > No popup please ack. A horizontal menu would be better -- No need to move the mouse to some place in the middle of the screen. > - have the sub-tools replace the coarser tool box and change back No wholesale replacement of tools on the UI, please. > with a click on the "BACK" button or right-click somewhere in the app. Someone just warned against burning right-click for not so important purposes. ;-) > (for laying traces or lines the first right-click breaks the (poly-)line > and so 2 right-clicks > are needed to change from "poly-line"-mode to "line-start"- to > "tool-select"-mode) pcb already supports this with the [esc] key. ---<)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: git HEAD PCB now supports user-defined holes in polygons
On Wed, 09 Jun 2010 13:35:55 +0200, Armin Faltl wrote: > kai-martin knaak wrote: >> Back in 1999 Microstation by Bentley did it this way: >> >> left click = do the default action >> >> right-click-drag = a horizontal menu with several icons representing >> different modes of the tool appears. The icon that is highlicghted on >> mouse button release is executed. >> >> right-click = the horizontal appears. Left-click on an icon makes this >> mode the default of the tool. >> > Right click is a very ergonomic action so I'd like to reserve it for > something IMO more important The right mouse button functionality I described, is exclusive to the mode buttons. It does not interfere in any way with right-mouse functions during routing, or on objects. > The use of the right mouse button to get back one level in handler > hierarchy is very convenient for me. It's a feature I learned to > love with QCad The concept of a hierarchy of tools is one of the aspects I explicitly dislike with qcad. It is a pain to constantly move up and down this hierarchy and keep the current position in the hierarchy in mind. The most important tools should be readily available, no matter what. ---<)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: Garbage drawn outside of pcb board area
On Tue, Jun 08, 2010 at 09:14:12PM +0100, Peter Clifton wrote: > > You were right - it seems the driver is at fault... It wasn't always > > like that so I'll try to track down what change broke the rendering. > > It might not be the driver's fault if I'm doing evil things like making > GL calls out of valid context setup. (Which I was). > > The patch I sent should (as far as I know) avoid the offending drawing > calls, but it does not 100% guarantee that nothing else calls a drawing > routine directly when it shouldn't. > > I assume from your response that the patch didn't get rid of the rubbish > on screen. I'm not sure what to suggest trying next. Perhaps I could > produce a patch which extends the locking to every drawing call, just in > case something slipping past. No, the patch did not fix the "rubbish issue", just the segfault. > We could look at whether it is possible to trim down various drawing > calls / methods, and see at what point the rubbish goes away. If this is present even for empty boards, then there aren't many things that get drawn (cursor, selection, background?) This could be a viable option. > Is it present for all boards, (including blank), or does it depend on > what you have on the board? It is present for all boards I've tested, including blank. It manifests itself only in the area not occupied by the board, or outside the drawing area. If I zoom in and the full window is occupied with the board, I can see no garbage. Best regards, -- Krzysztof Kościuszkiewicz "Simplicity is the ultimate sophistication" -- Leonardo da Vinci ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git HEAD PCB now supports user-defined holes in polygons
On Tue, 08 Jun 2010 10:51:10 -0400, Jim wrote: > Oh, please make that change configurable without recompiling! It is already configurable without recompiling. This is how: 1) locate the file gpcb-menu.res on your box. 2) copy the file to $HOME/.pcb 3) edit to your needs, save 4) on start-up, pcb will read this localised copy. This will overwrite whatever settings were made by the system gpcb-menu.res ---<)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: Changing traces from one layer to another
> On Tue, 2010-06-08 at 06:12 -0400, vinny wrote: > > I can move components but not trace, is there way to do that? > > Select the traces you want to move and the layer you wish to move them > to. Select 'Edit>Move selected to current layer' or press Shift-M. You > can also just press M when the cursor is over a trace. > > Richard Thank you very much that works perfectly. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git HEAD PCB now supports user-defined holes in polygons
Peter Clifton wrote: Perhaps a click on the polygon tool ought to expand with a pop-up with sub-variants of the tool to choose from? No popup please - have the sub-tools replace the coarser tool box and change back with a click on the "BACK" button or right-click somewhere in the app. (for laying traces or lines the first right-click breaks the (poly-)line and so 2 right-clicks are needed to change from "poly-line"-mode to "line-start"- to "tool-select"-mode) ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git HEAD PCB now supports user-defined holes in polygons
kai-martin knaak wrote: Back in 1999 Microstation by Bentley did it this way: left click = do the default action right-click-drag = a horizontal menu with several icons representing different modes of the tool appears. The icon that is highlicghted on mouse button release is executed. right-click = the horizontal appears. Left-click on an icon makes this mode the default of the tool. That way you can deal with a multitude of modes and get an intuitive way to configure the default to your own, special needs. OK, this is certainly too much for pcb in its current state. But it shows, what a powerful GUI can do. Right click is a very ergonomic action so I'd like to reserve it for something IMO more important: the ESC functionality in routing, i.e. break a trace and restart a new one. So for a tool-box popup I'd prefer shift-left-click or maybe shift-right click or one of the zilion of other mous buttons I have ;-) The use of the right mouse button to get back one level in handler hierarchy is very convenient for me. It's a feature I learned to love with QCad and implemented in my GUI-demo (with some known glitches) visible at www.varkon.org. I also prefer assignment of view operations to the middle mouse button/wheel as a clear concept: scroll = zoom, drag = pan. (in space it's a bit more complicated: scroll is move along camera axis, drag = move traverse, Ctrl-drag = rotate in space, alt-scroll = change perspective angle,...) Regards, Armin ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: git HEAD PCB now supports user-defined holes in polygons
On Mon, 07 Jun 2010 00:38:16 +0100 Peter Clifton wrote: > git HEAD PCB now supports user-defined holes in polygons Hi Peter, This feature is cool. Thank you for implementing it. I found that it makes a funny thing when you move a cutout corner outside the polygon. I wish we could define pads as polygons, so with this feature any kind of pads could be implemented. Solder-mask cut outs would be nice too. Thanks again, Levente -- Levente Kovacs http://levente.logonex.eu ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Next problem, PCB looses rats
Hm - doing that and throwing that knowledge away once the mouse hovers over
something else - I can't believe it's implemented like this.
And there must be at least 2 lists to be able to detect a shorting
of copper traces e.g. when moving a part. The rats optimizer needs the
information for all nets (btw. I think it has some flaws anyway - it doesn't
find the shortes connection in some cases, not even considering only the
endpoints of trace-segments)
Keeping one list of trace segments, polygons and pads per net would be
a natural solution. In that case the solution of copper islands is trivial:
keep them in a "not connected" list and allow to connect to such a segment.
If the segment changes net, treat it as new drawn to see what it touches...
The implementation must be present already to resolve the situation
after turning off/on the DRC. Just the handling of the contact needs to be
different: the "not connected" net would need to "virtually" belong to
the current net {if (netToTest == currentNet || netToTest == 0) ...}.
If the trace really gets connected, the portion with real contact has to
be split out.
If the traces belonging to nothing are not in a single list but disjoint
areas are in separate lists each, it's even simpler:
{if (netToTest == currentNet || netToTest < 0) ...} assuming there is an
internal net-number and net-listed nets have positiv, dangling nets have
negative numbers.
Thinking of practical routing, the question is, whether silently connecting
random copper fields to a random trace is really as desirable as it
looks when running into the off/on hassle while knowing what one does.
So making this potential feature configurable or requireing a shortcut-key
to be able to move onto dangling nets is probably due.
HTH, Armin
kai-martin knaak wrote:
Armin Faltl wrote:
If the copper traces have no idea of a net (or vice versa), how does the
positive test work, i.e. why is it possible to connect anything at all
despite there is a DRC?
A wild guess in the dark: The algorithm internally builds a list ob objects
connected to the currently drawn track. Everything else is to be avoided by
a margin.
---<)kaimartin(>---
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
