[Kicad-developers] A consistent name for the Aux Origin?
I just posted this in the KiCad "Software" forum for comment, but ultimately this is a dev question. In Pcbnew, you can place what is known internally as the “Aux Origin”. Thus far the only use for this has been to set the origin for generating Gerber files. The user interface doesn’t name this point consistently: * The Pcbnew docs call this the “auxillary origin”, and describes setting the “coordinates origin” * The toolbar icon tooltip calls it the “auxillary axis origin” * The “Generate Drill Files” dialog calls it the “auxillary axis” * The “Place” menu calls it the “Drill and Place Offset” * The “Move Item” dialog calls it the “Drill/Place Origin” * The (new, unmerged) v6 preferences dialog currently calls it the “Aux Origin” With the changes in Pcbnew for v6, we’ll be able to make this the origin for displayed coordinates when doing layout. “Drill and Place” doesn’t seem like a good description for this point. I’d lean toward calling it the “Coordinate Origin” everywhere, except for one thing: the v6 preferences dialog allows the user to choose the origin for displayed coordinates as one of the Page Origin, the Aux Origin, or the Grid Origin. Suggestions? Thoughts? ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] kicad aborts when wxpython is enabled
Just gave this a try, but pcbnew also fails immediately. I'll file a bugreport this evening. regards, Mark Andrew Lutsenko wrote: Another good thing to check would be if the issue only happens when trying to run pcbnew standalone. If launched from kicad process there should be no race since kicad binary doesn't touch any python afaik. On Thu, May 16, 2019 at 5:53 AM Seth Hillbrand wrote: > Am 2019-05-16 06:29, schrieb mdoes...@xs4all.nl: > > I've seen the following problem for some time when wxpython is enabled: > > > > > > > [xcb] Unknown sequence number while processing reply > > [xcb] Most likely this is a multi-threaded client and XInitThreads has > > not been called > > [xcb] Aborting, sorry about that. > > kicad: xcb_io.c:643: _XReply: Assertion > > `!xcb_xlib_threads_sequence_lost' failed. > > Aborted > > > > > > > If I disable wxpython everything just works. I suspect it's a problem > > with my configuration, since it's almost impossible to start pcbnew. Is > > there anyone who has a suggestion where to look? > > This looks like a race condition in the wxInit() between python and > pcbnew. Can you please open a bug report for this? > > -Seth > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] kicad aborts when wxpython is enabled
Another good thing to check would be if the issue only happens when trying to run pcbnew standalone. If launched from kicad process there should be no race since kicad binary doesn't touch any python afaik. On Thu, May 16, 2019 at 5:53 AM Seth Hillbrand wrote: > Am 2019-05-16 06:29, schrieb mdoes...@xs4all.nl: > > I've seen the following problem for some time when wxpython is enabled: > > > > > > > [xcb] Unknown sequence number while processing reply > > [xcb] Most likely this is a multi-threaded client and XInitThreads has > > not been called > > [xcb] Aborting, sorry about that. > > kicad: xcb_io.c:643: _XReply: Assertion > > `!xcb_xlib_threads_sequence_lost' failed. > > Aborted > > > > > > > If I disable wxpython everything just works. I suspect it's a problem > > with my configuration, since it's almost impossible to start pcbnew. Is > > there anyone who has a suggestion where to look? > > This looks like a race condition in the wxInit() between python and > pcbnew. Can you please open a bug report for this? > > -Seth > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
