Le 12/08/2019 à 21:54, Wayne Stambaugh a écrit :
> Sounds like a plan. If there are not bug reports against this over the
> next month, I'll will cherry-pick it into 5.1.
>
> Wayne
I am not sure this issue exists in 5.1.
AFAIK it comes from moving code from our DLIST to std::deque, only in
mast
Hi folks!
5.1.4 is up for macOS. It's in two versions, like last time. 10.12
and 10.13 use
https://kicad-downloads.s3.cern.ch/osx/stable/kicad-unified-5.1.4-0.dmg,
and 10.14 uses
https://kicad-downloads.s3.cern.ch/osx/stable/kicad-unified-5.1.4-0-10_14.dmg
The second file is not yet uploaded
Howdy Wayne,
no worries. Thanks for the heads up. I'm not surprised at all since this
only makes sense to have.
In the meantime I'll keep it up if viable as a local patch just for
fun-kickers.
Is that feature already progressing? If so, which tag?
Cheers
Johannes
On 13/08/19 7:27 AM, Wayne St
I’m not sure what we’re buying with the wxUpdateUIEvents then. Context menus
will still need to run the existing Evaluate() stuff (for visibility and for
the highlight hacks), at which point it might as well do the enabling/checking
too. And menu-bar menus will also still have to run menu dispa
Jeff,
I was thinking we would only move the update for the enable and check
attributes to the wxUpdateUIEvent mechanism and leave the visibility to the
conditional menu to deal with in its Evaluate() function as it currently
does. There is no way to get wxWidgets to hide items for us in menus (and
Hi Ian,
It sounds promising, but there are some potential pitfalls. wxWidgets only
supports two bits: enabled and checked. CONDITIONAL_MENU supports 2-1/2: the
enabled flag means visible if the is_context_menu flag is set. This is
probably a subtlety that does us no good: it would be more di
Sounds like a plan. If there are not bug reports against this over the
next month, I'll will cherry-pick it into 5.1.
Wayne
On 8/12/19 3:47 PM, Ian McInerney wrote:
> Wayne, lets let this settle in master for a while to make sure that no
> issues due to object lifetime surface.
>
> -Ian
>
> On
Wayne, lets let this settle in master for a while to make sure that no
issues due to object lifetime surface.
-Ian
On Mon, Aug 12, 2019 at 9:20 PM Wayne Stambaugh
wrote:
> Ian,
>
> I merged your patch. I'm guessing this should be cherry-picked into the
> 5.1 branch.
>
> Thanks,
>
> Wayne
>
> O
Following on from the discussion in this merge request (
https://code.launchpad.net/~imcinerney/kicad/+git/kicad/+merge/371156), I
thought a little about if the current framework could be adapted to use the
wxUpdateUIEvent handlers to do the synchronization, and I think it can be.
Here is my thinki
Johannes,
Once the new schematic and symbol library file formats are complete, you
will be able orient pin number and name positions freely. This is
planned for version 6 which is currently under development so no changes
will be made to the existing file format to support this. Thank you for
of
Ian,
I merged your patch. I'm guessing this should be cherry-picked into the
5.1 branch.
Thanks,
Wayne
On 8/11/19 4:42 PM, Ian McInerney wrote:
> I was noticing there were some memory leaks inside the board/module
> classes that got somewhat extreme in some cases (I saw ~300MB leaked
> from op
What is the status of this patch?
Cheers,
Wayne
On 8/8/19 7:16 PM, Ian McInerney wrote:
> In the current framework, if more than one global actions share the same
> hotkey (even if they are not all active in the current tool manager),
> the dispatcher will only choose the final action (in what s
Adam,
Please ping the mailing list once you get this uploaded so I can get
everything released.
Thanks,
Wayne
On 8/12/2019 10:04 AM, Adam Wolf wrote:
> Working on this this morning. Thanks for your patience all.
>
> Adam
>
> On Mon, Aug 12, 2019 at 7:56 AM Wayne Stambaugh wrote:
>>
>> Ian,
Working on this this morning. Thanks for your patience all.
Adam
On Mon, Aug 12, 2019 at 7:56 AM Wayne Stambaugh wrote:
>
> Ian,
>
> Nice catch. I just pushed the fix.
>
> Thanks,
>
> Wayne
>
> On 8/12/2019 8:47 AM, Ian McInerney wrote:
> > Wayne,
> >
> > There seems to be a typo in the releas
Ian,
Nice catch. I just pushed the fix.
Thanks,
Wayne
On 8/12/2019 8:47 AM, Ian McInerney wrote:
> Wayne,
>
> There seems to be a typo in the release announcement (line 23), it
> references the 5.1.3 milestone page twice instead of 5.1.3 and 5.1.4.
>
> -Ian
>
> On Mon, Aug 12, 2019 at 2:39
Wayne,
There seems to be a typo in the release announcement (line 23), it
references the 5.1.3 milestone page twice instead of 5.1.3 and 5.1.4.
-Ian
On Mon, Aug 12, 2019 at 2:39 PM Wayne Stambaugh
wrote:
> I just installed 5.1.4_1 on windows 10 and everything seems to be
> working as expected.
I just installed 5.1.4_1 on windows 10 and everything seems to be
working as expected. I did not see the 5.1.4 macos package. I will
hold off updating the website download page and the release announcement
until that is ready. Thank you everyone for your efforts. Hopefully
the next stable relea
17 matches
Mail list logo
