Re: [Kicad-developers] GAL cursor snap behavior

On Tue, Jul 26, 2016 at 10:49:21PM +0200, Tomasz Wlostowski wrote: > On 26.07.2016 22:35, Chris Pavlina wrote: > > ...maybe we should rethink the behavior of cursor-snapping in GAL a > > bit... > > > > https://misc.c4757p.com/gal_snap_insanity.mp4 > > > > At best it's very distracting, at worst

Re: [Kicad-developers] GAL cursor snap behavior

On 26.07.2016 22:35, Chris Pavlina wrote: > ...maybe we should rethink the behavior of cursor-snapping in GAL a > bit... > > https://misc.c4757p.com/gal_snap_insanity.mp4 > > At best it's very distracting, at worst it can make it nearly impossible > to select certain pads... > Hi Chris, I

[Kicad-developers] GAL cursor snap behavior

...maybe we should rethink the behavior of cursor-snapping in GAL a bit... https://misc.c4757p.com/gal_snap_insanity.mp4 At best it's very distracting, at worst it can make it nearly impossible to select certain pads... ___ Mailing list:

Re: [Kicad-developers] eeschema undo assertion

It doesn't happen when I undo something, it happens when I perform an action that can be undone. Typically happens the first time I interact with an object after starting eeschema. On Tue, Jul 26, 2016 at 10:47:26AM -0400, Wayne Stambaugh wrote: > The current undo item cannot be null so the

Re: [Kicad-developers] eeschema undo assertion

The current undo item cannot be null so the assertion is raised and then skips swapping the undo information between the two objects when the users chooses to continue. Is there a particular item where you undo edits that causes the assertion or does it seem to be any item? This would help me

Re: [Kicad-developers] eeschema undo assertion

Thanks. It's annoying (mostly as I tend to instinctively dismiss it with escape and that makes wx abort the whole application...) and I'm not really familiar enough with the undo code to know what the problem is. I don't _think_ anything is seriously broken, as it seems to work when I dismiss it

Re: [Kicad-developers] Geometry ongoing work

Le 26/07/2016 à 15:57, Wayne Stambaugh a écrit : > On 7/26/2016 9:29 AM, Nick Østergaard wrote: >> 2016-07-26 14:58 GMT+02:00 Wayne Stambaugh : >>> On 7/26/2016 7:20 AM, Nick Østergaard wrote: Welcome. I have found a pcb file on my computer, I am not sure of

Re: [Kicad-developers] Geometry ongoing work

On 7/26/2016 9:29 AM, Nick Østergaard wrote: > 2016-07-26 14:58 GMT+02:00 Wayne Stambaugh : >> On 7/26/2016 7:20 AM, Nick Østergaard wrote: >>> Welcome. >>> >>> I have found a pcb file on my computer, I am not sure of its origin, >>> that has a buggy rendering both in legacy

Re: [Kicad-developers] Geometry ongoing work

2016-07-26 14:58 GMT+02:00 Wayne Stambaugh : > On 7/26/2016 7:20 AM, Nick Østergaard wrote: >> Welcome. >> >> I have found a pcb file on my computer, I am not sure of its origin, >> that has a buggy rendering both in legacy and GAL in different, but >> similar ways. Maybe you

Re: [Kicad-developers] Geometry ongoing work

On 7/26/2016 7:20 AM, Nick Østergaard wrote: > Welcome. > > I have found a pcb file on my computer, I am not sure of its origin, > that has a buggy rendering both in legacy and GAL in different, but > similar ways. Maybe you should include this in your testing and > development. > > About

Re: [Kicad-developers] eeschema undo assertion

Duh! I was thinking wxLogDebug not wxASSERT. I'll start running debug builds to see if I can figure out why this is assertion is being triggered. On 7/25/2016 8:32 PM, Chris Pavlina wrote: > No need for a terminal on Linux, wx displays assertions in dialogs in > debug mode. > > On Mon, Jul 25,

Re: [Kicad-developers] Dialog text box autoselect

I prefer this behavior. One less key press or mouse action is a good thing. On 7/25/2016 7:35 PM, Chris Pavlina wrote: > Many of our dialogs have automatically selected the contents of their > primary field when they open, making it easy to replace them. I noticed > a while ago that this

Re: [Kicad-developers] Geometry ongoing work

Welcome. I have found a pcb file on my computer, I am not sure of its origin, that has a buggy rendering both in legacy and GAL in different, but similar ways. Maybe you should include this in your testing and development. About unittests, there is already some stuff in the qa folder using