Re: [Kicad-developers] 5.1 CMake Version Bump to 3.2

Great! :) fre. 15. maj 2020 13.50 skrev Ian McInerney : > FYI: I have just merged > https://gitlab.com/kicad/code/kicad/-/merge_requests/198 into 5.1 which > bumps the minimum CMake version required from 3.0 to 3.2 so that we can fix > https://gitlab.com/kicad/code/kicad/-/issues/4209. We discuss

[Kicad-developers] 5.1 CMake Version Bump to 3.2

FYI: I have just merged https://gitlab.com/kicad/code/kicad/-/merge_requests/198 into 5.1 which bumps the minimum CMake version required from 3.0 to 3.2 so that we can fix https://gitlab.com/kicad/code/kicad/-/issues/4209. We discussed the version bump at length inside https://gitlab.com/kicad/code

Re: [Kicad-developers] 5.1 branch freeze

Please see the comments about #4328 onnthe issue itself. I don't think you are testimg with the same conditions. ons. 6. maj 2020 12.55 skrev jp charras : > Le 06/05/2020 à 00:09, Nick Østergaard a écrit : > > Mmm, when you mean branch freeze, I assume you really mean that we > > have a string f

Re: [Kicad-developers] 5.1 branch freeze

Le 06/05/2020 à 00:09, Nick Østergaard a écrit : > Mmm, when you mean branch freeze, I assume you really mean that we > have a string freeze for the branch. > > I am sorta wondering why we can't enable the CI, for example. [1] > > Also as a heads up, there a couple of critical issues for the 5.1.

Re: [Kicad-developers] 5.1 branch freeze

Mmm, when you mean branch freeze, I assume you really mean that we have a string freeze for the branch. I am sorta wondering why we can't enable the CI, for example. [1] Also as a heads up, there a couple of critical issues for the 5.1.6 milestone being added after 5.1.6-rc1 [2], most importantly

Re: [Kicad-developers] 5.1 branch freeze

We are just under two weeks out of the 5.1.6 release. If anyone needs any extra time. Please let me know. Thanks, Wayne On 4/16/20 8:19 AM, Wayne Stambaugh wrote: > Done. > > On 4/16/20 7:58 AM, Nick Østergaard wrote: >> Just the tag in git >> >> tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh

Re: [Kicad-developers] 5.1 branch freeze

Hi, On 16.04.20 03:30, Wayne Stambaugh wrote: > The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable > release. Please do not make any commits to the 5.1 branch without first > confirming with the lead dev team and no translated string changes. Presumably that implies that tr

Re: [Kicad-developers] 5.1 branch freeze

Done. On 4/16/20 7:58 AM, Nick Østergaard wrote: > Just the tag in git > > tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh >: > > Nick, > > Do you need a source archive or just the tag? > > Cheers, > > Wayne > > On 4/16/20 3:58 AM, Nick Østerg

Re: [Kicad-developers] 5.1 branch freeze

Just the tag in git tor. 16. apr. 2020 13.25 skrev Wayne Stambaugh : > Nick, > > Do you need a source archive or just the tag? > > Cheers, > > Wayne > > On 4/16/20 3:58 AM, Nick Østergaard wrote: > > Can we have a 5.1.6-rc1 tag then? > > > > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh >

Re: [Kicad-developers] 5.1 branch freeze

Nick, Do you need a source archive or just the tag? Cheers, Wayne On 4/16/20 3:58 AM, Nick Østergaard wrote: > Can we have a 5.1.6-rc1 tag then? > > tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh >: > > The 5.1 branch has been frozen in order to prepare for t

Re: [Kicad-developers] 5.1 branch freeze

Can we have a 5.1.6-rc1 tag then? tor. 16. apr. 2020 03.30 skrev Wayne Stambaugh : > The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable > release. Please do not make any commits to the 5.1 branch without first > confirming with the lead dev team and no translated string chan

[Kicad-developers] 5.1 branch freeze

The 5.1 branch has been frozen in order to prepare for the 5.1.6 stable release. Please do not make any commits to the 5.1 branch without first confirming with the lead dev team and no translated string changes. I would like to release on Friday, May 15th if possible so please let me know if ther

Re: [Kicad-developers] 5.1 branch commits

Oops. At least one of those was mine. Apologies. Cheers, Jeff. > On 6 Nov 2019, at 22:08, Wayne Stambaugh wrote: > > Just a reminder, please do not push any commits to the 5.1 branch unless > it fixes a high priority bug (crash or data loss) without letting the > dev team know. I want to av

