On 04/21/2016 04:52 PM, jp charras wrote:
> Le 21/04/2016 16:25, Maciej Sumiński a écrit :
>> I got rid off the artifacts resulting from mipmapping, and I think the
>> branch [1] is ready for merging. Apart from bitmap fonts, there are also
>> a few other changes that shoul
On 04/18/2016 05:20 PM, Wayne Stambaugh wrote:
[snip]
> Please don't dismiss this idea too quickly. We've already discussed
> using freetype to allow us to use any font even in boards. We also
> already have an indirect dependency on freetype via cairo so we wouldn't
> be adding much in that
ext chars based on the previous shader calculation :/
> ________
> From: Maciej Sumiński [maciej.sumin...@cern.ch]
> Sent: 18 April 2016 15:12
> To: Mário Luzeiro; kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] Bitmap fonts
>
> Lines a
ril 2016 11:39
> To: kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] Bitmap fonts
>
> Le 15/04/2016 11:21, Maciej Sumiński a écrit :
>> On 04/14/2016 06:39 PM, Simon Richter wrote:
>>> Hi,
>>>
>>> On 14.04.2016 11:33, Maciej Sumi
On 04/15/2016 03:41 PM, "Torsten Hüter" wrote:
> Hi Orson,
> thanks for your nice work. I remember that we have discussed about this
> subject
> a few years ago - in general I think it's an advantage to
> have an alternative for the stroke font. Not for performance, but for the
> visual
>
As you have already noticed - it is not. It may be moved back to
noncached container and it will be redrawn every frame.
Another solution is to apply dynamic scaling using shaders - it is
already done for lines, so they do not disappear when their width is
smaller than 1 px.
Regards,
Orson
On
On 04/15/2016 12:39 PM, jp charras wrote:
[snip]
> Orson,
>
> I just tested your last version, and I find the result rather good.
I have just changed one more thing: now vertex data is not stored in the
system memory, but in mapped video memory [1]. I hope it solves all the
memory related
On 04/14/2016 06:39 PM, Simon Richter wrote:
> Hi,
>
> On 14.04.2016 11:33, Maciej Sumiński wrote:
>
>> Currently, the most expensive thing to draw is stroked text, as there
>> are lots of labels on tracks and pads. To reduce the drawing cost (and
>&g
On 04/15/2016 12:35 AM, Simon Richter wrote:
> Hi,
>
> On 14.04.2016 20:27, Vesa Solonen wrote:
>
>> Orson, please have a look how rendering is done on gEDA gschem. IIRC
>> font rendering is by Peter Clifton and he went on to optimize stroke
>> (pixel)grid fitting, etc. The actual renderer is
On 04/14/2016 08:27 PM, Vesa Solonen wrote:
> 14/04/16, 13:00, Mário Luzeiro kirjoitti:
>
>> But it may suffer from scaling issues, as we can see in your screenshots in
>> the very small size (they are not render properly, C2: pin 1.. etc)
>> So you may need to pre-render the font in difference
)
>
> but if you manage to enable the midmapping in opengl and see that it works
> OKs.. so I guess that it "will work for now"
> .. but mind that the openGL midmapping may be an overwriten quality option by
> the system configuration.
>
> my 2 cents (of €uro)! :P
> Mario
&
On 04/14/2016 03:30 PM, jp charras wrote:
[snip]
> I just tested it
> (note: on msys2, W7 32 bits I had a GL_INVALID_FRAMEBUFFER_OPERATION
> undefined compil error)
It should be fixed now.
Regards,
Orson
signature.asc
Description: OpenPGP digital signature
On 04/14/2016 03:30 PM, jp charras wrote:
[snip]
> Thanks, Orson.
>
> I just tested it
> (note: on msys2, W7 32 bits I had a GL_INVALID_FRAMEBUFFER_OPERATION
> undefined compil error)
>
> After testing a complex 16 layers board, the current version allocates up to
> 128 Mbytes, and the
>
but as far as I know,
> most of the times they use "one font size" -> "one texture" and it is not
> common to have different text scales on/using the same font/texture
> Thats it why you need to go more tricky here.. :)
>
> Mario
> _
Regards,
Orson
> Keep good work!
> Mario Luzeiro
>
> From: Kicad-developers
> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of
> Maciej Sumiński [maciej.sumin...@cern.ch]
> Sent: 14 April 2016 10:33
> To: Ki
On 04/14/2016 11:48 AM, Lorenzo Marcantonio wrote:
> On Thu, Apr 14, 2016 at 11:33:18AM +0200, Maciej Sumiński wrote:
>> Hi,
>>
>> As recently Jean-Pierre has reported he had been running out of memory
>> with complex boards, I decided to take another step to reduce me
Hi,
As recently Jean-Pierre has reported he had been running out of memory
with complex boards, I decided to take another step to reduce memory
footprint of OpenGL canvas.
Currently, the most expensive thing to draw is stroked text, as there
are lots of labels on tracks and pads. To reduce the
On 04/04/2016 01:39 PM, jp charras wrote:
> Sorry if you already sent me a response to this "old" message (first posted
> on feb 05)
> but I did not remember this response.
>
> It is annoying for the rounded rect pads which use this method.
> (I currently use a fixed (modified) version in my
On 04/04/2016 12:50 PM, jp charras wrote:
> Le 04/04/2016 01:28, Collin Anderson a écrit :
>> So, I used to be into game development, I was big on writing my own engines
>> from scratch in C++.
>> This exact memory management problem is one encountered very frequently in
>> such projects. Any
y, there are no hangs with the timer.
>
>
> Regards,
> Bernhard
>
>> On 12 Feb 2016, at 14:06, Maciej Sumiński <maciej.sumin...@cern.ch> wrote:
>>
>> Hi Bernhard,
>>
>> I see your patch significantly affects the performance, but I need to
>>
; information. It is used in wxWidgets window.mm, for instance, when
>> translating NSEvents to wx events.
>>
>> Garth
>>
>>> On Feb 8, 2016, at 9:31 AM, Bernhard Stegmaier <stegma...@sw-systems.de>
>>> wrote:
>>>
>>>
>>>
Redrawing has to be done with every mouse movement (at least to redraw
the cursor), so to avoid issuing too frequent paint events, the timer
limits the number of requests per second.
I cannot really tell why there is such discrepancy in wxTimer behavior
depending on the platform. Was this the
On 02/08/2016 06:17 PM, Andy Peters wrote:
>
>> On Feb 8, 2016, at 9:25 AM, Wayne Stambaugh wrote:
>>
>> I'm surprised other osx users have not complained about this before now.
>> Is it possible that this is due a particular version of wxWidgets
>> and/or osx and only
On 02/01/2016 08:18 PM, jp charras wrote:
> Le 01/02/2016 19:33, Andrew Zonenberg a écrit :
>> Pads on the same net overlapping should not necessarily be a DRC
>> error, consider the case of someone trying to make a D-shaped pad
>> by putting a round one on top of a rectangle. Maybe if they're
Thank you Andrew, that was a good catch!
Regards,
Orson
On 02/01/2016 07:33 PM, Andrew Zonenberg wrote:
> Pads on the same net overlapping should not necessarily be a DRC
> error, consider the case of someone trying to make a D-shaped pad by
> putting a round one on top of a rectangle. Maybe if
Apparently the most expensive part is RN_DATA::processPads() that does
collision checks for pads. It handles cases when tracks do not end in
the middle of a pad, or when pads overlap (IMHO this should be caught by
DRC as an error instead, as pointed out at FOSDEM).
If you do not care about mini
After some extra testing and fixes, I have merged the patches
[6522-6527]. I hope it will encourage others to test it out as well.
Thank you Tom, now the forward annotation process is much faster &
convenient.
Regards,
Orson
On 01/21/2016 11:30 PM, Tomasz Wlostowski wrote:
> Dear all,
>
> This
On 01/07/2016 11:39 AM, "Torsten Hüter" wrote:
> Hi Wayne,
>
> this is of course right, but the idea would be to emulate cooperative
> multitasking with threads. This is done by synchronizing the threads with
> condition variables and mutexes. The principle can be found in the articles
> [1]
On 12/11/2015 05:58 PM, Wayne Stambaugh wrote:
> On 12/11/2015 3:25 AM, Maciej Sumiński wrote:
>> On 12/08/2015 09:57 PM, Wayne Stambaugh wrote:
>> [snip]
>>> I'm not the biggest github fan either. I think its OK but it was
>>> expecting a lot more given all of
Very nice! I like the way it works now. The code looks fine too, though
I am wondering why do you std::swap in BOARD::ReplaceNetlist instead of
simply filling aNewFootprintsVector? It adds some unnecessary copying,
though it should not be noticeable for the user when it comes to
execution time.
Hi Tom,
Thank you for noticing, a pull request to correct this has already been
sent.
BTW: I have just noticed we keep two documents describing the compiling
process - on the website and in the source repository
(Documentation/development/compiling.md). How about getting rid of the
latter one?
Apparently find_package() is not able to determine the OpenGL library
version, so any requirements are not really meaningful there.
Perhaps it has a meaning for other platforms, and if so then I would use
2.1 as the required version.
Regards,
Orson
On 12/20/2015 08:29 PM, Wayne Stambaugh wrote:
Hi Windsor,
Thank you for the patch, I like the results. Personally, I would love to
have it merged, but we need to check if it does not break anything on
other platforms first.
Regards,
Orson
On 12/14/2015 04:42 AM, Windsor Schmidt wrote:
> Hi everyone,
>
> This is my first post to the list,
On 12/08/2015 09:57 PM, Wayne Stambaugh wrote:
[snip]
> I'm not the biggest github fan either. I think its OK but it was
> expecting a lot more given all of the fan fair. I do like working with
> git. I've been using it exclusively for my Eeschema refactor work. Has
> anyone tried using the
c 10, 2015 at 8:05 PM, Maciej Sumiński <maciej.sumin...@cern.ch>
> wrote:
>
>> Hi Cirilo,
>>
>> Should not it be 'GLM_INCLUDE_DIR' there?
>>
>> Regards,
>> Orson
>>
>> On 12/10/2015 02:09 AM, Cirilo Bernardo wrote:
>>> Some more
Hi Cirilo,
Should not it be 'GLM_INCLUDE_DIR' there?
Regards,
Orson
On 12/10/2015 02:09 AM, Cirilo Bernardo wrote:
> Some more header problems have been revealed by people building
> kicad since we switched to using the system's installed libglm.
> In many instances '#include ' only worked by
>
OpenMP is optional, it boosts the ratsnest calculation in GAL canvases.
It was in the section specific to both gcc and clang, what are other
compilers that we support?
Anyway, if it works for other compilers, I do not see a reason that
prevents enabling it.
Regards,
Orson
On 12/10/2015 02:30
> commit it if you comfortable with the changes.
>
> Thanks,
>
> Wayne
>
> On 12/7/2015 7:38 AM, Maciej Sumiński wrote:
>> Hi Cirilo,
>>
>> Thank you for the FindGLM script. I had to modify it slightly, as it did
>> not work with CMake 3.4.0 (problem wi
Hi Cirilo,
Thank you for the FindGLM script. I had to modify it slightly, as it did
not work with CMake 3.4.0 (problem with STREQUAL).
Here is complete patch [1], that I applied to KiCad in order to use the
system glm library (0.9.7 in my case). If there are no problems with
other
_
> From: Kicad-developers
> [kicad-developers-bounces+mrluzeiro=ua...@lists.launchpad.net] on behalf of
> Maciej Sumiński [maciej.sumin...@cern.ch]
> Sent: 04 December 2015 08:37
> To: Cirilo Bernardo; KiCad Developers
> Subject: Re: [Kicad-developers] GLM
>
> Hi Ciri
Hi Cirilo,
I do not see any obstacles. Are you already testing the new version? If
everything seems fine, then I will update it in the product branch.
Regards,
Orson
On 12/03/2015 10:10 PM, Cirilo Bernardo wrote:
> While looking into preparing an initial merge of the 3D refactor branch I
>
On 11/05/2015 04:39 AM, Marco Ciampa wrote:
> On Tue, Nov 03, 2015 at 12:36:41PM +0200, Lachlan Audas wrote:
>> Hi, I was looking at the source code, and my old brain need's some real
>> help with all the endless includes.. etc
>> I was wondering if any one had put up the source code using Lxr,
Hi Mario,
Here is the board [1] that I used for testing OpenGL canvas performance.
Regards,
Orson
1. http://www.ohwr.org/attachments/download/2187/wrs.kicad_pcb
On 11/01/2015 06:59 AM, Mário Luzeiro wrote:
> Hello all,
>
> Does anyone have some complex board designed in kicad to share?
Hi Dan,
Unfortunately, we have not received the screenshots.
Would you report the problem on the official bug tracker [1], so we will
have a permanent trace of it? Issues reported exclusively on the mailing
list tend to be forgotten.
Regards,
Orson
1. https://bugs.launchpad.net/kicad/
On
Hi Bernhard,
This is how it works in the legacy canvas, nothing wrong with OSX. We
have simply done it in a different way in the GAL canvas.
Regards,
Orson
On 10/21/2015 04:09 PM, Bernhard Stegmaier wrote:
> Hi,
>
> nice discussion, but could anybody please just try if drawing arcs on
>
did not find out how to do that in pcbnew - apart from creating some
> (random) arc with the mouse and then tweaking it via the edit menu the way it
> should be.
> If that is how it should be, fine for me… :)
>
>
> Regards,
> Bernhard
>
>> On 21 Oct 2015, at 07:17,
On 10/13/2015 09:51 PM, Adam Wolf wrote:
> Hi folks,
>
> This is actually the article I ran into today:
>
> https://rheingoldheavy.com/new-stable-kicad-10-steps-to-import-an-old-kicad-project/
>
> Is there an official document on migrating from 4022 to 4.0.0?
>
> Adam Wolf
> Cofounder and
On 10/11/2015 03:37 PM, Marco Ciampa wrote:
> 2) the only mention to this is here:
>
> http://docs.kicad-pcb.org/en/pcbnew.html#_general_remarks
There is also: http://kicad-pcb.org/post/known-system-related-issues/
Perhaps it could be moved to a permanent page (Help->Known issues or
something
Hi Jean-Pierre,
On 09/24/2015 01:53 PM, jp charras wrote:
> Orson,
>
> Could you have a look at these few issues:
>
> - When the number of layers is increased (for instance from 2 to 4
> layers), the tracks drawn on the new layers (for instance usung the
> legacy mode) are not displayed in
On 09/24/2015 03:24 PM, jp charras wrote:
> Le 24/09/2015 14:38, Maciej Sumiński a écrit :
>> Hi Jean-Pierre,
>>
>> On 09/24/2015 01:53 PM, jp charras wrote:
>>> Orson,
>>>
>>> Could you have a look at these few issues:
>>>
>>> - Wh
On 09/24/2015 06:38 PM, Maciej Sumiński wrote:
> On 09/24/2015 03:24 PM, jp charras wrote:
>> When I encountered this "issue", the currently selected layer pair was
>> Front+back, and the error message was "Only through vias can be placed
>> between front and
On 09/13/2015 10:45 PM, bob smith wrote:
> Hi,
>
> Possibly working on a feature, just wanted to bounce my ideas off you guys.
>
> The basic idea is as follows:
>
> As you block select footprints/symbols, the settings dialog shows the
> settings that are common to all of the selected
On 09/03/2015 11:37 PM, Brian Sidebotham wrote:
> To match functionality of the Legacy canvas I propose we extend the
> GAL ORIGIN_VIEWITEM class to allow us to add an axis origin marker
> when using the Footprint Editor. I'm sure even while in the stable
> feature-lock this is okay to commit, but
On 09/03/2015 09:58 PM, LordBlick wrote:
> In response to a message written on 02.09.2015, 22:38, from Maciej
> Sumiński:
>> True, I would like to remove the center point due to the same reason. I
>> am just not sure if there is other code relying on the cu
I am working on one issue related to arc bounding box in pcbnew, and I
am wondering whether it is desired to include the center point when
computing the bounding box (check the attached screenshot for
comparison). It seems to me that only the arc itself is relevant, but I
might be missing
On 09/02/2015 06:36 PM, LordBlick wrote:
> In response to a message written on 02.09.2015, 17:48, from Maciej
> Sumiński:
>> I am working on one issue related to arc bounding box in pcbnew, and I am
>> wondering whether it is desired to include the center point when
>> c
al.
>
> Marcos
>
> On Wed, Sep 2, 2015 at 2:05 PM, LordBlick <lordbl...@gmail.com> wrote:
>
>> In response to a message written on 02.09.2015, 18:54, from Maciej
>> Sumiński:
>>
>>> On 09/02/2015 06:47 PM, LordBlick wrote:
>>>
>>>> I
Well done team! The new site looks way *much* better and seems to be
easier to navigate. Thank you for the effort you have put into bringing
it up.
Regards,
Orson
On 08/26/2015 11:31 PM, Nick Østergaard wrote:
Hello KiCad developers
We are happy to announce a new website for KiCad, this
Hi Michael,
Unfortunately both patches came here malformed (1st has lines wrapped,
2nd one contains additional empty lines), but anyway I applied in
revision 6129. Thank you for helping with KiCad development.
Regards,
Orson
On 08/26/2015 05:37 PM, Michael Beardsworth wrote:
I moved the patch
On 08/25/2015 05:59 PM, Maciej Sumiński wrote:
On 08/25/2015 05:48 PM, Wayne Stambaugh wrote:
Is anyone else have an issue with the track width and via diameter combo
boxes in the auxiliary tool bar not being populated with the board
design rules information? I just noticed this because I
On 08/25/2015 05:48 PM, Wayne Stambaugh wrote:
Is anyone else have an issue with the track width and via diameter combo
boxes in the auxiliary tool bar not being populated with the board
design rules information? I just noticed this because I added some
dummy design rules so I could change
Hi Jean-Pierre,
I have just pushed a fix for the problem you describe (revision 6132).
Please let me know if it works for you.
Regards,
Orson
On 08/25/2015 10:59 AM, jp charras wrote:
Hi, Orson.
I have a usability issue in GAL mode (Windows specific, at least W7 32
bits) when a Pcbnew
On 08/23/2015 05:23 PM, Lorenzo Marcantonio wrote:
Strange thing of the day. In the footprint editor settings I customize
things as desired, they persist correctly between invocations.
Choosing new footprint however reset them to the compiled-in defaults...
First look impression: could
Hi Joseph,
Does KiCad crash after these messages? If no, then I would not worry too
much - I have seen such errors in many other applications, without
facing any particular problems.
Regards,
Orson
On 08/22/2015 10:18 AM, Joseph Chen wrote:
Does anyone know the possible causes for my following
, 2015 at 10:39:54AM -0400, Wayne Stambaugh wrote:
On 8/5/2015 10:16 AM, Maciej Sumiński wrote:
Chris has pointed out that it was already discussed [1] and the change
was not entirely clear. Apparently it had not been wrapped before
revision 5834, so maybe OnPgmExit() should be still called
If I may suggest something, how about wrapping the 4 lines to load
preferences into a function (e.g. EDA_DRAW_PANEL::LoadPreferences( const
EDA_DRAW_PANEL* aOther ))?
Regards,
Orson
On 08/07/2015 03:01 AM, Jon Neal wrote:
This patch is to provide a general fix for bug #1468388. There is a patch
Pcbnew without scripting support crashes when run with an invalid file
given as a parameter (stack overflow in ~wxSingleInstanceChecker()).
There is a fix for that, but wrapped with #ifdef
KICAD_SCRIPTING_WXPYTHON .. #endif. I removed the mentioned directives
and it seems fine here, but I am not
/kicad-developers@lists.launchpad.net/msg14014.html
On 08/05/2015 11:22 AM, Maciej Sumiński wrote:
Pcbnew without scripting support crashes when run with an invalid file
given as a parameter (stack overflow in ~wxSingleInstanceChecker()).
There is a fix for that, but wrapped with #ifdef
On 08/05/2015 04:39 PM, Wayne Stambaugh wrote:
On 8/5/2015 10:16 AM, Maciej Sumiński wrote:
Chris has pointed out that it was already discussed [1] and the change
was not entirely clear. Apparently it had not been wrapped before
revision 5834, so maybe OnPgmExit() should be still called
Hi Simon,
Thank you for noticing, now it is corrected.
Regards,
Orson
On 07/28/2015 12:40 AM, Simon Richter wrote:
Hi,
that function returns a bool, but common/geometry/shape_poly_set.cpp
line 704-705 has
if( !d )
return -1;
That smells fishy and
On 07/31/2015 09:43 PM, LordBlick wrote:
In response to a message written on 24.07.2015, 16:42, from Tomasz
Wlostowski:
On 24.07.2015 16:20, jp charras wrote:
I'll have a look at this dialog.
In a recent commit (the one for single-click update) I've fixed this
problem
- now the HTML panel
test in modedit because I get a crash after switching to OpenGL
thanks
Maurice
On 30/07/2015 14.25, Maciej Sumiński wrote:
Hi Marco,
Thank you for reporting the issue. It should be fixed in revision 6023.
Regards,
Orson
On 07/30/2015 02:40 AM, Marco Hess wrote:
Hi Maciej,
I am
Applied in 6026, thank you!
Regards,
Orson
On 07/27/2015 11:59 PM, Simon Richter wrote:
This macro is defined in stddef.h, so cstddef is needed.
---
include/gal/opengl/vertex_common.h | 2 ++
1 file changed, 2 insertions(+)
___
Mailing
On 07/29/2015 12:25 PM, Marco Hess wrote:
[snip]
But the DXF import only working in legacy mode and not in the other
modes is a
definitely a bug I think.
Marco
Hi Marco,
I have just tried importing the mentioned file and it worked here. Could
you give some more details about the problem?
On 07/14/2015 06:31 AM, Blair Bonnett wrote:
I cannot reproduce this on r5908 from the product branch. I
am building the latest revision from there now to check with.
I can now confirm this does not occur on r5935 so it does seem to be
something to do with the new polygon handling.
I have
Hi Andrew,
Thank you very much for the patchset, it's really appreciated. I have
just merged all the changes (5928).
Regards,
Orson
On 07/12/2015 01:12 AM, Andrew Zonenberg wrote:
Hi guys,
Here's a fix for two separate issues where the GAL text tool captures
the cursor under undesirable
Hi Jon,
I have applied one of the patches you have attached to the responding
bug report with minor modifications in 5909.
I have chosen another patch as I would rather avoid making GAL dependent
on the legacy canvas and one of your patches did it the right way. Thank
you for fixing this!
On 07/06/2015 03:24 PM, LordBlick wrote:
In response to a message written on 06.07.2015, 14:27, from Maciej
Sumiński:
On 07/02/2015 09:56 PM, LordBlick wrote:
After select some items and pressing any of „←”, „→”, „↑”, „↓” first
action
makes only cursor move (toward closest gird point
Hi,
On 07/04/2015 10:23 AM, LordBlick wrote:
I found in GAL some issues:
- sometimes, when zone was changed and Undo requested it hangs in some
loop,
application kill needed.
Is there a board file that could ease reproducing the issue?
- zone refilling is not necessary, when it's not
Hi Garth,
Thank you for the patch. I consider the changes to be low risk, so they
have been committed in revision 5888.
Regards,
Orson
On 07/04/2015 11:33 PM, Garth Corral wrote:
On Jul 4, 2015, at 2:02 PM, Garth Corral
gcor...@abode.commailto:gcor...@abode.com wrote:
On Jul 1, 2015,
On 07/06/2015 02:30 PM, Tomasz Wlostowski wrote:
Fixes to SHAPE_POLY_SET slitting/fracturing algo: - Tom's too
dumb to use C++ iterators (so he uses pointers now ;) - Some speed
optimization
I have tested the patch with all demos and one case that crashed KiCad
before and all worked fine.
On 07/02/2015 09:24 AM, jp charras wrote:
Le 02/07/2015 09:13, LordBlick a écrit :
In response to a message written on 02.07.2015, 05:44, from Garth Corral:
While poking at function keys in response to the earlier thread about,
uh, function keys. I stumbled on a crash caused by switching to
Thank you for noticing, should be fixed in 5850.
Regards,
Orson
On 06/30/2015 08:36 PM, Nick Østergaard wrote:
I can confirm this issue on 5848 linux.
2015-06-30 19:41 GMT+02:00 LordBlick lordbl...@gmail.com:
After last patches I assume that there is problem with displayed cursor
positions
On 06/26/2015 09:05 PM, LordBlick wrote:
In response to a message written on 26.06.2015, 17:50, from Maciej
Sumiński:
My patch was only for the html report window (i.e. the one in the
netlist import dialog). What is your opinion about the final effect? I
hope it looks fine with light gray
On 06/28/2015 10:14 PM, LordBlick wrote:
In response to a message written on 28.06.2015, 14:25, from Simon Richter:
A few years ago, I've made some projects with netnames ended with
-MINUS/-PLUS,
so now I've made some patch, which expands namespace of differential
pairs PNS
router, to enjoy
On 06/26/2015 05:46 PM, LordBlick wrote:
In response to a message written on 26.06.2015, 16:48, from Tomasz
Wlostowski:
Given the number of Linux flavors out there, and the way people customize
their systems, it's next to impossible to make things render correctly
under
every single Linux
On 06/26/2015 05:28 PM, Wayne Stambaugh wrote:
On 6/26/2015 10:56 AM, jp charras wrote:
Le 26/06/2015 16:11, LordBlick a écrit :
In response to a message written on 26.06.2015, 14:57, from Wayne
Stambaugh:
It uses HTML to render the report - so when we generate the HTML we
need to
take the
Committed in 5794, thanks!
Cheers,
Orson
On 06/19/2015 06:50 PM, Tomasz Wlostowski wrote:
On 19.06.2015 18:35, jp charras wrote:
Among issues detected by Coverity, 3 of them worried me.
(see attached text for these 3 Coverity bugs or strange things)
- In shape_collisions.cpp , CollideShapes
Hi Jon,
Thank you for the patch. I have committed it in 5767 with a minor
modification - I removed the zoom in part, as the legacy canvas does not
do that.
Regards,
Orson
On 06/18/2015 12:44 AM, Jon Neal wrote:
Fixes a discrepancy between legacy and GAL described in this bug:
On 06/01/2015 06:23 PM, Tomasz Wlostowski wrote:
Hi all,
I did a small investigation of the polygon-related
segfaults/miscalculations. It looks like Boost.polygon badly handles
cases where intersection points of the edges of the polygons lie close
to each other or overlap, causing the 'snap
Hi Chris,
I could not reproduce the assert, but your patch surely will not harm
the code, so there are chances it is going to work better. Thank you, I
committed your changes in revision 5695.
Regards,
Orson
On 06/02/2015 05:44 PM, Chris Pavlina wrote:
In GAL, an assertion
Hi Melroy,
Interactive Router should be merged with Pcbnew documentation. I will
handle it this week.
Regards,
Orson
On 05/27/2015 03:00 PM, Melroy van den Berg wrote:
True, example link:
Hi Chris,
Good point, thank you for the patch. It has been committed in revision 5682.
Regards,
Orson
On 05/26/2015 04:30 PM, Chris Pavlina wrote:
D_PAD::ViewGetLayers tries to handle the case of a pad that exists only
on mechanical layers, but misses a few (silkscreen, Dwgs.User,
wxWidgets.
On May 21, 2015, at 2:31 PM, Maciej Sumiński maciej.sumin...@cern.ch wrote:
Wayne agreed, so the patch has been committed in 5673. There is just one
reminder - please test the patch thoroughly before the stable release,
as later we will only backport patches that cause
/work on OS X.
Garth
On May 21, 2015, at 12:13 PM, Maciej Sumiński maciej.sumin...@cern.ch
wrote:
Hi Garth,
If I recall correctly there were issues on other platforms, but I guess
it is not the case anymore, so if Wayne does not mind - I will merge
them. Personally, I do not mind applying
On May 18, 2015, at 5:09 AM, Maciej Sumiński maciej.sumin...@cern.ch wrote:
Hi,
I have just committed a patch that should fix the problem. Finally I had
an opportunity to play with a MacBook, and it resulted in two more
changes for Macs:
- Apple MagicMouse and trackpad should be now usable
Hi,
There were already 2 people today who had the same problem. I have just
changed the patch, so the modified wx headers contain a #define to
indicate that you are building using patched version. I apologize for
disturbances.
I only had a Mac with Retina screen at hand, so I could not test
Hi Johannes,
Thank you for spotting the typo, it should be fixed now.
Regards,
Orson
On 05/19/2015 05:25 PM, Johannes Maibaum wrote:
Dear list,
first, a big thank you to Orson for fixing the OpenGL zooming issues on OSX
as Pcbnew is a lot more usable now. Even if one can become quite
Hi,
I have just committed a patch that should fix the problem. Finally I had
an opportunity to play with a MacBook, and it resulted in two more
changes for Macs:
- Apple MagicMouse and trackpad should be now usable (no more crazy
zooming in/out).
- Full resolution support for Retina screens in
Is it possible the problem is related to the recent diode pin swapping
in KiCad library?
Regards,
Orson
On 05/13/2015 05:35 PM, Chris Pavlina wrote:
Hi Wayne,
That's interesting. I can't really imagine what would cause that, and I
haven't seen anything like that - I've tested it on many
601 - 700 of 886 matches
Mail list logo