Hi,
Another icon! (Groan)
This one is the update PCB from Schematic icon. Currently, this
re-uses the "Import PCB board file" icon from the file menu.
I think this is a bit non-obvious, because the action isn't an
"import", it's an update, and the icon makes no reference to the
schematic nature
Thank you all! It was the #1 issue with the 5.0 release.
Cheers,
Orson
On 07/25/2018 08:57 PM, Mark Roszko wrote:
> Appears Simon has handled it, the downloads are updated.
>
> I installed it and it no longer asserts.
>
> On Wed, Jul 25, 2018 at 1:20 PM Wayne Stambaugh wrote:
>>
>> On
Nice work team!
On Wed, Jul 25, 2018, 1:57 PM Mark Roszko wrote:
> Appears Simon has handled it, the downloads are updated.
>
> I installed it and it no longer asserts.
>
> On Wed, Jul 25, 2018 at 1:20 PM Wayne Stambaugh
> wrote:
> >
> > On 7/25/2018 12:54 PM, Mark Roszko wrote:
> > > *
Appears Simon has handled it, the downloads are updated.
I installed it and it no longer asserts.
On Wed, Jul 25, 2018 at 1:20 PM Wayne Stambaugh wrote:
>
> On 7/25/2018 12:54 PM, Mark Roszko wrote:
> > * Simon's pull request.
> >
> > https://github.com/KiCad/kicad-winbuilder/pull/74
>
> Nick
Hi,
On 25.07.2018 18:00, Wayne Stambaugh wrote:
> The 5.1 branch will go away. I just haven't gotten around to it.
Even better.
Simon
signature.asc
Description: OpenPGP digital signature
___
Mailing list:
On 7/25/2018 12:54 PM, Mark Roszko wrote:
> * Simon's pull request.
>
> https://github.com/KiCad/kicad-winbuilder/pull/74
Nick must have given me admin permissions so I merged Simon's pull
request. The new release packages should be available shortly. Do I
need to do anything to make sure the
Hi,
On 25.07.2018 18:18, Wayne Stambaugh wrote:
> I guess we will have to wait until Nick returns from vacation to get
> this resolved.
I just pointed Jenkins at my fork, but that's bad style, basically.
Simon
signature.asc
Description: OpenPGP digital signature
* Simon's pull request.
https://github.com/KiCad/kicad-winbuilder/pull/74
On Wed, Jul 25, 2018 at 12:33 PM Wayne Stambaugh wrote:
>
> I believe have github admin permissions at the org level. Please post
> the link to Mark's pull request and I will see if I can merge it.
>
> On 7/25/2018 12:29
I believe have github admin permissions at the org level. Please post
the link to Mark's pull request and I will see if I can merge it.
On 7/25/2018 12:29 PM, Adam Wolf wrote:
> Does anyone else have admin permissions at the org level?
>
> On Wed, Jul 25, 2018, 11:19 AM Wayne Stambaugh
Does anyone else have admin permissions at the org level?
On Wed, Jul 25, 2018, 11:19 AM Wayne Stambaugh wrote:
> On 7/25/2018 11:15 AM, Mark Roszko wrote:
> > @Wayne, The hold up on Windows was that Nick went on vacation
> > basically the day after posting the first 5.0 build. So bad timing.>
Fabrizio,
On 7/25/2018 9:05 AM, Fabrizio Tappero wrote:
> Hi Guys,
> I just wold like to remind you that if you decide to personalize kicad
> icons, kicad will end up with a lot of icons to maintain.
>
> Currently kicad is using really a lot of icons and few years ago we
> tried to simplified
On 7/25/2018 11:15 AM, Mark Roszko wrote:
> @Wayne, The hold up on Windows was that Nick went on vacation
> basically the day after posting the first 5.0 build. So bad timing.>
>
>> I've changed it to Release for the time being (but someone still needs to
>> accept my pull request in GitHub)
>
I thought I made it clear what the current branches were for but I will
officially reiterate my previous comments.
The development branch is currently only open for 5.1 development. This
includes 5.0 bug fixes, Jeff's UI refactoring, and the GTK3 fixes. No
new features will be allowed until 5.1
Hi,
The pixel alignment of the op-amp icons looks a bit fuzzy compared to
the other newer icons. These are not the only misaligned icons, but
they are a very prominent set of them.
The problem is that both:
1) The lines are not on the pixel grid
2) The lines are not a whole number of pixels
@Wayne, The hold up on Windows was that Nick went on vacation
basically the day after posting the first 5.0 build. So bad timing.
>I've changed it to Release for the time being (but someone still needs to
>accept my pull request in GitHub)
Unforunately Nick is the only one with privs on the
Hi Fabrizio,
I think we’re moving in both directions at once. Where there is only a single
context, I favour the generic icons (for instance, we’re moving to using a
generic save icon in contexts where that isn’t ambiguous). However, where
multiple contexts are visible at once (such as in
Thanks, John!
> On 25 Jul 2018, at 11:44, John Beard wrote:
>
> Hi Jeff,
>
> Sure thing! Here they are.
>
> I have modified part_properties (patch 1) and create field_properties
> and used in the menu and toolbar (patch 2).
>
> Attached are the PNGs for reference.
>
> Cheers,
>
> John
>
>
On Wed, Jul 25, 2018 at 8:45 AM, Maciej Sumiński
wrote:
>
> I would not mind adding more hotkeys, I think the primary reason is that
> not every action is executed often enough to justify a hotkey. Even with
> the current configuration it might be challenging to find a free hotkey
> for an
Hi Fabrizio,
I agree with the principle, and I am happy that we have lost the huge
number of item-specific icons in GAL menus compared to Legacy.
To be honest, I don't care what the metaphor for "board properties"
is. However, I think it is unhelpful to use a generic "properties"
icon in the
Hi,
On 25.07.2018 14:16, Wayne Stambaugh wrote:
> We should have created a release build of the stable version. I'm fine
> with nightly builds having debugging information. Stable releases
> should not have debug info.
These are built as RelWithDebInfo, and the debug information is stripped
Hi,
On 25.07.2018 14:25, Wayne Stambaugh wrote:
> It seems to me that 5.1.0-dev would sort before 5.1.0-rc1 or am I
> missing something?
We already have tricks in place to sort RC before the release (without
suffix), which is annoying as is but an established convention.
IMO, any tag that
Hi,
On 24.07.2018 09:01, Maciej Sumiński wrote:
> At the moment the master branch contains all commits from 5.1 and a few
> more. It might be the right moment to drop 5.1 branch.
As it should be. Well, ideally commits on 5.1 should be cherry-picked
from master by the 5.1 release manager.
Do we
(Marek and I did pull the macOS builds, and I regenerated it as
Release and got everything all fixed up on the website.)
On Wed, Jul 25, 2018 at 7:31 AM Wayne Stambaugh wrote:
>
> We should have created a release build of the stable version. I'm fine
> with nightly builds having debugging
Dates do not convey useful branch information which is important from a
developer point of view.
It seems to me that 5.1.0-dev would sort before 5.1.0-rc1 or am I
missing something? Would one of our package devs care to comment. If
this sorts properly, I will change the kicad version and repo
We should have created a release build of the stable version. I'm fine
with nightly builds having debugging information. Stable releases
should not have debug info.
On 7/25/2018 8:10 AM, Jakub Kozdon wrote:
> There are probably in http://downloads.kicad-pcb.org/windows/testing/
> instead of
There are probably in http://downloads.kicad-pcb.org/windows/testing/
instead of stable.
Dne 25.7.2018 v 13:51 Wayne Stambaugh napsal(a):
I thought we created a new windows release build to prevent the
assertions. Did that not happen?
On 7/25/2018 7:01 AM, Andrew Lutsenko wrote:
Were the
Am 25.07.18 um 17:40 schrieb Maciej Sumiński:
> Nobody forbids working on new features in separate branches that we will
> start merging once 5.1 is released and 6.0 development cycle starts. I
> have already started a few branches for v6 features, but they need to
> wait now.
That's what I mean,
I thought we created a new windows release build to prevent the
assertions. Did that not happen?
On 7/25/2018 7:01 AM, Andrew Lutsenko wrote:
> Were the windows builds ever fixed?
> I downloaded 5.0 today and get a wxWidgets assert simply from clicking
> on tools menu in Pcbnew.
>
Were the windows builds ever fixed?
I downloaded 5.0 today and get a wxWidgets assert simply from clicking on
tools menu in Pcbnew.
[image: kicadassert.png]
On Mon, Jul 23, 2018 at 6:34 AM Wayne Stambaugh
wrote:
> I'm fine with creating a packaging document. We could add it to the
>
Hi Jeff,
Sure thing! Here they are.
I have modified part_properties (patch 1) and create field_properties
and used in the menu and toolbar (patch 2).
Attached are the PNGs for reference.
Cheers,
John
On Tue, Jul 24, 2018 at 8:35 PM, Jeff Young wrote:
> Hi John,
>
> When you get a chance
On 07/25/2018 11:23 AM, Carsten Schoenert wrote:
> Hello Orson,
>
> Am 25.07.18 um 15:53 schrieb Maciej Sumiński:
> ...
>> It has been discussed in this thread already, but I will repeat: the
>> main problem now is that we need to apply patches to both master and
>> 5.1.
>
> thanks for
Hello Orson,
Am 25.07.18 um 15:53 schrieb Maciej Sumiński:
...
> It has been discussed in this thread already, but I will repeat: the
> main problem now is that we need to apply patches to both master and
> 5.1.
thanks for clarifying (probably again).
The question will come again and again,
On 07/25/2018 04:28 AM, Carsten Schoenert wrote:
> Am 24.07.18 um 15:01 schrieb Maciej Sumiński:
>> At the moment the master branch contains all commits from 5.1 and a few
>> more. It might be the right moment to drop 5.1 branch.
>
> This depends on the achievements which are desired or wanted in
Hi John,
On 07/24/2018 07:21 PM, John Beard wrote:
> Hi,
>
> I have a few questions about hotkeys in GAL tools:
>
> 1) Is there are reason so many GAL tools don't get hotkeys?
>
> Very many TOOL_ACTIONS have a hotkey set to '0'. Most others that do
> have a hotkey have a LegacyHotkey
Why not just use the date at which the nightly was compiled?
So something like dev-snapshot--mm-dd_g23849572
This is sortable and it should confuse nobody.
On 24/07/18 23:58, Eeli Kaikkonen wrote:
ti 24. heinäk. 2018 klo 22.59 Wayne Stambaugh (stambau...@gmail.com
35 matches
Mail list logo
