On 2019-07-05 3:55 p.m., Jeff Young wrote:
No, thats just LaunchPad ???helping??? out. ??Heres a
bitmap of it
ok, thanks Jeff.
--
Cheers!
Kevin.
http://www.ve3syb.ca/ | "Nerds make the shiny things that
https://www.patreon.com/KevinCozens | distract the
3.1.x is essentially only available on the lesser-known distros and as
additional packages for OpenSUSE. Aside from that, most distros run
anything between 3.0.2 and 3.0.4. (see here:
https://repology.org/project/wxwidgets/versions).
-Ian
On Fri, Jul 5, 2019 at 7:52 PM Wayne Stambaugh wrote:
Wayne's comment about the wxWidgets version required for the patch reporter
reminded me about something I had read earlier about wxPython, specifically
wxPhoenix will be switching to wxWidgets 3.1.x as its backend (see here
https://github.com/wxWidgets/Phoenix/blob/master/CHANGES.rst) in its next
Hi Sylwester,
There is a minor problem with this patch. You can no longer copy the
contents of the netlist viewer window to the clipboard (a least on
linux) with your patch so I am reluctant to merge it because I'm sure
users will want to be able to copy and paste the generated netlist for
bug
Hi Wayne-
This shouldn't affect users, only developers. Once the binary is built,
there are no differences in requirements for running KiCad.
I would only push this to master and not 5.1, so that 5.1.3+ bug fixes
will still build for 14.04 (which was supported when 5.1 was released).
On 2019-07-05 2:05 p.m., Wayne Stambaugh wrote:
Looks good to me. If no one else objects, I see no reason not not to
merge it.
[snip]
On 2019-07-05 09:46, Jeff Young wrote:
On 5 Jul 2019, at 12:19, Jeff Young wrote:
(setup
(last_trace_width 0.25)
(trace_clearance 0.2)
No indenting to make
Hey Seth,
Sorry about the delay. I've been wrestling (and loosing) with restoring
a broken boot manager on my desktop after a bios update stepped all over
my uefi boot configuration (thank you HP). I would like to hold off on
C++14 for a while. I suspect there are users who prefer running
Tom,
On 7/4/19 8:54 AM, Tomasz Wlostowski wrote:
> On 01/07/2019 23:49, Nick Østergaard wrote:
>> Hello Tomasz
>>
>> Do you have any comments on the wxwidgets version?
>
> Hi Nick,
>
> I have 3.1.1 in my MSYS environment, probably manually built.
>
> We have two options:
> - ask MSYS folks to
Looks good to me. If no one else objects, I see no reason not not to
merge it.
Wayne
On 7/5/19 12:25 PM, Jeff Young wrote:
> Oops. Good catch.
>
>> On 5 Jul 2019, at 16:43, Seth Hillbrand wrote:
>>
>> Looks good to me. Thanks Jeff! The only thing that I didn't see was the
>> file version
Hi Thomas-
Sounds good. Can you add it to the bug tracker? Doubtful for v6 as we
have a lot on the agenda already but could be a good v7 project.
-Seth
On 2019-07-05 13:00, Thomas Pointhuber wrote:
On the long run, what about improving the fill algorithm to be able to
only update affected
Hi,
On Fri, Jul 05, 2019 at 06:24:45PM +0200, Tomasz Wlostowski wrote:
> > I can't test the Windows functionality but this doesn't appear to break
> > anything on Linux.
> I'm ok with Simon's patches. Can give them a try on MSVC, but I'm pretty
> confident they will work already.
These are
On the long run, what about improving the fill algorithm to be able to
only update affected regions?
e.g. As long as an update cannot split the zone and the update has no
overlap with other zones it should be possible to only recalculate parts
of the zone fill and ignoring the rest.
I know this
Oops. Good catch.
> On 5 Jul 2019, at 16:43, Seth Hillbrand wrote:
>
> Looks good to me. Thanks Jeff! The only thing that I didn't see was the
> file version bump.
>
> Let's see if anyone else want to weigh in after this thread :)
>
> -Seth
>
> On 2019-07-05 09:46, Jeff Young wrote:
>>
On 05/07/2019 18:21, Seth Hillbrand wrote:
> I can't test the Windows functionality but this doesn't appear to break
> anything on Linux.
>
I'm ok with Simon's patches. Can give them a try on MSVC, but I'm pretty
confident they will work already.
@Simon: Now that we'll be supporting MSVC,
I can't test the Windows functionality but this doesn't appear to break
anything on Linux.
-Seth
On 2019-07-04 12:05, Simon Richter wrote:
Hi,
another attempt at getting the MSVC patchset merged. :)
The mails with the patches are for commenting, this branch should
probably
be merged from
On 7/5/19 11:50 AM, Seth Hillbrand wrote:
> On 2019-07-05 07:46, Jeff Young wrote:
>> 1) If I move a footprint which is over a zone, the zone fill becomes
>> stale.
>>
>> 2) If I move a zone which has footprints over it, the zone is re-filled.
>>
>> 3) If I edit the points of a zone and then
On 2019-07-05 07:46, Jeff Young wrote:
1) If I move a footprint which is over a zone, the zone fill becomes
stale.
2) If I move a zone which has footprints over it, the zone is
re-filled.
3) If I edit the points of a zone and then de-select it, the zone is
re-filled.
Item (2) turns out
Looks good to me. Thanks Jeff! The only thing that I didn't see was
the file version bump.
Let's see if anyone else want to weigh in after this thread :)
-Seth
On 2019-07-05 09:46, Jeff Young wrote:
Git is alive again:
Git is alive again:
https://git.launchpad.net/~jeyjey/kicad/commit/?id=602bd05291677de97e50e84bef7a3510ff80be23
> On 5 Jul 2019, at 12:19, Jeff Young wrote:
>
> (setup
> (last_trace_width 0.25)
> (trace_clearance 0.2)
> (zone_clearance 0.508)
> (zone_45_only no)
>
Hi Alex,
Yes, MessageTextFromValue() is what you want. (There’s also StringFromValue(),
but that produces very exact numbers to prevent round-off errors so they’re
much less human-readable.)
Use ShowModal(), not ShowQuasiModal(). ShowQuasiModal() is a bit of a hack for
modal dialogs which
1) If I move a footprint which is over a zone, the zone fill becomes stale.
2) If I move a zone which has footprints over it, the zone is re-filled.
3) If I edit the points of a zone and then de-select it, the zone is re-filled.
Item (2) turns out to be a side effect of the PointEditor getting
(setup
(last_trace_width 0.25)
(trace_clearance 0.2)
(zone_clearance 0.508)
(zone_45_only no)
(trace_min 0.2)
(via_size 0.8)
(via_drill 0.4)
(via_min_size 0.4)
(via_min_drill 0.3)
(user_diff_pair 1 2 3)
(uvia_size 0.3)
(uvia_drill 0.1)
Hi All!
Jeff,
I don't think, it should have it's own tool either ))) But I couldn't realize
by myself, where to put it. No problems, I will rename to PCB_INSPECTION_TOOL.
Ian,
1) I will look at that. To be honest, I don't know much about imperial units )
But I think that's some parameter in
Hi!
Sorry for delay in my answer, I have 2 small kids and sometimes there's no time
for everything.
Do I answer just to kicad-developers@lists.launchpad.net , right?
Mario, Shuklin is my surname. Name is Alex)))
I will try to do what you are asking for. Do you mean "count" components, not
list
24 matches
Mail list logo