[Kicad-developers] 5.1 branch commits

Just a reminder, please do not push any commits to the 5.1 branch unless it fixes a high priority bug (crash or data loss) without letting the dev team know. I want to avoid the 5.1.1 and 5.1.3 disasters. Looking at the commits that flew in under the radar I didn't see anything that looked like a

Re: [Kicad-developers] 5.1 Hotkey problems

Seth, I am not sure about if they would cause usability issues on other platforms (it could be that they don't, since there have been no reports about it), but I do see a downside/idiosyncrasy with having them duplicated. Currently, the 5.1 hotkey configuration tools have no idea which tool is ena

Re: [Kicad-developers] 5.1 Hotkey problems

Hi Ian- On 2019-06-11 12:56, Ian McInerney wrote: Somewhat in relation to the patch I just sent, 5.1 currently has some hotkey issues with the default hotkeys that are being shipped with it, namely with pcbnew where: Paste is a duplicate hotkey of Add Microvia (both have Ctrl-V) Add a similar zo

[Kicad-developers] 5.1 Hotkey problems

Somewhat in relation to the patch I just sent, 5.1 currently has some hotkey issues with the default hotkeys that are being shipped with it, namely with pcbnew where: Paste is a duplicate hotkey of Add Microvia (both have Ctrl-V) Add a similar zone has an invalid hotkey (it is currently ctrl+shift+

Re: [Kicad-developers] 5.1 release

On 3/30/19 11:17 PM, Kevin Cozens wrote: On 2019-03-10 5:39 p.m., Adam Wolf wrote: Nick, is the docs tarball ready? That is an interesting question. Who maintains the file format doc? The only version I can find is over 2 years old. I'm writing a script to convert the files from a schematic

Re: [Kicad-developers] 5.1 release

On 2019-03-10 5:39 p.m., Adam Wolf wrote: Nick, is the docs tarball ready? That is an interesting question. Who maintains the file format doc? The only version I can find is over 2 years old. I'm writing a script to convert the files from a schematic capture program I used to use in to a form

Re: [Kicad-developers] 5.1 release

Nick, is the docs tarball ready? Thanks! Adam On Sun, Mar 10, 2019, 3:57 PM Wayne Stambaugh wrote: > I just pushed the initial draft of the release announcement to the > website repo[1]. Please take a look at it and let me know if I missed > anything or there are any issues. > > Thanks, > > W

Re: [Kicad-developers] 5.1 release

I just pushed the initial draft of the release announcement to the website repo[1]. Please take a look at it and let me know if I missed anything or there are any issues. Thanks, Wayne [1]: https://github.com/KiCad/kicad-website/blob/master/content/blog/release-5.1.0.adoc On 3/10/2019 3:37 PM,

Re: [Kicad-developers] 5.1 release

Thank you. søn. 10. mar. 2019 20.34 skrev Wayne Stambaugh : > Nick, > > I'll push the initial draft later this evening. I figure it will be > Tuesday or Wednesday until most of the packages are built and uploaded > to the website. > > Wayne > > On 3/10/19 3:25 PM, Nick Østergaard wrote: > > Plea

Re: [Kicad-developers] 5.1 release

Nick, I'll push the initial draft later this evening. I figure it will be Tuesday or Wednesday until most of the packages are built and uploaded to the website. Wayne On 3/10/19 3:25 PM, Nick Østergaard wrote: Please push the announcement to the website repo in case we want to add some mor

Re: [Kicad-developers] 5.1 release

Please push the announcement to the website repo in case we want to add some more info. søn. 10. mar. 2019 20.23 skrev Wayne Stambaugh : > Thank your Rene and all of the library developers for your efforts. > This should be the last of the repo tags so lets fire up those package > builders. I wi

Re: [Kicad-developers] 5.1 release

Thank your Rene and all of the library developers for your efforts. This should be the last of the repo tags so lets fire up those package builders. I will finish up the release announcement this evening so that once most of the packages are built I can make the release announcement. Cheers,

Re: [Kicad-developers] 5.1 release

The library has been tagged. It includes a few bug fixes since rc2. Details see: https://github.com/KiCad/kicad-symbols/issues/1470#issuecomment-471333999 On 08/03/19 20:16, Wayne Stambaugh wrote: The 5.1.0 release has been tagged and the source archive[1] has been uploaded to launchpad. Plea

Re: [Kicad-developers] 5.1 release

Forwarding to kicad-doc-devs in case anyone missed it, and adding tag intent on kicad-i18n and kicad-doc as: https://github.com/KiCad/kicad-i18n/issues/363 https://github.com/KiCad/kicad-doc/issues/691 On Fri, 8 Mar 2019 at 20:16, Wayne Stambaugh wrote: > The 5.1.0 release has been tagged and t

Re: [Kicad-developers] 5.1 release

The 5.1.0 release has been tagged and the source archive[1] has been uploaded to launchpad. Please let me know if there are any issues. The 5.1 development branch has been created. I decided to use -br-unknown for the KiCad version suffix of the 5.1 branch so that we can distinguish between the

[Kicad-developers] 5.1 release

I plan on tagging and branch 5.1 today around 12PM EST. Please do not push any further changes to the development branch unless a critical bug needs to be fixed. Will the repo maintainers tag all of the library, doc, and translation repos as soon as possible so we can get packages built. Once yo

[Kicad-developers] 5.1 bug triage

For final preparation of the 5.1 release, I just did a quick search of bug reports[1] that have not been closed or assigned to a milestone. There are a few reports with critical and high priority which I believe have been fixed. If you are aware that any of these bug reports have been fixed, pleas

Re: [Kicad-developers] 5.1 stable release

Hey Carsten, On 1/11/19 2:54 AM, Carsten Schoenert wrote: > Hello Wayne, > > I've some further questions regarding the planned version 5.1 and > switching to GTK3+. > > Am 17.12.18 um 16:18 schrieb Wayne Stambaugh: >> The other option assuming you have the gtk3 variant of wxwidgets >> installed

Re: [Kicad-developers] 5.1 stable release

Hello Wayne, I've some further questions regarding the planned version 5.1 and switching to GTK3+. Am 17.12.18 um 16:18 schrieb Wayne Stambaugh: > The other option assuming you have the gtk3 variant of wxwidgets > installed (if not `sudo apt-get install libwxgtk3.0-gtk3-dev`) you can > make that

Re: [Kicad-developers] 5.1 string freeze

Seth, On 1/5/19 4:42 PM, Seth Hillbrand wrote: > Am 2019-01-05 16:21, schrieb Wayne Stambaugh: >> Is there any reason not to start the 5.1 string freeze?  If so, please >> let me know.  Otherwise we can officially freeze the strings so our >> translators can start work towards the 5.1 stable relea

Re: [Kicad-developers] 5.1 string freeze

I’m not aware of anything pending. Cheers, Jeff. > On 5 Jan 2019, at 21:21, Wayne Stambaugh wrote: > > Is there any reason not to start the 5.1 string freeze? If so, please > let me know. Otherwise we can officially freeze the strings so our > translators can start work towards the 5.1 stabl

Re: [Kicad-developers] 5.1 string freeze

Am 2019-01-05 16:21, schrieb Wayne Stambaugh: Is there any reason not to start the 5.1 string freeze? If so, please let me know. Otherwise we can officially freeze the strings so our translators can start work towards the 5.1 stable release. For 5.0, the string freeze was RC2. Are we tagging

[Kicad-developers] 5.1 string freeze

Is there any reason not to start the 5.1 string freeze? If so, please let me know. Otherwise we can officially freeze the strings so our translators can start work towards the 5.1 stable release. Cheers, Wayne ___ Mailing list: https://launchpad.net/

Re: [Kicad-developers] 5.1 stable release

On 12/16/2018 1:35 PM, Seth Hillbrand wrote: > Am 2018-12-16 13:24, schrieb Eeli Kaikkonen: >> Someone in the user forum asked how to compile with GTK3 >> (https://forum.kicad.info/t/force-gtk3-build/14173). I still don't >> know. I just upgraded Kubuntu to 18.10 and had also to reconfigure >> KiCa

Re: [Kicad-developers] 5.1 stable release

Am 2018-12-16 13:24, schrieb Eeli Kaikkonen: Someone in the user forum asked how to compile with GTK3 (https://forum.kicad.info/t/force-gtk3-build/14173). I still don't know. I just upgraded Kubuntu to 18.10 and had also to reconfigure KiCad compilation from scratch. But I didn't notice there any

Re: [Kicad-developers] 5.1 stable release

Someone in the user forum asked how to compile with GTK3 ( https://forum.kicad.info/t/force-gtk3-build/14173). I still don't know. I just upgraded Kubuntu to 18.10 and had also to reconfigure KiCad compilation from scratch. But I didn't notice there anything about GTK3 and don't know what the depen

Re: [Kicad-developers] 5.1 stable release

Hey Marco, On 12/10/2018 11:17 AM, Marco Ciampa wrote: > On Sun, Dec 09, 2018 at 01:22:30PM -0500, Wayne Stambaugh wrote: >> Now that 5.0.2 is out the door, it's time to get serious about 5.1. >> This is the official 5.1 feature freeze announcement. I plan on make >> the official string freeze an

Re: [Kicad-developers] 5.1 stable release

On Sun, Dec 09, 2018 at 01:22:30PM -0500, Wayne Stambaugh wrote: > Now that 5.0.2 is out the door, it's time to get serious about 5.1. > This is the official 5.1 feature freeze announcement. I plan on make > the official string freeze announcement in another week or two so if you > have any UI str

Re: [Kicad-developers] 5.1 stable release

Hey Carsten, On 12/10/2018 9:15 AM, Carsten Schoenert wrote: > Hello Wayne, > > Am 10.12.18 um 14:04 schrieb Wayne Stambaugh: >> Hey John, >> >> I can help with the test against gtk3. I am currently using gtk3 on my >> home system although I have not yet tried to build with gtk3 and >> phoenix.

Re: [Kicad-developers] 5.1 stable release

Hello Wayne, Am 10.12.18 um 14:04 schrieb Wayne Stambaugh: > Hey John, > > I can help with the test against gtk3. I am currently using gtk3 on my > home system although I have not yet tried to build with gtk3 and > phoenix. I'm not sure Debian supports this yet because I believe > wxwidgets use

Re: [Kicad-developers] 5.1 stable release

Hey John, I can help with the test against gtk3. I am currently using gtk3 on my home system although I have not yet tried to build with gtk3 and phoenix. I'm not sure Debian supports this yet because I believe wxwidgets used to build phoenix is 3.1.1 or later where wxwidgets is 3.0.4 which woul

Re: [Kicad-developers] 5.1 stable release

Am 2018-12-09 14:41, schrieb John Beard: On that note, how many people are actually using gtk3 for actual designs? I know I am, but I've been stuck with fallback for a while due to lagging, which I think is likely fixed now with the event stuff, but I haven't had time to rebuild and check. Hi

Re: [Kicad-developers] 5.1 stable release

Hi Wayne, I can take a look at doing that. I'm on gtk3, so it's easy to check. On that note, how many people are actually using gtk3 for actual designs? I know I am, but I've been stuck with fallback for a while due to lagging, which I think is likely fixed now with the event stuff, but I have

[Kicad-developers] 5.1 stable release

Now that 5.0.2 is out the door, it's time to get serious about 5.1. This is the official 5.1 feature freeze announcement. I plan on make the official string freeze announcement in another week or two so if you have any UI string work that you are planning to do, please try to wrap it up in the nex

Re: [Kicad-developers] 5.1

Hi Wayne, On 10/25/18 5:17 PM, Wayne Stambaugh wrote: [snip] > I looked at this and it only works for linux. Although it may be highly > unlikely, given that wxpython and wxwidgets can be build against gtk on > windows and msys2 provides gtk2, gtk3, and as of a few days ago gtk4 > packages, there

Re: [Kicad-developers] 5.1

On 10/25/2018 2:37 AM, Maciej Sumiński wrote: > On 10/25/18 2:23 AM, Seth Hillbrand wrote: >> Am 2018-10-24 17:20, schrieb Maciej Suminski: >>> Actually I was pretty sure that my approach is bullet-proof, but perhaps >>> I do not get where the trap is hidden. As far as I understand, Seth >>> experi

Re: [Kicad-developers] 5.1

On 10/25/18 2:23 AM, Seth Hillbrand wrote: > Am 2018-10-24 17:20, schrieb Maciej Suminski: >> Actually I was pretty sure that my approach is bullet-proof, but perhaps >> I do not get where the trap is hidden. As far as I understand, Seth >> experienced problems when pcbnew (wxWidgets/gtk2) loaded w

Re: [Kicad-developers] 5.1

Am 2018-10-24 17:20, schrieb Maciej Suminski: Actually I was pretty sure that my approach is bullet-proof, but perhaps I do not get where the trap is hidden. As far as I understand, Seth experienced problems when pcbnew (wxWidgets/gtk2) loaded wxPython shared libraries (wxWidgets/gtk3), which

Re: [Kicad-developers] 5.1

Hi Wayne, On 10/24/18 5:35 PM, Wayne Stambaugh wrote: > On 10/23/2018 10:12 AM, Maciej Sumiński wrote: >> On 10/23/18 3:00 PM, Seth Hillbrand wrote: >>> The issues were asserts, missing icons and a crash on exit.  I tracked >>> it down to a wx module that was loaded by pip in my user cache from wh

Re: [Kicad-developers] 5.1

On 10/23/2018 10:12 AM, Maciej Sumiński wrote: > On 10/23/18 3:00 PM, Seth Hillbrand wrote: >> The issues were asserts, missing icons and a crash on exit.  I tracked >> it down to a wx module that was loaded by pip in my user cache from when >> I was testing gtk3 builds.  Yay, python.  Removing it

Re: [Kicad-developers] 5.1

On 10/23/18 3:00 PM, Seth Hillbrand wrote: > The issues were asserts, missing icons and a crash on exit.  I tracked > it down to a wx module that was loaded by pip in my user cache from when > I was testing gtk3 builds.  Yay, python.  Removing it cleared all issues. Indeed it sounds like gtk2/gtk3

Re: [Kicad-developers] 5.1

Am 2018-10-23 03:08, schrieb Maciej Sumiński: Hi Seth, On 10/22/18 11:50 PM, Seth Hillbrand wrote: Hi Orson- This looks very nice.  It works well for me with scripting off on Debian Stretch.  I had some issues with scripting on that I haven't encountered with the master branch but I suspect

Re: [Kicad-developers] 5.1

Hi Seth, On 10/22/18 11:50 PM, Seth Hillbrand wrote: > Hi Orson- > > This looks very nice.  It works well for me with scripting off on Debian > Stretch.  I had some issues with scripting on that I haven't encountered > with the master branch but I suspect that this is a gtk2/3 issue because > I c

Re: [Kicad-developers] 5.1

Am 2018-10-21 19:09, schrieb Maciej Suminski: I have just fixed the last printing related bug I knew about and rebased the code on the current master [1]. I consider it ready to merge as long as there are no other issues found. The branch still does not bring Cairo printing backend to eeschema,

Re: [Kicad-developers] 5.1

On 10/22/2018 5:52 AM, jp charras wrote: > Le 22/10/2018 à 01:09, Maciej Suminski a écrit : >> I have just fixed the last printing related bug I knew about and rebased >> the code on the current master [1]. I consider it ready to merge as long >> as there are no other issues found. The branch still

Re: [Kicad-developers] 5.1

Le 22/10/2018 à 01:09, Maciej Suminski a écrit : > I have just fixed the last printing related bug I knew about and rebased > the code on the current master [1]. I consider it ready to merge as long > as there are no other issues found. The branch still does not bring > Cairo printing backend to ee

Re: [Kicad-developers] 5.1

I have just fixed the last printing related bug I knew about and rebased the code on the current master [1]. I consider it ready to merge as long as there are no other issues found. The branch still does not bring Cairo printing backend to eeschema, which is planned to be added soon, but not requir

Re: [Kicad-developers] 5.1

Hi, Am 19.10.18 um 16:46 schrieb Carsten Schoenert: > Hello Wayne, > > Am 19.10.18 um 15:35 schrieb Wayne Stambaugh: > ... >> packages for it. I'm concerned we are going to spend a huge amount of >> effort for little or no net gain. Has wx 3.1.1 been packaged for Debian >> yet? > > As far I se

Re: [Kicad-developers] 5.1

Seth, On 10/19/2018 11:53 AM, Seth Hillbrand wrote: > Am 2018-10-19 03:37, schrieb Maciej Sumiński: >> As far as I remember there are two problems related to GTK versions: >> - Having KiCad and wxPython build againt different toolkits results in >> wxWidgets symbol conflicts when wxPython is loade

Re: [Kicad-developers] 5.1

Hi Carsten- Am 2018-10-19 05:53, schrieb Carsten Schoenert: 5.0.1 is almost unusable if build with libwxgtk3.0-gtk3-dev and right now the KiCad package in testing would become RC if the transition to libwxgtk3.0-gtk3-{0v5,dev} would start. Right. This was the (or one of the) motivation(s) beh

Re: [Kicad-developers] 5.1

Am 2018-10-19 03:37, schrieb Maciej Sumiński: As far as I remember there are two problems related to GTK versions: - Having KiCad and wxPython build againt different toolkits results in wxWidgets symbol conflicts when wxPython is loaded. This issue should be resolved by linking KiCad against the

Re: [Kicad-developers] 5.1

Hi, I made an GTK3 build with wx3.0.4 and didn't noticed more bugs than with wx3.1.1 and GTK3 on a quick glance. I'm using X11 as display manager, and run a Arch based system. Regards, Thomas Am 19.10.18 um 11:53 schrieb Carsten Schoenert: > Hello Seth, > > Am 18.10.18 um 21:52 schrieb s...@hi

Re: [Kicad-developers] 5.1

Hello Wayne, Am 19.10.18 um 15:35 schrieb Wayne Stambaugh: ... > packages for it. I'm concerned we are going to spend a huge amount of > effort for little or no net gain. Has wx 3.1.1 been packaged for Debian > yet? As far I see and know not yet. https://qa.debian.org/developer.php?email=team%

Re: [Kicad-developers] 5.1

Carsten, On 10/19/2018 5:53 AM, Carsten Schoenert wrote: > Hello Seth, > > Am 18.10.18 um 21:52 schrieb s...@hillbrand.org: >> * sense flipped here * Debian 9 = python-wxgtk only uses gtk2 and >> Debian 10 = python-wxgtk only uses gtk3 > > yes, and for wxpython3.0 there is currently no backpor

Re: [Kicad-developers] 5.1

Hey Orson, On 10/19/2018 4:16 AM, Maciej Sumiński wrote: > On 10/17/18 8:30 PM, Wayne Stambaugh wrote: >> Now that the Eeschema gal code has been merged into the development >> branch and things seem reasonably stable, we need to start thinking >> about the 5.1 release. I would like to merge Thom

Re: [Kicad-developers] 5.1

Hello Seth, Am 18.10.18 um 21:52 schrieb s...@hillbrand.org: > * sense flipped here * Debian 9 = python-wxgtk only uses gtk2 and > Debian 10 = python-wxgtk only uses gtk3 yes, and for wxpython3.0 there is currently no backport for stretch available and probably will never be due the massive rev

Re: [Kicad-developers] 5.1

Dear Orson&All, On Freitag, 19. Oktober 2018 10:16:24 CEST Maciej Sumiński wrote: > On 10/17/18 8:30 PM, Wayne Stambaugh wrote: > > Now that the Eeschema gal code has been merged into the development > > branch and things seem reasonably stable, we need to start thinking > > about the 5.1 release.

Re: [Kicad-developers] 5.1

On 10/17/18 8:30 PM, Wayne Stambaugh wrote: > Now that the Eeschema gal code has been merged into the development > branch and things seem reasonably stable, we need to start thinking > about the 5.1 release. I would like to merge Thomas' python 3 code and > Orson's cairo print code as soon as the

Re: [Kicad-developers] 5.1

On 10/18/18 9:48 PM, s...@hillbrand.org wrote: > Hi Wayne- > > We should probably start moving the default build on some Linuxes over > to gtk3 as the gtk2/3 conflicts were one of the prime drivers to the > GAL-legacy switch in eeschema.  This requires turning on > -DUSE_WX_GRAPHICS_CONTEXT as wel

Re: [Kicad-developers] 5.1

Am 2018-10-18 17:35, schrieb Thomas Pointhuber: Short question: what does USE_WX_GRAPHICS_CONTEXT change? I didn't see any differences on my gtk3 builds. gtk3 wxWidgets had issues with XOR for drawing [1][2][3] -S [1] https://trac.wxwidgets.org/ticket/2461 [2] https://github.com/wxWidgets/Pho

Re: [Kicad-developers] 5.1

Hi, I agree that GTK3 should be a first class citizen of supported toolkit in the future. I have gtk3 builds running for testing purpose, and at the moment scrolling is the most annoying issue in my opinion, which makes it nearly unusable to simply zoom in/out reliable: https://bugs.launchpad.ne

Re: [Kicad-developers] 5.1

On 2018-10-18 15:48, s...@hillbrand.org wrote: Unfortunately, this is an either/or in that Debian9 (and derivatives in Ubuntu) doesn't provide a python-wxgtk built against gtk2 and Debian 10/Ubuntu 18.04 don't provide python-wxgtk built against gtk3. * sense flipped here * Debian 9 = python-wx

Re: [Kicad-developers] 5.1

On 2018-10-18 10:10, Wayne Stambaugh wrote: Hi John, The legacy canvas in the pcb tools and gerbview is slated for removal during v6 development. I image it will happen fairly quickly after 5.1 is released. I also expect there to be great wailing and gnashing of teeth once it's removed but kee

Re: [Kicad-developers] 5.1

Hi, This is what I was getting at. If outright disabling of the legacy canvas (with or without the cull of associated code) is not desirable for 5.1, is it feasible to switch the legacy_wx canvas to legacy_gal in pcbnew, so the options are then "GAL canvas+legacy tools" and "GAL canvas+new tools"

Re: [Kicad-developers] 5.1

Hi Wayne, Sounds good! What's the plan for the WX legacy canvases? Pcbnew, gerbview, cvpcb and pl_editor still use the WX canvas in legacy tool mode (but also have GAL canvas+tool framework), whereas eeschema has a GAL canvas and legacy tools. I know we're not planning to remove the legacy tool s

Re: [Kicad-developers] 5.1

Hi John, The legacy canvas in the pcb tools and gerbview is slated for removal during v6 development. I image it will happen fairly quickly after 5.1 is released. I also expect there to be great wailing and gnashing of teeth once it's removed but keeping it around doesn't make sense. We will ju

[Kicad-developers] 5.1

Now that the Eeschema gal code has been merged into the development branch and things seem reasonably stable, we need to start thinking about the 5.1 release. I would like to merge Thomas' python 3 code and Orson's cairo print code as soon as they are ready to go so we can get some additional test

Re: [Kicad-developers] 5.1 UI feedback

Thanks, Jeff. I'll give it a try when it hits the nightlies. Diego On Fri, Jul 20, 2018 at 6:54 PM Jeff Young wrote: > I’ve merged this suggestion. > > Unfortunately wxGrid conspires against us in trying to present the buttons > when the grid cell is focused, but you do get them once you try t

Re: [Kicad-developers] 5.1 UI feedback

I’ve merged this suggestion. Unfortunately wxGrid conspires against us in trying to present the buttons when the grid cell is focused, but you do get them once you try to edit the cell. Cheers, Jeff. > On 20 Jul 2018, at 13:52, Jeff Young wrote: > > No need. I’ve just about got it implement

Re: [Kicad-developers] 5.1 UI feedback

No need. I’ve just about got it implemented so a reminder would be surplus to requirements. ;) > On 20 Jul 2018, at 12:32, Wayne Stambaugh wrote: > > I don't remember seeing a bug report for that just Diego's post to the > mailing list. If you want me to, I will create a bug report. > > On 0

Re: [Kicad-developers] 5.1 UI feedback

I don't remember seeing a bug report for that just Diego's post to the mailing list. If you want me to, I will create a bug report. On 07/19/2018 03:53 PM, Jeff Young wrote: > I thought there was already a bug for this (reported by Gabriel > perhaps?), but I can’t seem to find it. > >> On 19 Jul

Re: [Kicad-developers] 5.1 UI feedback

I like the button idea, the same thing should be done in the schematic field editor, that would basically replace cvpcb for most usecases. On Thu, Jul 19, 2018 at 2:53 PM, Jeff Young wrote: > I thought there was already a bug for this (reported by Gabriel perhaps?), > but I can’t seem to find it

Re: [Kicad-developers] 5.1 branch

Cool. Thanks, Tom. > On 19 Jul 2018, at 16:28, Tomasz Wlostowski wrote: > > On 18/07/18 13:06, Jeff Young wrote: >> Hi Tom, et al, >> >> I assume we just need to drop wxDC for the canvas, but that UI constructs >> (such as colour swatches, etc.) would continue to use wxDC? > > To clarify: SC

Re: [Kicad-developers] 5.1 UI feedback

I thought there was already a bug for this (reported by Gabriel perhaps?), but I can’t seem to find it. > On 19 Jul 2018, at 20:40, Wayne Stambaugh wrote: > > I second this motion. I didn't find the right click trick so I fell > back to cvpcb which is overkill to change the footprint of a sing

Re: [Kicad-developers] 5.1 UI feedback

I second this motion. I didn't find the right click trick so I fell back to cvpcb which is overkill to change the footprint of a single symbol. A tooltip might be useful here as well. On 7/19/2018 3:19 PM, Diego Herranz wrote: > Hi, > > I've started to test these changes and, on the Symbol prop

Re: [Kicad-developers] 5.1 UI feedback

Hi, I've started to test these changes and, on the Symbol properties dialog, I found it hard to assign a footprint. Before, there used to be a button to open the Footprint selector window. Now you seem to need right click on the footprint field and "select footprint" and that only works if you're

Re: [Kicad-developers] 5.1 testing

Windows. I can test linux after I get home from work this evening. On 7/19/2018 2:14 PM, Jeff Young wrote: > Windows or Linux? > > It should highlight to two footnotes, although I’m not sure I’ve tested > courtyard errors. > > Try a track too close to a pad, and it should highlight the track a

Re: [Kicad-developers] 5.1 testing

Windows or Linux? It should highlight to two footnotes, although I’m not sure I’ve tested courtyard errors. Try a track too close to a pad, and it should highlight the track and the pad. (But probably not on Windows, as it’s based on the same code we use for selection disambiguation highlighti

Re: [Kicad-developers] 5.1 testing

What exactly is supposed to get highlighted? I have board I'm working on with some overlapped courtyard errors and I don't see any highlighting when I select a error in the drc dialog or hover over the drc markers. I do see the board pan to show the drc marker when it is underneath the dialog. W

[Kicad-developers] 5.1 testing

Could someone test the DRC highlighting on Linux and Windows. (Since it uses the same selection highlighting code my guess is that it doesn’t work on Windows.) Run a DRC on a board that has some errors. Right click on an error in the DRC errors list. Hover back and forth over the two entries in

Re: [Kicad-developers] 5.1 branch

On 18/07/18 13:06, Jeff Young wrote: > Hi Tom, et al, > > I assume we just need to drop wxDC for the canvas, but that UI constructs > (such as colour swatches, etc.) would continue to use wxDC? To clarify: SCH/PCB preview widgets will also use GAL. Tom > > Thanks, > Jeff. > > >> On 17 Jul 2

Re: [Kicad-developers] 5.1 branch

Hi Jeff, Yes, for the moment we work to replace wxDC only in places that really need it. So far it was necessary in pcbnew to boost performance, now eeschema suffers the same problem with GTK3. Cheers, Orson On 07/18/2018 01:06 PM, Jeff Young wrote: > Hi Tom, et al, > > I assume we just need to

Re: [Kicad-developers] 5.1 UI feedback

Changes in. Could Kevin or Wayne please post the following dialogs one more time: 1) Change Footprints 2) CvPCB (with footprint selected from right column) 3) Footprint Properties 4) Edit Track & Via Properties Thanks, Jeff. > On 18 Jul 2018, at 15:28, Jeff Young wrote: > > Yeah, the “Show”

Re: [Kicad-developers] 5.1 UI feedback

Yeah, the “Show” label of the Output Messages checkboxes is misplaced too. I’ll have another build along shortly…. Cheers, Jeff. > On 18 Jul 2018, at 15:05, Kevin Cozens wrote: > > On 2018-07-18 08:32 AM, Wayne Stambaugh wrote: >> Attached are the updated screen shots. > > One minor point. I

Re: [Kicad-developers] 5.1 UI feedback

On 2018-07-18 08:32 AM, Wayne Stambaugh wrote: Attached are the updated screen shots. One minor point. In the first screen shot the icon with the books and magnifying glass is on the right side of the dialog the first time it appears but is just after the end of the entry field the second tim

Re: [Kicad-developers] 5.1 branch

Hi Tom, et al, I assume we just need to drop wxDC for the canvas, but that UI constructs (such as colour swatches, etc.) would continue to use wxDC? Thanks, Jeff. > On 17 Jul 2018, at 15:44, Tomasz Wlostowski wrote: > > On 16/07/18 17:54, Wayne Stambaugh wrote: >> I was really hoping just to

Re: [Kicad-developers] 5.1 UI feedback

Hi Wayne, I merged a bunch of spacing changes (only in master for now). When you have a chance could you screen-shot those same 4 dialogs again? Thanks, Jeff. > On 17 Jul 2018, at 20:48, Wayne Stambaugh wrote: > > Hey Jeff, > > The text size is better but there is now dead space above the b

  1   2   >