Rebased branch pushed.
> On 27 Sep 2018, at 19:22, Jeff Young wrote:
>
> PS: By “push” I mean to my public repo, not to master. ;)
>
>> On 27 Sep 2018, at 19:18, Jeff Young > <mailto:j...@rokeby.ie>> wrote:
>>
>> I have re-based the GAL br
PS: By “push” I mean to my public repo, not to master. ;)
> On 27 Sep 2018, at 19:18, Jeff Young wrote:
>
> I have re-based the GAL branch on master. I’ll push once I’ve built it and
> shaken out any obvious issues.
>
> Cheers,
> Jeff.
>
>
>> On
I have re-based the GAL branch on master. I’ll push once I’ve built it and
shaken out any obvious issues.
Cheers,
Jeff.
> On 24 Sep 2018, at 23:13, Jeff Young wrote:
>
> Hi Tom,
>
> I’m happy to do it. Do I have your latest changes?
>
> Cheers,
> Jeff.
>
>
Hi Thomas,
When you say you can’t enter text into the filter, does the insertion point
show up there and just not the text, or can you not focus on it at all?
I only changed the list-item-padding for MSW, so if you’re still getting a
much-too-long list it looks like GTK wants a smaller padding
Argh. The dreaded SetColumnWidth() again. (It’s #defined to the new name for
it on OSX, but not on MSW.)
> On 27 Sep 2018, at 18:44, Thomas Pointhuber wrote:
>
> Hi Jeff,
>
> I like the idea, but it still has some problems on my system:
>
> * I cannot enter any text into the filter field
>
I had planned to get rid of another of our nanny items (“illegal” characters in
names). The plan was to escape these strings coming in from the UI, and
unescape them going out to the UI (or to canvas painting routines).
But I ran into a snag: we let you edit the FPID in the GUI, and that has
er
> amusing side effect.
>
> Maybe we should revert back to a stock dropdown and live without type
> ahead find until we move to a later version of wxwidgets.
>
> Cheers,
>
> Wayne
>
>
> On 9/27/2018 6:58 AM, Jeff Young wrote:
>> Hi guys,
>>
>&g
Hi guys,
Some wxWidgets facilities clearly aren’t working as advertised, so I’ve removed
them and simplified the code.
I’ve put in some defensive code for the second issue, but I don’t know if it
will work or not.
I’ve put in de-bouncing logic which I’m pretty sure will fix the third issue.
Hi Seth,
Fix pushed.
Cheers,
Jeff.
> On 26 Sep 2018, at 22:29, Seth Hillbrand wrote:
>
> Am Mi., 26. Sep. 2018 um 13:58 Uhr schrieb Jeff Young <mailto:j...@rokeby.ie>>:
> Hi JP,
>
> The main reason I don’t favour the 2-control solution is that you want to see
. ;)
One more re-write is up. This one turns the popup into a wxSTAY_ON_TOP
wxDialog and uses an EventFilter rather than its own eventLoop.
Cheers,
Jeff.
> On 26 Sep 2018, at 08:55, jp charras wrote:
>
> Le 25/09/2018 à 18:57, Jeff Young a écrit :
>> Thanks, JP. I’ve push
Thanks, JP. I’ve pushed another “fix”. It works on OSX, but then so did the
first one, so who knows.
Let me know how it works on Linux & MSW.
Cheers,
Jeff.
> On 25 Sep 2018, at 16:38, jp charras wrote:
>
> Le 25/09/2018 à 16:09, Jeff Young a écrit :
>> OK, so it looks
ote:
>
> This is how it looks:
> https://www.dropbox.com/s/fplbtsct41ycwoj/kicad%202018-09-25%2014-53-52.mov?dl=0
> Moving mouse does not change anything.
>
> Andrzej
>
>
> W dniu 2018-09-25 o 14:15, Jeff Young pisze:
>> Hi Andrzej,
>>
>> A couple of more
>
> Andrzej
>
> W dniu 2018-09-25 o 12:29, Jeff Young pisze:
>> Hi Andrzej,
>>
>> How recent is your code? Seth made some recent fixes to the Net Selector on
>> GTK, so let’s make sure you’ve got that code first.
>>
>> Neither Seth nor I have MSW
>
> net selector seems to no longer work on Windows and Linux.
> When I try to drop it down it just flickers and folds back up.
>
> Andrzej
>
> W dniu 2018-09-21 o 21:43, Jeff Young pisze:
>> I just pushed a new version of the net selector combobox. It’s a complete
&g
Hi Tom,
I’m happy to do it. Do I have your latest changes?
Cheers,
Jeff.
> On 24 Sep 2018, at 19:54, Tomasz Wlostowski wrote:
>
> On 24/09/18 20:07, Wayne Stambaugh wrote:
>> Hey Jeff,
>>
>> On 9/21/2018 9:49 AM, Jeff Young wrote:
>>> Hi Tom,
&
Imagine you commit something with the text “Work around stupid assert in XYZ”.
Git will format-patch this as “0001-Work-around-stupid-assert-in-XYZ.patch”.
Imagine that you now email it to Seth.
The filename, being too long, gets elipsized:
“0001-Work-around-stupid-ass…YZ.patch”
Gave me a
Patch pushed.
Cheers,
Jeff.
> On 22 Sep 2018, at 16:35, Maciej Suminski wrote:
>
> One more patch to fix off grid component placement after paste
> operation. Apart from that, the result is very impressive. Well done!
>
> Cheers,
> Orson
>
> On 9/19/18
Excellent news; thanks for doing this Seth!
Cheers,
Jeff.
> On 21 Sep 2018, at 20:53, Seth Hillbrand wrote:
>
> Hi All-
>
> I've just finalized the process of removing OpenMP from our codebase. See
> https://lists.launchpad.net/kicad-developers/msg34520.html
>
I just pushed a new version of the net selector combobox. It’s a complete
re-write using less wxStuff, and so hopefully won’t run into the same bugs.
It’s used in the Track Properties, Pad Properties and Global Edit Tracks and
Vias dialogs; if you get a chance to try it out I’d love to hear
Hi Tom,
Do you have additional fixes that are not in your branch of my repo?
If not, does it make sense for me to rebase it on master? (It would have to
become “truth” at that point, but you could clone back from it.)
Cheers,
Jeff.
___
Mailing
A couple of more commits are up (including backing out the polyline change).
> On 19 Sep 2018, at 19:27, jp charras wrote:
>
> Le 19/09/2018 à 13:01, Rene Pöschl a écrit :
>> On 19/09/2018 11:54, jp charras wrote:
>>> Le 19/09/2018 à 11:40, Rene Pöschl a écrit :
Ok i looked at the pot
OSX is double-buffered, so I wouldn’t notice the flicker even if it were
happening.
FWIW, I haven’t noticed it in profiling.
> On 19 Sep 2018, at 18:33, Wayne Stambaugh wrote:
>
> I've noticed recently (around v5 release) that the layer manager (at
> least on windows 10) looks like it's
Hi JP,
Do you think it’s worth checking the colours of the stroke and fill, or just
remove the change and require that the libraries get fixed?
(Why doesn’t the original issue show up with legacy? Maybe it is checking for
stroke == fill and then closing the polygons?)
Cheers,
Jeff.
Hi Wayne,
It’s certainly less necessary with the modern canvas (which has selection
highlighting), but I’m only speculating.
Cheers,
Jeff.
> On 19 Sep 2018, at 16:32, Wayne Stambaugh wrote:
>
> Does anyone know why we always disable the warp mouse pointer option in
> the find dialog when
The 74LS00 in my (admittedly dated) library aren’t filled. Are they in more
recent libraries?
(If so, we’ll need to back out my change as it will indeed affect them.)
___
Mailing list: https://launchpad.net/~kicad-developers
Post to :
Hi Wayne,
> On 18 Sep 2018, at 23:20, Wayne Stambaugh wrote:
>
> On 9/18/2018 7:20 AM, Jeff Young wrote:
>> When calculating obstacles we currently use the diff-pair gap as a
>> clearance between a diff-pair trace and a diff-pair pad.
>>
>> I’m pretty sure tha
ppened to work before by accident)?
>
> Cheers,
>
> John
> On Tue, Sep 18, 2018 at 12:35 AM Jeff Young wrote:
>>
>> There’s a setting for that (Always show crosshairs). You probably have it
>> on in Pcbnew/Display Options but not in Eeschema/Display Options.
&g
What’s the purpose of the: gwsTarget.FilterByOrientation( DIRECTION_45::ANG_STRAIGHT | DIRECTION_45::ANG_HALF_FULL, DIRECTION_45( dirV ) );line in DIFF_PAIR_PLACER::routeHead()?It keeps one from being able to route a diff-pair straight out from pads 42/43 in the attached PCB.(Note that even with
Got it. Thanks for the pointer.
> On 18 Sep 2018, at 13:32, Tomasz Wlostowski wrote:
>
> On 18/09/18 12:17, Jeff Young wrote:
>> When we check for collisions we do it first with the
>> worst-case-clearance value (m_maxClearance). I imagine this is so that
>> we can
When calculating obstacles we currently use the diff-pair gap as a clearance
between a diff-pair trace and a diff-pair pad.
I’m pretty sure that’s wrong. I’m just not sure how wrong.
I suspect the diff-pair gap shouldn’t be used as a clearance at all. It’s the
gap between the traces, not a
When we check for collisions we do it first with the worst-case-clearance value
(m_maxClearance). I imagine this is so that we can search the RTree uniformly.
But don’t we then have to check each collision for actual clearance violation
(ie: with the actual, not worst-case clearance values)?
t the cursor is no longer displayed when the select tool is
> active. This is different than the old canvas where the cursor always
> tracked the mouse point for all tools.
>
> Cheers,
>
> Wayne
>
> On 9/17/2018 7:21 PM, Jeff Young wrote:
>> I pushed fixes for sh
I pushed fixes for sheet pins and the cursor. (It also removes a bunch of
legacy grid and cursor colour stuff that is no longer needed.)
Cheers,
Jeff.
> On 17 Sep 2018, at 20:03, mdoes...@xs4all.nl wrote:
>
> I don't think I mailed the list, but also found another issue.
>
> I noticed the
JP’s latest has been pushed.
Cheers,
Jeff
> On 17 Sep 2018, at 11:41, jp charras wrote:
>
> Le 16/09/2018 à 23:37, Jeff Young a écrit :
>> I pushed JP’s commit and another that fixes up zoom & scroll issues
>> entering and leaving sheets.
>>
>> Cheers
I pushed JP’s commit and another that fixes up zoom & scroll issues entering
and leaving sheets.
Cheers,
Jeff.
> On 16 Sep 2018, at 16:03, jp charras wrote:
>
> Le 16/09/2018 à 15:08, Jeff Young a écrit :
>> I pushed a bunch of CLangTidy fixes and a fix for the grid co
I pushed a bunch of CLangTidy fixes and a fix for the grid colour.
Cheers,
Jeff.
> On 16 Sep 2018, at 08:40, mdoes...@xs4all.nl wrote:
>
> I've given the GAL version a test-drive. Here are some issues I noted.
> I guess most of it is because the black background was not tested before.
>
> 1.
I pushed JP’s changes.
(I’m pretty sure I fixed the add-item-undo issue yesterday.)
Cheers,
Jeff.
> On 15 Sep 2018, at 15:24, jp charras wrote:
>
> Le 14/09/2018 à 11:30, Jeff Young a écrit :
>> I pushed JP’s patches.
>>
>> What’s our plan for getting t
Hi Seth,
When you added the std::thread stuff for zone triangulation, did you search for
wxStrings which might be also be used outside the threads (globals, in
particular)?
We really should get rid of wxString everywhere that’s not GUI-related, but
that’s going to be a big job….
Cheers,
I pushed JP’s patches.
What’s our plan for getting this branch merged to master?
Cheers,
Jeff.
> On 14 Sep 2018, at 10:15, jp charras wrote:
>
> Le 12/09/2018 à 17:01, Jeff Young a écrit :
>> I just pushed a fix for a segfault while routing.
>> (https://bugs.lau
I just pushed a fix for a segfault while routing.
(https://bugs.launchpad.net/kicad/+bug/1792037)
Cheers,
Jeff.
> On 10 Sep 2018, at 14:47, Jeff Young wrote:
>
> Another commit set up. JP’s crash-on-startup, sheet pin refresh bugs,
> Clarify Selection minimisation, and O
Another commit set up. JP’s crash-on-startup, sheet pin refresh bugs, Clarify
Selection minimisation, and OpenGL canvas default on OSX.
> On 10 Sep 2018, at 14:23, Simon Richter wrote:
>
> Hi,
>
> On 10.09.2018 01:22, Jeff Young wrote:
>
>> New set of commits pu
New set of commits pushed.
Includes a bunch of fixes for refresh of various operations, fixes to dangling
symbol drawing for power symbols, removal of unused and redundant stuff, and
clamping of no-connect and junction sizes to a multiple of the wire size (along
with user-definable junction
Hi Jon,
That was definitely what I was looking for. Thanks for the pointer!
Cheers,
Jeff.
> On 7 Sep 2018, at 19:39, Jeff Young wrote:
>
> Hi Jon,
>
> That certainly looks like it. I’ll set some breakpoints once my tree builds
> again and see how I get on….
&
I’ve pushed JP’s 2 patches along with fixes to:
1) cross probing
2) the drawing line segments assert
3) preference changes to panning, etc.
Cheers,
Jeff.
> On 8 Sep 2018, at 17:47, Jeff Young wrote:
>
> No worries JP, you got the fix up before I got around to the first one
No worries JP, you got the fix up before I got around to the first one anyway.
;)
Cheers,
Jeff.
> On 8 Sep 2018, at 17:41, jp charras wrote:
>
> Le 08/09/2018 à 13:16, jp charras a écrit :
>> Le 07/09/2018 à 23:50, Jeff Young a écrit :
>>> I pushed a few more bug
t;
> On 09/06/2018 12:18 PM, jp charras wrote:
>> Le 06/09/2018 à 17:57, Tomasz Wlostowski a écrit :
>>> On 06/09/18 17:37, Jeff Young wrote:
>>>> Hi Tom,
>>>>
>>>> I have committed the completion of the block rotate and mirror fixes
>>&
g for?
>
> On Fri, Sep 7, 2018 at 11:19 AM Jeff Young <mailto:j...@rokeby.ie>> wrote:
> When I move a view item, what is supposed to remove it and re-add it to the
> R-tree?
>
> Right now this isn’t happening so the moved objects get clipped when their
> original
When I move a view item, what is supposed to remove it and re-add it to the
R-tree?
Right now this isn’t happening so the moved objects get clipped when their
original space goes out of the view.
Thanks,
Jeff.
___
Mailing list:
Hi all,
An update on a few of the issues Marcus reported:
1) Hooked up the “Always show cursor” preference so it isn’t shown when no tool
is active.
2) Fixed the outline issue. We *were* drawing the outline centred, it’s just
that we were filling it *after* stroking so that the fill covered
>
> Hi Tom, hi Jeff,
>
> I observed some minor issues (tested on Linux with GTK3):
> - buses and graphic lines always have the same colour as wires
I just pushed a fix for this.
> - symbol outlines/pins are not drawn correctly (see attached screenshot)
It appears that we draw the body line
Hi Folks,
I pushed a commit that overhauls the block logic to allow rotation and
mirroring on the fly with blocks.
Cheers,
Jeff.
> On 6 Sep 2018, at 22:08, Jeff Young wrote:
>
> Hi Marcus,
>
> Supersampling (4x) is still slow on my 3-year-old Mac Powerbook. But
>
,
Jeff.
> On 6 Sep 2018, at 20:59, Aimylios wrote:
>
> Am 06.09.2018 um 17:57 schrieb Tomasz Wlostowski:
>> On 06/09/18 17:37, Jeff Young wrote:
>>> Hi Tom,
>>>
>>> I have committed the completion of the block rotate and mirror fixes
>>> (incl
disappear when ~90 of the module is off the canvas
>
>
> Really looks great so far! Thanks guys!
>
> Am Do., 6. Sep. 2018 um 09:41 Uhr schrieb Jeff Young <mailto:j...@rokeby.ie>>:
> Thanks, JP. I pushed your patch.
>
> > On 6 Sep 2018, at 17:18, jp charras > <
Thanks, JP. I pushed your patch.
> On 6 Sep 2018, at 17:18, jp charras wrote:
>
> Le 06/09/2018 à 17:57, Tomasz Wlostowski a écrit :
>> On 06/09/18 17:37, Jeff Young wrote:
>>> Hi Tom,
>>>
>>> I have committed the completion of the block rotate an
Hi Tom,
I have committed the completion of the block rotate and mirror fixes (including
for LibEdit).
Cheers,
Jeff.
> On 5 Sep 2018, at 23:56, Jeff Young wrote:
>
> I pushed a commit with some improvements for block operations:
>
> 1) when duplicating don’t keep original h
at having block rotate and mirror not drop the block (which is
also a pre-5.0 bug), but it’s going to take some more time.
Cheers,
Jeff.
>
> On 5 Sep 2018, at 18:55, Jeff Young wrote:
>
> Dragging transparency is up.
>
> Cheers,
> Jeff.
>
>
>> On 5 Sep
Dragging transparency is up.
Cheers,
Jeff.
> On 5 Sep 2018, at 15:49, Jeff Young wrote:
>
> I’ll look into it.
>
> In the meantime there’s one more commit up which implements
> MoveCursorToCrossHair().
>
> Cheers,
> Jeff.
>
>
>> On 5 Sep 2
I’ll look into it.
In the meantime there’s one more commit up which implements
MoveCursorToCrossHair().
Cheers,
Jeff.
> On 5 Sep 2018, at 15:44, Tomasz Wlostowski wrote:
>
> On 05/09/18 14:51, Jeff Young wrote:
>> Hi Tom,
>>
>> 2 more commits (update view after
Hi Tom,
2 more commits (update view after dragging symbol and update view after
breaking wire).
Cheers,
Jeff.
> On 5 Sep 2018, at 10:57, Jeff Young wrote:
>
> 2 more commits:
>
> 1) Fixes for LibEdit grid
> 2) Implementation of ERC markers
>
>
>> On 4
2 more commits:
1) Fixes for LibEdit grid
2) Implementation of ERC markers
> On 4 Sep 2018, at 21:54, Jeff Young wrote:
>
> Never mind the LibEdit grid issue: it *is* drawing the grid, it’s just not
> getting the grid dot size so they’re really, really small. I should be able
Never mind the LibEdit grid issue: it *is* drawing the grid, it’s just not
getting the grid dot size so they’re really, really small. I should be able to
track that down….
Cheers,
Jeff.
> On 4 Sep 2018, at 20:27, Jeff Young wrote:
>
> Hi Tom,
>
> 6 more commits are up.
,
Jeff.
> On 4 Sep 2018, at 13:54, Tomasz Wlostowski wrote:
>
> On 04/09/18 11:49, Jeff Young wrote:
>> Hi Tom,
>>
>> I pushed a commit which fixes up the grid, preferences, and Grid Settings…
>> dialog.
>>
> Two more minor issues:
> - ERC markers
Hi Tom,
I pushed a commit which fixes up the grid, preferences, and Grid Settings…
dialog.
Cheers,
Jeff.
> On 3 Sep 2018, at 15:41, Jeff Young wrote:
>
> Yeah, changing the grid spacing also doesn’t work (or at least doesn’t
> refresh) so I’ll look into that too.
>
>>
Yeah, changing the grid spacing also doesn’t work (or at least doesn’t refresh)
so I’ll look into that too.
> On 3 Sep 2018, at 15:08, Tomasz Wlostowski wrote:
>
> On 03/09/18 16:00, Jeff Young wrote:
>> One more commit: implementation of zoom.
>>
>>
> Great J
One more commit: implementation of zoom.
> On 2 Sep 2018, at 23:35, Jeff Young wrote:
>
> 3 more commits:
>
> 1) re-wrote my previous unit handling to also work for libEdit
> 2) fixed a crash bug when cancelling a block selection
> 3) fixed a bug in text measurement (w
eff Young wrote:
>
> Another commit is up with 4 fixes for various orientation and alignment
> issues.
>
> Cheers,
> Jeff.
>
>
>> On 31 Aug 2018, at 22:42, Jeff Young wrote:
>>
>> Hi Tom,
>>
>> Two more commits.
>>
>> The first
Another commit is up with 4 fixes for various orientation and alignment issues.
Cheers,
Jeff.
> On 31 Aug 2018, at 22:42, Jeff Young wrote:
>
> Hi Tom,
>
> Two more commits.
>
> The first implements hidden text, lines, etc.
>
> The second fixes the draw or
Hi Seth,
Copper drawings repel all nets. This example show collisions with text and an
arc (ignore the two via markers):
If you want to see some Christmas lights, set your router to “Highlight
Collisions” mode and run a track into some text. It will highlight individual
segments of the
FWIW, DRC now handles collisions with copper arcs, and zone cutouts for copper
arcs.
What’s still missing is the Connection Algorithm (because they’re arcs and not
tracks). That also means the DRC clearance calculations are one-sided as they
only take into account the clearance of the
provide a user-editable z-order.
Anyway, give it a look and let me know what you think.
Cheers,
Jeff.
> On 31 Aug 2018, at 00:13, Jeff Young wrote:
>
> One more commit (adds dangling ends for lines and labels).
>
>
>> On 30 Aug 2018, at 21:41, Jeff Young wrote:
>>
One more commit (adds dangling ends for lines and labels).
> On 30 Aug 2018, at 21:41, Jeff Young wrote:
>
> Yes, that’s “a couple more issues completed”, not “a couple more issues
> found”. ;)
>
>> On 30 Aug 2018, at 21:38, Tomasz Wlostowski
>> wrote:
>>
Yes, that’s “a couple more issues completed”, not “a couple more issues found”.
;)
> On 30 Aug 2018, at 21:38, Tomasz Wlostowski wrote:
>
> On 30/08/18 21:49, Jeff Young wrote:
>> A couple more for you:
>>
>> 1) pin name/number offset
>> 2) pin electr
A couple more for you:
1) pin name/number offset
2) pin electrical types
3) hidden pins
4) dangling pins (pin targets)
I found another dialog preview (rescue symbols), so I’ll do that next.
Cheers,
Jeff.
> On 30 Aug 2018, at 20:30, Tomasz Wlostowski wrote:
>
> On 29/08/18 20:46, J
Hi Tom,
I pushed again.
This one fixes up the Symbol Viewer (aka Symbol Library Browser).
I’ll go on to pin/text labels next….
Cheers,
Jeff.
> On 29 Aug 2018, at 08:44, Nick Østergaard wrote:
>
> In the Symbol Library Browser
>
> ons. 29. aug. 2018 01.47 skrev Jeff Y
: anyone know of any other eeschema previews in dialogs other than the Symbol
Chooser?
> On 28 Aug 2018, at 21:12, Tomasz Wlostowski wrote:
>
> On 28/08/18 15:30, Jeff Young wrote:
>> I tried to push my changes so you could review them before I get too far,
>> but I don’t
>
>
>>
>> -S
>>
>> Am Di., 28. Aug. 2018 um 10:35 Uhr schrieb Jeff Young > <mailto:j...@rokeby.ie>>:
>>
>>Scratch that last comment; I got myself tied in knots.
>>
>>It is Cairo that renders blocky.
>>
>>
>
yne Stambaugh wrote:
>
> Do we need to write a macos GAL object that uses the native macos device
> context? This seems redundant to me because isn't that the purpose of
> wxDC and it's derivatives?
>
> On 8/28/2018 1:11 PM, Jeff Young wrote:
>> Hi Seth,
>>
>> T
Interesting. It’s not Cairo.
We currently have EDA_DRAW_PANEL_GAL hard-coded to OpenGL, so it’s actually
OpenGL that’s rendering blocky….
> On 28 Aug 2018, at 18:11, Jeff Young wrote:
>
> Hi Seth,
>
> The scaling comes out correct, it’s just blocky.
>
> Is there so
Scratch that last comment; I got myself tied in knots.
It is Cairo that renders blocky.
> On 28 Aug 2018, at 18:29, Jeff Young wrote:
>
> Interesting. It’s not Cairo.
>
> We currently have EDA_DRAW_PANEL_GAL hard-coded to OpenGL, so it’s actually
> OpenGL that’
> Can we just use cairo_scale to adjust the axes for Mac retina?
>
> -S
>
> Am Di., 28. Aug. 2018 um 09:59 Uhr schrieb Jeff Young <mailto:j...@rokeby.ie>>:
> JP made the Footprint Wizard Cairo-only recently, and I planned to do the
> same for the Eeschema dial
JP made the Footprint Wizard Cairo-only recently, and I planned to do the same
for the Eeschema dialog previews.
However, I’ve just discovered that Cairo doesn’t handle Retina displays on Mac.
(It essentially draws blocks of 2x2 pixels instead of individual ones.)
Anyone know if this is
to have write privileges on your repo.
Cheers,
Jeff.
> On 28 Aug 2018, at 13:55, Jeff Young wrote:
>
> Hi Tom,
>
> Thanks for the overview.
>
> The trouble I’m running into is that in the meantime when I instantiate a
> SCH_DRAW_PANEL, it inherits from legacy_g
.
Is it just the constructor I need to replicate (to create a view, hook it up
to the SCH_PAINTER, etc.)?
Cheers,
Jeff.
> On 28 Aug 2018, at 13:25, Tomasz Wlostowski wrote:
>
> On 28/08/18 12:12, Jeff Young wrote:
>> Another question:
>>
>> Right now we have SCH_DRA
and SCH_DRAW_PANEL_GAL.
Thoughts?
> On 27 Aug 2018, at 21:23, Tomasz Wlostowski wrote:
>
> On 27/08/18 22:21, Jeff Young wrote:
>> Music to my ears.
>>
>> So I’ll assume:
>>
>> 1) switch eeschema dialog canvases to Cairo (only)
>> 2) after we’re up and running,
mitted, then do a
rebase, and then re-clone?
Or did I misunderstand more fundamentally?
Thanks,
Jeff.
> On 27 Aug 2018, at 21:15, Jeff Young wrote:
>
> Preferences > Build, Execution, Deployment > CMake > CMake Options
>
>> On 27 Aug 2018, at 21:12, Jeff Young
Preferences > Build, Execution, Deployment > CMake > CMake Options
> On 27 Aug 2018, at 21:12, Jeff Young wrote:
>
> Yeah, I already had.
>
> But that reminded me that it has to be set in CLion somewhere too. Now if
> only I could remember where….
>
>
&g
Yeah, I already had.
But that reminded me that it has to be set in CLion somewhere too. Now if only
I could remember where….
> On 27 Aug 2018, at 21:04, Tomasz Wlostowski wrote:
>
> On 27/08/18 21:56, Jeff Young wrote:
>> He he… you did say that at the start, didn’t you?
&g
JP recently updated one of the Pcbnew previews (footprint viewer, maybe?) to be
fixed-Cairo canvas.
I presume we want to do the same for the Eeschema previews (such as the Symbol
Chooser and Symbol Viewer), and also for the other PCB previews (such as Pad
Properties)?
Are we going to
On 27 Aug 2018, at 20:49, Tomasz Wlostowski wrote:
>
> On 27/08/18 21:43, Jeff Young wrote:
>> OK, got it cloned.
>>
>> But when I do a make install I’m getting:
>
> Did you check out the branch tom-eeschema-gal-aug27?
>
> Tom
__
ts.txt:484 (perform_feature_checks)
> On 27 Aug 2018, at 20:43, Jeff Young wrote:
>
> OK, got it cloned.
>
> But when I do a make install I’m getting:
>
> [ 1%] creating 'boost scratch repo' specifically for boost to track boost
> patches
> make[2]: bz
]: *** [CMakeFiles/boost.dir/all] Error 2
Is there something different about this repo, or did I perform some step on the
main repo that I’ve now forgotten?
Thanks,
Jeff
> On 27 Aug 2018, at 19:54, Tomasz Wlostowski wrote:
>
> On 27/08/18 20:49, Jeff Young wrote:
>> Another question:
master merges with remote master
Local refs configured for 'git push':
5.0pushes to 5.0(local out of date)
master pushes to master (fast-forwardable)
I also don’t see anything under
https://code.launchpad.net/kicad/+git
Thanks,
Jeff.
> On 27 Aug 2018, at 17:27, Jeff Yo
Hi Tom,
What’s the plan for merging? Will I push changes to your branch, or will you
be re-basing it and I should send you patches?
Cheers,
Jeff.
> On 27 Aug 2018, at 14:49, Tomasz Wlostowski wrote:
>
> On 27/08/18 15:43, Jeff Young wrote:
>> Cool. I’ll start on the dialog
Cool. I’ll start on the dialog preview widgets.
Cheers,
Jeff.
> On 27 Aug 2018, at 14:37, Tomasz Wlostowski wrote:
>
> On 24/08/18 17:09, Tomasz Wlostowski wrote:
>> On 24/08/18 16:43, Jeff Young wrote:
>>> Hi Tom,
>>>
>>> Is there anything I can d
We currently draw in the order:
Tracks
PCB objects
Zones
Modules
Since PCB objects are going to be predominantly human-readable stuff, and it
seems like the copper should go together, I'd propose changing it to:
Tracks
Zones
PCB objects
Modules
Note that this won’t make any difference for
ets fork…?
> Old scripts just checked for a change and pulled head of the branch.
>
>
> Regards,
> Bernhard
>
>> On 25. Aug 2018, at 17:10, Jeff Young > <mailto:j...@rokeby.ie>> wrote:
>>
>> BTW, do our build scripts do this automatically?
>&g
BTW, do our build scripts do this automatically?
> On 25 Aug 2018, at 16:10, Jeff Young wrote:
>
> Rats. I meant to mention that folks on OSX will need to pull from our
> wxWidgets branch.
>
> Cheers,
> Jeff.
>
>> On 25 Aug 2018, at 14:19, Adam Wolf > <
Rats. I meant to mention that folks on OSX will need to pull from our
wxWidgets branch.
Cheers,
Jeff.
> On 25 Aug 2018, at 14:19, Adam Wolf wrote:
>
> Hi folks!
>
> I saw this macOS build failure today. Sometimes build failures are flukes,
> but this looks like it might be legit.
>
> Any
Thanks, Ronnie, I’ve cleaned those up.
(Two hadn’t gotten their version updated to 5.0.1, one wasn’t re-opened when it
moved to 5.1, and one was incorrectly marked released.)
Cheers,
Jeff.
> On 25 Aug 2018, at 14:19, Ronnie Gaensli wrote:
>
> Sorry for being pedantic: I've noticed that the
Hi Tom,
Is there anything I can do to help out with the GALification effort?
I’m just trawling the bug list right now, and while there’s plenty available,
fixing them might not be the right priority.
Cheers,
Jeff.
___
Mailing list:
701 - 800 of 1638 matches
Mail list logo
