I don't see an advantage of creating a 5.0 branch before more issues are fixed
https://github.com/KiCad/kicad-doc/issues
We don't gain anything by having a 5.0 branch other than wasting
valuable time. IMHO.
On Thu, 11 Oct 2018 at 08:13, Marco Ciampa wrote:
>
> On Wed, Oct 10, 2018 at 07:04:16PM
The branch seems to be fairly buildable. It is only some of the first
commits that does not build well, see
https://jenkins.simonrichter.eu:8443/job/windows-kicad-msys2-evaluate/86/artifact/build-report.txt/*view*/
On Sat, 29 Sep 2018 at 01:39, Simon Richter wrote:
>
> Hi,
>
> > Really guys,
r., 14. Sep. 2018 um 06:45 Uhr schrieb Nick Østergaard
> :
>>
>> This still needs testing on macos, but as no one have proved it to be broken
>> ok macos, I vote for merging as is.
>>
>> It has been tested on windows and linux.
>>
>> fre. 14. sep. 2018
Using chrome 69.0.3497.100, I can still browse the page without issues.
This is currently the latest release of chrome.
Where is this described? I mean, that chrome will refuse to load http pages?
Proper support for proper https will happen in the future, but not tomorrow.
man. 24. sep. 2018
This still needs testing on macos, but as no one have proved it to be
broken ok macos, I vote for merging as is.
It has been tested on windows and linux.
fre. 14. sep. 2018 11.39 skrev Thomas Pointhuber :
> Hi,
>
> I posted this proposal on launchpad, but no answers so far:
> * see:
In addition to that I can note; that it follows the 5.0 branch for the
kicad source and the kicad-i18n, but is using the 5.0.0 tag for
everything else.
On Mon, 10 Sep 2018 at 14:29, Nick Østergaard wrote:
>
> Hi Seth
>
> I have created them now, they are currently locat
It is not ideal, but should be good enough.
Nick
On Mon, 10 Sep 2018 at 11:11, Nick Østergaard wrote:
>
> I will add it for the windows builds soon.
>
> I don't think there is a nightly PPA for the 5.0 branch yet, there was
> for the 4.0 branch for a period at least.
> On Sun, 9 Sep 2
I will add it for the windows builds soon.
I don't think there is a nightly PPA for the 5.0 branch yet, there was
for the 4.0 branch for a period at least.
On Sun, 9 Sep 2018 at 16:22, Seth Hillbrand wrote:
>
> Hi All-
>
> Can we update the packaging scripts that produce nightly packages to also
Hi Seth
I have made the milestone, currently with this description.
"For stuff we don't really need to block 5.0.1 and we would like to
backport to 5.0..."
I am not sure we need this milestone, I thought we went for 5.1.0. But
as I am far behind with the emails, I created it anyways to not
I cant view the patch via my phone right now, but please add a simple
unittest in the qa folder as well.
fre. 31. aug. 2018 14.56 skrev Wayne Stambaugh :
> Andrew,
>
> I looked at this patch an it looks fine to me. I fine with exposing the
> 3D model properties in the Python scripting. Is
In the Symbol Library Browser
ons. 29. aug. 2018 01.47 skrev Jeff Young :
> Hi Tom,
>
> I pushed changes to
> https://git.launchpad.net/~jeyjey/kicad/log/?h=tom-eeschema-gal-aug27.
>
> This includes converting the Choose Symbol dialog to GAL, moving the
> GAL_DISPLAY_OPTIONS to common, and
Kevin, that is partly correct. But it is casued because the master
branch on Tom's repo is very old. This should not be needed anymore,
if it was not removed completely. There should not be any need for bzr
anymore.
On Tue, 28 Aug 2018 at 16:46, Kevin Cozens wrote:
>
> On 2018-08-27 03:43 PM,
There are still open issues that either need to be analyzed.
https://launchpad.net/kicad/+milestone/5.0.1
On Wed, 22 Aug 2018 at 07:51, Ingo Kletti wrote:
>
> Hello,
>
> don't want to sound like a "are we there yet?"-like kid, but: What is
> the status of the 5.0.x release?
>
> I'm asking
No we do not currently log downloads actively.
Den man. 23. jul. 2018 kl. 05.03 skrev Adam Wolf
:
>
> Do we capture download statistics on the file server at all? It would
> be really fun to see how many folks are downloading things. I know it
> is not an accurate representation of userbase, but
If you just push it to a local branch somwhere I can easily trigger a
windows build.
Den tir. 21. aug. 2018 kl. 20.05 skrev Wayne Stambaugh :
>
> Hey Tom,
>
> On 8/9/2018 10:12 AM, Tomasz Wlostowski wrote:
> > Hi all,
> >
> > The patch set in the attachment brings back the legacy autoplacement
> >
Alternatively, we could provide them in a dedicated repository on the
kicad org on github. Then they are decoupled from the normal source
and the wild west for IDE confs are self contained. This is just a
suggestion if you think this would be useful.
Den tir. 21. aug. 2018 kl. 19.49 skrev Wayne
Thank you, enjoy your vacation. :)
Den tor. 16. aug. 2018 kl. 09.26 skrev Marco Ciampa :
>
> Saturday 18 morning I'll be leaving for vacation until sunday 26, this
> time without any laptop.
>
> To the admins: please keep an eye on the translations and docs pull
> requests.
>
> To the translators
Any update on this? It does not look like it is merged.
Den tor. 26. jul. 2018 kl. 17.17 skrev John Beard :
>
> Hi,
>
> Another -Wcatch-value warning, this time in kicad2step.cpp.
>
> Cheers,
>
> John
> ___
> Mailing list:
errors. It looks
like it needs to be updated to py3k syntax.
Regards
Nick Østergaard
Den lør. 4. aug. 2018 kl. 12.23 skrev Thomas Pointhuber
:
>
> Hi,
>
> I managed to get KiCad to run with Python 3 as well as did some quick
> verification that basic methods are working using CLI
It looks lile the patch does not compile, but maybe the patch was not
applied correctly. You should be able to look at the patched code in the
workspace.
tir. 7. aug. 2018 21.39 skrev Nick Østergaard :
> I triggered this windows build with the patch.
>
> https://jenkins.simonrichter.eu
Yes
https://bugs.launchpad.net/kicad/+bug/1785113
Den søn. 5. aug. 2018 kl. 21.56 skrev Wayne Stambaugh :
>
> I just updated my laptop build (Ubuntu 17.10 with stock gnome desktop)
> and notice a rather odd layout of the new exit dialog. Is anyone else
> seeing this?
>
> Wayne
>
The one with the fatter text and lighter blue.
søn. 5. aug. 2018 17.22 skrev Kevin Cozens :
> On 2018-08-05 08:22 AM, John Beard wrote:
> > Eagle-eyed (is that an offensive slur on a KiCad list?) Nick noticed
> > that the doxygen header logo is actually slightly incorrect.
> > Presumably I used
The new patch looks good to me.
Den søn. 5. aug. 2018 kl. 14.22 skrev John Beard :
>
> Hi,
>
> Eagle-eyed (is that an offensive slur on a KiCad list?) Nick noticed
> that the doxygen header logo is actually slightly incorrect.
> Presumably I used the wrong file for a source, not sure where it came
Ok, I completely forgot about this, but I have uploaded it for 5.0.0 now.
Den man. 4. sep. 2017 kl. 18.26 skrev Nick Østergaard :
>
> No, but good point. I will try to make that available.
>
> Den 4. sep. 2017 5.10 PM skrev "Greg Smith" :
>>
>> Is there an equ
Hello
Attached is a patch to update the dev-docs about the new option ot use
OCC instead of OCE
Regards
Nick Østergaard
From e8300b778c29f22f94023c4ae1683653f2e84977 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Nick=20=C3=98stergaard?=
Date: Thu, 2 Aug 2018 19:11:04 +0200
Subject: [PATCH] Add
** Changed in: kicad
Status: New => Invalid
** Changed in: kicad-footprints (Ubuntu)
Status: New => Invalid
** Changed in: kicad-packages3d (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello
It may be off by default, but should we enable it by default? I think
yes. It has been discussed briefly here and there.
If we like it in the 5.0 builds I propose we set it as default on on
the 5.0 branch now.
Nick
Den man. 23. jul. 2018 kl. 05.48 skrev Seth Hillbrand :
>
> Hi Devs-
>
>
Yes.
https://github.com/KiCad/kicad-winbuilder/issues/53
It does basically work that way, but simply needs a bit of refactoring on
the build server to support both mechanisms, but as getting 5.0.0 has been
a priority have not not done it yet.
Nick
Den ons. 1. aug. 2018 kl. 15.32 skrev Ben Hest
FYI there is also a GTK setting to choose to show icons or not, so
some users on linux see the icons and other not depending on that
option, and also depending on the kicad option to show icons or not.
Den tir. 31. jul. 2018 kl. 13.45 skrev John Beard :
>
> Flag icons are also (ab)used in the
Hi Andrew
Seth already shared the build log.
tir. 31. jul. 2018 05.29 skrev Andrew Lutsenko :
> I just noticed that my patch was reverted with reference to a build
> failure with gcc 4.9.2
>
> Could you share the error messages too?
> Also curios which platform uses such ancient compiler. I
I guess we could remove the last section entirely. Please submit a PR
for how you would like to describe the assembler code thingie.
Den søn. 22. jul. 2018 kl. 22.20 skrev Nick Østergaard :
>
> woopsie, that meant to only to up to 4.0.7
> Den søn. 22. jul. 2018 kl. 22.19 skrev Simo
woopsie, that meant to only to up to 4.0.7
Den søn. 22. jul. 2018 kl. 22.19 skrev Simon Richter :
>
> Hi,
>
> On 22.07.2018 18:44, Wayne Stambaugh wrote:
>
> > I just pushed the updated version of the v5 release announcement[1].
> > Please let me know if you find any missing features.
>
> The
I have now published the page, feel free to add PR's to make it better
or correct errornous info.
Den søn. 22. jul. 2018 kl. 20.04 skrev Nick Østergaard :
>
> I added some more information to the release note.
> Den søn. 22. jul. 2018 kl. 19.18 skrev Nick Østergaard :
> >
> >
I added some more information to the release note.
Den søn. 22. jul. 2018 kl. 19.18 skrev Nick Østergaard :
>
> Depending on what you like, I think we should just release the doc
> today, I will be away from tomorrow anyways, and it looks like
> different linux packagers startin
Depending on what you like, I think we should just release the doc
today, I will be away from tomorrow anyways, and it looks like
different linux packagers starting to package it anyways, so it should
begin to be available for many users anyways. We can just add a note
that the macos package is
t;> The page looks a little strange in Fedora's Firefox, although it looks
> >> fine in chrome.
> >>
> >> I attached a screenshot showing how part of the text is chopped off. I
> >> hesitate to write a bug for that because it may just be somethin
The patches look fin for me.
I suggest you add the [PATCH] tag to your email title next time.
Den lør. 21. jul. 2018 kl. 16.21 skrev Aimylios :
>
> Hi!
>
> While trying to build KiCad for Fedora 28 I discovered some minor
> problems in the main CMakeLists.txt file. Patches attached.
>
> Best
be one of the most noticeable improvements in the v5 release.
> >
> > Cheers,
> >
> > Wayne
> >
> > On 07/19/2018 06:51 PM, Nick Østergaard wrote:
> >> Awesome, thanks for the update!
> >> Den fre. 20. jul. 2018 kl. 00.48 skrev Rene Pöschl :
&
Awesome, thanks for the update!
Den fre. 20. jul. 2018 kl. 00.48 skrev Rene Pöschl :
>
> The library repos should now all be tagged. (Github had some server
> problems so it all took quite some time. I hope nothing got damaged
> because of that.)
>
> On 19/07/18 10:49, Nic
it if possible.
Nick
Den tor. 19. jul. 2018 kl. 10.49 skrev Nick Østergaard :
>
> As the installer package everything we can not make a proper 5.0.0
> stable before it has been tagged.
> Den tor. 19. jul. 2018 kl. 10.21 skrev Maciej Sumiński
> :
> >
> > Hi Simon,
>
As the installer package everything we can not make a proper 5.0.0
stable before it has been tagged.
Den tor. 19. jul. 2018 kl. 10.21 skrev Maciej Sumiński
:
>
> Hi Simon,
>
> The installer works well, no warnings observed here. Do you think you
> could create one for 5.0.0 stable and upload it to
This sounds good. Thank you.
Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl :
>
> On 18/07/18 19:59, Carsten Schoenert wrote:
> > Am 18.07.18 um 19:55 schrieb Rene Pöschl:
> >>> I'm traveling the whole Saturday and Sunday to Debian DebCamp and
> >>> DebConf in Taiwan and working on packaging
Den ons. 18. jul. 2018 kl. 19.50 skrev Carsten Schoenert
:
>
> Hi,
>
> Am 18.07.18 um 15:00 schrieb Marco Ciampa:
> >> wouldn't it have been better to pull first all outstanding pull request
> >> that are for the version 5.0.0 nonetheless?
> >
> > Whenever I see a pull request that should be
I am away from monday, so no worries.
ons. 18. jul. 2018 16.27 skrev Wayne Stambaugh :
> Nick,
>
> Please let me know if you can't get around to tagging the i18n and doc
> repos. I can tag them on Friday if need be.
>
> Cheers,
>
> Wayne
>
> On 7/18/2018 10:23 AM
:
>
> Sorry about that. I missed the restructure info. I think I covered
> most of the changes in my repo. I will try to get my changes pushed
> tonight so I can get some feedback before the official release announcement.
>
> On 7/18/2018 10:13 AM, Nick Østergaard wrote:
>
ontent/blog/release-5.0.0.adoc
>
> On 7/18/2018 10:01 AM, Nick Østergaard wrote:
> > Wayne,
> >
> > If you have a draft ready for the release announcement, please create
> > a pull request with it as a draft or push it as a draft, in case we
> > would
Hi
I think having a one to one mapping with branches for the i18n repo is
fine, and the i18n is highly dependent on the kicad src. But for the
doc repo, I don't think that is needed, it is better to have as few
branches here as possible, as the docs are only a meta description of
kicad and not
Wayne,
If you have a draft ready for the release announcement, please create
a pull request with it as a draft or push it as a draft, in case we
would like to add more info. This to avoid anyone else in attempting
to write it.
Nick
Den ons. 18. jul. 2018 kl. 14.41 skrev Wayne Stambaugh :
>
>
Why does this need to be so complicated?
I think we could just rename the kicad config folder created and
searched by kicad from "kicad" to "kicad5" and be happy in the 5.x
branches.
Den man. 16. jul. 2018 kl. 15.11 skrev Bob Gustafson :
>
> There is a tool which allows developers to quickly
Can you edit anything on them? Can you provide a screenshot of the
preferences dialog?
søn. 15. jul. 2018 23.15 skrev Eeli Kaikkonen :
>
>
> su 15. heinäk. 2018 klo 14.39 Jeff Young (j...@rokeby.ie) kirjoitti:
>
>> I renamed my 6.0 branch to 5.1, since most of what it contains goes there.
>>
>>
I guess Jeff's reasoning is to stabilize it a bit before braching. We all
know that changing the dialogs often leads to cross platform issues. But
either way is fine for me.
lør. 14. jul. 2018 01.59 skrev Wayne Stambaugh :
> That would prevent us from adding new features such as the new
FWIW The documentation does not use markdown syntax, but asciidoc.
Den fre. 13. jul. 2018 kl. 23.52 skrev Wayne Stambaugh :
>
> If the wxHtml widget would support markdown that would work but I don't
> think that is the case. I prefer converting it to markdown and moving
> it into the Eeschema
I don't think so, I guess we still want some time to give translators a chance.
Den fre. 13. jul. 2018 kl. 23.24 skrev Adam Wolf
:
>
> Resending from proper email address...
>
> On Fri, Jul 13, 2018, 4:23 PM Adam Wolf wrote:
>>
>> Good work, Wayne, and good work, team!
>>
>> Are you thinking the
frame.
Are you sure you don't have some local changes and is in a merge state
such that you are not actually checked out to those commits.
Den fre. 13. jul. 2018 kl. 10.02 skrev Nick Østergaard :
>
> I guess some patches were just pushed which were not verified to
> build. In the mean tim
I guess some patches were just pushed which were not verified to
build. In the mean time you can checkout any of these commits if you
want to test (take the bottom one).
https://jenkins.simonrichter.eu:8443/job/windows-kicad-msys2-evaluate/54/artifact/build-report.txt
Den fre. 13. jul. 2018 kl.
For windows the installer should also be in good nick. No pun intended.
There are some minor things that I would like to do, but they are by
no means a blocker for a release.
Nick
Den ons. 11. jul. 2018 kl. 21.35 skrev Adam Wolf
:
>
> MacOS installer is ready.
>
> Adam
> On Wed, Jul 11, 2018 at
The docs are not hosted there it is on
http://docs.kicad-pcb.org/master/
The dev docs are also still there.
ons. 11. jul. 2018 19.11 skrev Wayne Stambaugh :
> I just went to http://darine.hogyros.de:8080/job/any-kicad-doc-head/ and
> I cannot load the web page. I wanted to take a look at my
The docs are not hosted there it is on
http://docs.kicad-pcb.org/master/
The dev docs are also still there.
ons. 11. jul. 2018 19.11 skrev Wayne Stambaugh :
> I just went to http://darine.hogyros.de:8080/job/any-kicad-doc-head/ and
> I cannot load the web page. I wanted to take a look at my
And another i18n change in common/tool/common_tools.cpp
Den søn. 8. jul. 2018 kl. 14.12 skrev :
> From: Carsten Schoenert
>
> Hi,
>
> here again a small patch set for fixing up small grammar typos found by
> the Debian QS tool Lintian that should go into before the final release
> of 5.0.0.
>
>
I created a ticket on launchpad in
https://bugs.launchpad.net/kicad/+bug/1780601
I have target it to the 5.0.0 milestone such that we can make sure we
discuss this in time.
Den søn. 8. jul. 2018 kl. 06.19 skrev Adam Wolf <
adamw...@feelslikeburning.com>:
> Let's postpone this discussion maybe
Thank you.
Den søn. 8. jul. 2018 kl. 05.54 skrev Mark Roszko :
> Rejoice, the windows installer now setups file associations, icons and
> friendly names for kicad files.
>
> https://i.imgur.com/EcgnKmz.png
>
> I hope .sch and .pro get renamed to .kicad_sch and .kicad_pro in v6
> To avoid
I have tested this on windows. I don't know if it is any problem on other
platform, I would not expect it to be.
Den søn. 8. jul. 2018 kl. 06.18 skrev Константин Барановский <
baranovskiykonstan...@gmail.com>:
> The Tkinter module is the standard Python interface to the Tk GUI toolkit.
> Inside
Hi
I guess we could add it to the qa target somehow? What I don't
particularyly like with this patch is that executing "make test" does not
check for dependency changes.
Back to the status about qa_geometry... it did pass a long time ago, doing
a bit of git bisect points at this commit as the
; > Is there a tarball of the tagged docs somewhere?
> > >
> > > Adam
> > >
> > > On Wed, Jul 4, 2018, 7:14 AM Steven A. Falco
> wrote:
> > >>
> > >> Perfect! Thanks.
> > >>
> > >> Steve
> >
kicad-doc and kicad-i18n is also tagged
søn. 1. jul. 2018 00.34 skrev Rene Pöschl :
> template repo is now tagged (sorry forgot about that one)
>
> On 30/06/18 23:56, Steven A. Falco wrote:
> > Thank you!
> >
> > There are three repos not yet tagged with rc3 on github - two are
> probably
at
> hudson.model.AbstractProject.checkout(AbstractProject.java:1208)
> at
> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
> at
> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
>
No, this has not been disabled on purpose. I noticed this too, but I have
also noticed that I actually works, the mailing list is receiving it, but I
go not see it in my gmail inbox either.
https://lists.launchpad.net/kicad-developers/msg36340.html
So because of this I stopped to look for issues
I have put the upated image live now, and it seems to work. I will try to
revert the removal of the macros.
Den tor. 28. jun. 2018 kl. 23.21 skrev Nick Østergaard :
> Hi Seth
>
> Ok, thank you for your investigation. I will update the docker image to
> bionic which uses 0.52 of po
Hi Seth
Ok, thank you for your investigation. I will update the docker image to
bionic which uses 0.52 of po4a.
Nick
Den tor. 28. jun. 2018 kl. 23.05 skrev Seth Hillbrand <
seth.hillbr...@gmail.com>:
> Bother. po4a fixed this back in 2016 (
>
Hello Seth
I have created the following milestone names:
5.1.0
This is for fixes that are backportable from master, it could be string
fixes and minor features.
5.0.1
Post release fixes that does not involve string changes.
Att. Wayne, I would like you to say this is ok, or if we should use
logo and keep
>> > the title as it is?
>> >
>> > Cheers,
>> >
>> > John
>> >
>> > On Wed, Jun 13, 2018 at 11:18 PM, Wayne Stambaugh > > <mailto:stambau...@gmail.com>> wrote:
>> >
>> > I agree. The doub
Thank you that is good news.
Do you know if it also resolves the issues mentioned on
https://bugzilla.redhat.com/show_bug.cgi?id=1440904#c3
I was made aware of this from
https://github.com/KiCad/fedora-packaging/issues/7#issuecomment-397015599
2018-06-12 22:44 GMT+02:00 Holger Vogt :
> Yes,
@Seth, ok I didnt't notice it was not for the PPA. Ubuntu maintainers
need to address this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767652
Title:
kicad on ubuntu mate 18.04 cursor ghosting
elative to main binary or bundle location.
>
>
> Regards,
> Bernhard
>
>
> On 14. Jun 2018, at 08:51, Nick Østergaard wrote:
>
> It seems a bit strange to be that relative paths like that has to be used,
> can't some cmake install prefix path be used wheni is a bundle?
It seems a bit strange to be that relative paths like that has to be used,
can't some cmake install prefix path be used wheni is a bundle? Is this
also how it is done for other parts of kicad?
2018-06-13 4:39 GMT+02:00 Adam Wolf :
> Hi folks!
>
> This patch is meant to fix a crash Seth found
The normal build job is up again.
2018-06-12 16:54 GMT+02:00 Marco Ciampa :
> On Tue, Jun 12, 2018 at 10:31:55AM +0200, Nick Østergaard wrote:
> > tir. 12. jun. 2018 09.28 skrev Marco Ciampa :
> >
> > > Hi folks,
> > > I would like to know better the
Maybe we need to remove the word KiCad from the title, as it essentially
reads "[KiCad] KiCad Pcbnew Python Scripting"
2018-06-13 21:12 GMT+02:00 John Beard :
> Sorry, I had a line commented in a local commit to avoid a costly re-build
> of the docstrings when I didn't need them to be (the
code. All this can (and should) be transplanted onto a new "stable" Python
> interface in future.
>
> Cheers,
>
> John
>
> On Tue, Jun 12, 2018 at 2:47 PM, Nick Østergaard
> wrote:
>
>> I am not sure if this will slightly derail this patch's topic. Sor
Python doc generation if
> that's an acceptable way to present it.
>
> Cheers,
>
> John
>
> On Tue, Jun 12, 2018 at 2:11 PM, Nick Østergaard
> wrote:
>
>> We already have doxygen generation for the python API, although people
>> say that it is easier to read
We already have doxygen generation for the python API, although people say
that it is easier to read the C++ one. It is generated with
the doxygen-python make target. See
http://docs.kicad-pcb.org/doxygen-python/
Does the additions in 0002 add to the normal python docs?
2018-06-12 15:07
I think this would be ok as it does not change anything from the user even
if the translation is not updated. But I am not really a translator, so
there might be some subtle thing I have missed.
2018-06-12 5:28 GMT+02:00 Seth Hillbrand :
> Hi Devs-
>
> We're in string freeze but I've run across
tir. 12. jun. 2018 09.28 skrev Marco Ciampa :
> Hi folks,
> I would like to know better the organization of the build process
> (Continuous Integration) for the doc files.
>
> What I would like to know precisely is:
>
> - who is in charge to run the machines that build the docs
>
Ajo, but I
It looks like loose text strings in symbols are not transformed correctly
in the tom-eeschema-gal branch I just tested. See attached image.
2018-06-04 22:55 GMT+02:00 Nick Østergaard :
> Ok, sorry, I see Eeli also saw that and you intend to fix it later. I will
> stay with make ee
Ok, sorry, I see Eeli also saw that and you intend to fix it later. I will
stay with make eeschema.
2018-06-04 22:53 GMT+02:00 Nick Østergaard :
> Hi Tomasz,
>
> the build failed for me with:
> [ 54%] Linking CXX shared module _cvpcb.kiface
> ../common/libcommon.a(block
Hi Tomasz,
the build failed for me with:
[ 54%] Linking CXX shared module _cvpcb.kiface
../common/libcommon.a(block_commande.cpp.o): In function
`BLOCK_SELECTOR::InitData(DRAW_PANEL_BASE*, wxPoint const&)':
/home/nickoe/kicad-source-mirror/common/block_commande.cpp:150: undefined
reference to
** Changed in: kicad (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767652
Title:
kicad on ubuntu mate 18.04 cursor ghosting (eeshcema), pcb design
It looks like it works as intended, but I don't think the naming is that
good. Maybe it might be better to call it KICAD_RUNTIME_DIR analogous to
XDG terminology used elsewhere and nearby...
If it is called KICAD_CACHE_HOME one would think that this would control
the location of the 3d cache too,
I figured I just made it since no 5.0.0 was made.
I agree with Simon that we are likely to have an rc3. We can just rename
the milestone if we change our mind. Afterall it does not cost us anything.
2018-05-28 14:25 GMT+02:00 Wayne Stambaugh :
> On 05/26/2018 04:13 PM,
I created a 5.0.0-rc3 milestone.
2018-05-26 1:30 GMT+02:00 Seth Hillbrand :
> Now that RC2 is released, can we get a new target in the bug tracker for
> things that should be fixed prior to v5 release? Currently, we only have
> v6 as a target
>
> Thanks-
> Seth
>
>
>
Is this the one from the Browse Libraries... from the fp-lib-table dialog?
2018-05-25 11:10 GMT+02:00 Maciej Sumiński :
> Thank you for the feedback. I have fixed the reported issues (disabled
> "Show Hidden", made the dialog resizable and ${KIRPRJMOD} substitution)
>
I think 80% is too high. Actually I think we should just ship the
translations that has had any contribution within the string freeze period.
It could be an incitement for a random contributor to see that some strings
are actually translated. And then hopefully most of the work they may do
can be
Hi Seth,
I have sometimes sent out an email directly to some of the "usual" and
recent translators for languages that were missing updates. I have been
playing with the thought of using something like transifex for the
translations, but I decided not to use that because I can not see how it
can
A bug related to some recent changes is
https://bugs.launchpad.net/kicad/+bug/1769143
It sounds simple, but I don't know if it is.
2018-05-19 9:24 GMT+02:00 Andrey Kuznetsov :
> What about this bug for MacOS that makes it too frustrating to use
> eeschema?
>
> Basically, I
5/18/2018 12:02 PM, Nick Østergaard wrote:
> > For wxpython, we "just" need to upgrade to phoenix, which supports gtk3.
>
> Has this been verified on all platforms? I thought there were issues
> with our use of swig and the use of sip by the phoenix project. I
For wxpython, we "just" need to upgrade to phoenix, which supports gtk3.
2018-05-18 18:01 GMT+02:00 Wayne Stambaugh :
> Hi Tom,
>
>
> On 05/18/2018 11:51 AM, Tomasz Wlostowski wrote:
>
>> On 18/05/18 17:38, Wayne Stambaugh wrote:
>>
>>> As we approach the v5 stable release,
ment your suggestions and give people another few days to test
> if they're interested in this topic before merging.
>
> Best-
> Seth
>
> 2018-03-18 15:57 GMT-07:00 Nick Østergaard <oe.n...@gmail.com>:
>
>> Hi Seth,
>>
>> I tried to test your patch. It bas
** Changed in: ubuntu
Status: Confirmed => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1461698
Title:
Cross-hair pointer leaves a trace on screen in eeschema
To manage
See the unittests in the qa folder. Thay are executed by the build job also.
ons. 9. maj 2018 15.25 skrev miles mccoo :
> Thank you, Jeff, for taking the time to look at my patch.
>
> attached is a new version of the patch. I've changed a couple things:
>
>- fixed the curly
I vote for accepting XDG_CONFIG_HOME on all platforms for consistency.
After all this is an advanced configuration feature and should not be
touched by the normal user.
I don't know why the patch was made so complex initially.
2018-05-07 15:54 GMT+02:00 Adam Wolf :
Remember that a ascii freindly version can be used in the source and then
we can use the unicode char in the translations. This is the reason there
is also a po file for english.
2018-05-04 17:59 GMT+02:00 jp charras :
>
> Message transféré
> Sujet : Re:
401 - 500 of 1927 matches
Mail list logo