This came from wxWidgets trunk and fixes http://trac.wxwidgets.org/ticket/15684
Garth
> On Nov 6, 2014, at 4:54 PM, Wayne Stambaugh wrote:
>
> Sorry it took so long. I committed this patch in product branch r5256.
> Thank you for your contribution to KiCad. Did you pulling this patch
> from w
Sorry it took so long. I committed this patch in product branch r5256.
Thank you for your contribution to KiCad. Did you pulling this patch
from wxWidgets trunk or did you fix it yourself? If you fixed a
wxWidgets bug, please open a bug report on the wxWidgets bug tracker so
we don't have to ma
Adam,
I’m glad you picked #2. That’s what make the most sense.
Jean-Paul
AC9GH
On Nov 6, 2014, at 4:00 PM, Adam Wolf wrote:
> There will be an appropriate symlink.
>
> Adam Wolf
>
> On Thu, Nov 6, 2014, 2:17 PM Bob Gustafson wrote:
> I would vote for 2 or 3.
>
> One question is whether ~/L
Thanks for testing this Bernhard.
Cheers,
Wayne
On 11/6/2014 2:52 PM, Bernhard Stegmaier wrote:
> … applies, builds, and fixes the problem (tested with rev. 5249).
>
> Regards,
> Bernhard
>
>> On 06.11.2014, at 20:25, Bernhard Stegmaier wrote:
>>
>> I can check on OSX…
>>
>> On 06.11.2014, at
On 11/6/2014 3:32 PM, Garth Corral wrote:
> Thanks, Bernhard, and sorry again, Wayne, for the poorly written bug. I’m a
> little surprised you’re not seeing it on Windows, it doesn’t seem like it
> should be platform specific.
It's possible that on Windows that a separate wxWidgets event doesn'
There will be an appropriate symlink.
Adam Wolf
On Thu, Nov 6, 2014, 2:17 PM Bob Gustafson wrote:
> I would vote for 2 or 3.
>
> One question is whether ~/Library/Application\ Support/ is visible in the
> Finder or would the magic move/copy/link be done by drag and drop icons on
> the dmg back
Thanks, Bernhard, and sorry again, Wayne, for the poorly written bug. I’m a
little surprised you’re not seeing it on Windows, it doesn’t seem like it
should be platform specific.
Garth
On Nov 6, 2014, at 11:52 AM, Bernhard Stegmaier wrote:
> … applies, builds, and fixes the problem (tested
I would vote for 2 or 3.
One question is whether ~/Library/Application\ Support/ is visible in
the Finder or would the magic move/copy/link be done by drag and drop
icons on the dmg background?
Bob G
On 11/06/2014 01:09 PM, Adam Wolf wrote:
I'll try to clarify the options that I see.
1) Store
> On Nov 6, 2014, at 12:36 PM, Bernhard Stegmaier
> wrote:
>
> Is it on intention that you use "-mmacosx-version-min=10.9”?
> I always build with 10.5 and everything is fine… maybe some previously only
> deprecated changes got removed when using a 10.9 Framework?
I tried both 10.5 and 10.9 an
… applies, builds, and fixes the problem (tested with rev. 5249).
Regards,
Bernhard
> On 06.11.2014, at 20:25, Bernhard Stegmaier wrote:
>
> I can check on OSX…
>
> On 06.11.2014, at 20:19, Wayne Stambaugh wrote:
>
>> On 11/6/2014 2:01 PM, Garth Corral wrote:
>>>
>>> Yes, sorry, OS X. I’ll
Is it on intention that you use "-mmacosx-version-min=10.9”?
I always build with 10.5 and everything is fine… maybe some previously only
deprecated changes got removed when using a 10.9 Framework?
Regards,
Bernhard
On 06.11.2014, at 19:57, Andy Peters wrote:
>>
>> On Nov 6, 2014, at 10:09 AM
Great! 2 it is. (and the docs are going to be inside the executable)
Adam Wolf
On Nov 6, 2014 1:25 PM, "Bernhard Stegmaier"
wrote:
> I also think #2 is best…
>
> Downloading a little bit more doesn’t hurt nowadays.
> Advanced users with their own library can just ignore the ones in the dmg,
> b
I also think #2 is best…
Downloading a little bit more doesn’t hurt nowadays.
Advanced users with their own library can just ignore the ones in the dmg,
beginners get everything at once (but, of course, have to install application
and libraries separately).
Documentation should of course go in
I can check on OSX…
On 06.11.2014, at 20:19, Wayne Stambaugh wrote:
> On 11/6/2014 2:01 PM, Garth Corral wrote:
>>
>> Yes, sorry, OS X. I’ll add the version information to the bug and include
>> it in the future.
>
> That's why I didn't see it. If someone with OSX could verify this patch
>
On 11/6/2014 2:01 PM, Garth Corral wrote:
>
> Yes, sorry, OS X. I’ll add the version information to the bug and include it
> in the future.
That's why I didn't see it. If someone with OSX could verify this patch
I would appreciate it. I'll test it on windows and linux to make sure
it doesn't
In response to a message written on 06.11.2014 16:32, from jp charras:
CPolyLine now is mapped in python since revision 5253
Attached a file which read and print zones and outlines corner lists
from a board.
Thanks a lot.
--
Best Regards,
LordBlick
__
I'll try to clarify the options that I see.
1) Store the libraries *inside* the bundle, in kicad.app. Users should
never change these, because if they do, the changes would be lost when you
update KiCad.
2) Have the libraries be included in the DMG, but users would have to drag
Kicad into Applica
> On Nov 6, 2014, at 11:51 AM, Bernhard Stegmaier
> wrote:
>
> Yes, one .dmg is also fine with me.
>
> We shouldn’t put anything into the bundle that a user can change (like adding
> his own symbol to a predefined library, etc.).
> If the changes are stored in files inside the bundle itself t
Yes, sorry, OS X. I’ll add the version information to the bug and include it
in the future.
Garth
On Nov 6, 2014, at 10:49 AM, Wayne Stambaugh wrote:
> What platform are you using? You should always copy the clipboard from
> the Help->Copy Version Information menu entry. That typically te
Hmm. Now I don't know which to do.
Would two DMGs make it easier for end users to modify things?
I do not want to move into Mac packages.
Adam Wolf
On Thu, Nov 6, 2014 at 12:51 PM, Bernhard Stegmaier wrote:
> Yes, one .dmg is also fine with me.
>
> We shouldn’t put anything into the bundle t
> On Nov 6, 2014, at 10:09 AM, Adam Wolf wrote:
>
> First, I patch the source with:
>
> patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
> patch -p0 <
> ../kicad/patches/wxwidgets-3.0.0_macosx_bug_15908.patch
> patch -p0 <
> ../kicad/pa
Hey Adam,
Is this your patch? I want to make sure I give credit to the
appropriate author when I commit it.
Thanks,
Wayne
On 11/5/2014 9:53 PM, Adam Wolf wrote:
> Hi folks,
>
> I have isolated the problem and solved it. Thankfully, the CMake folks
> have already ran into it, and solved it.
>
What platform are you using? You should always copy the clipboard from
the Help->Copy Version Information menu entry. That typically tells the
developer the minimum information required to evaluated your bug report.
I just tested this on windows debug build and it doesn't happen so
apparently it
Yes, one .dmg is also fine with me.
We shouldn’t put anything into the bundle that a user can change (like adding
his own symbol to a predefined library, etc.).
If the changes are stored in files inside the bundle itself then they will just
get lost when a user tries to update the usual way (del
If you inadvertently select the Hotkeys sub-menu (not an item within it) from
the Preferences menu of any application, it presents an error dialog. I’ve
filed https://bugs.launchpad.net/kicad/+bug/1389932 with patch.
Garth
smime.p7s
Description: S/MIME cryptographic signature
_
The current dmg for the kicad application for OS X has an alias for
Applications, so people can just draft the Kicad folder to the Applications
link and everything is good.
For libraries, the majority of users will want to install them on their own
home directory, so I will do that. I will includ
> On Nov 6, 2014, at 11:32 AM, Jean-Paul Louis wrote:
>
> Bernhard and Adam,
> I agree with Bernhard that the libraries should not be in the app bundle, but
> the libraries should still be in the same dmg package, as it would be very
> frustrating for a beginner to install the app and find out
Patch committed in product branch 5254. Thank you for the patch Adam.
Wayne
On 11/6/2014 1:30 PM, Adam Wolf wrote:
> Yes. Thanks Wayne!
>
> (OS X Kicad is getting more and more useful, everyday!)
>
> Adam Wolf
> Cofounder and Engineer
> W&L
>
>
> On Thu, Nov 6, 2014, 12:27 PM Wayne Stambaug
Bernhard and Adam,
I agree with Bernhard that the libraries should not be in the app bundle, but
the libraries should still be in the same dmg package, as it would be very
frustrating for a beginner to install the app and find out that they cannot do
anything worth a try until they contact someo
Yes. Thanks Wayne!
(OS X Kicad is getting more and more useful, everyday!)
Adam Wolf
Cofounder and Engineer
W&L
On Thu, Nov 6, 2014, 12:27 PM Wayne Stambaugh
wrote:
> Hey Adam,
>
> Is this your patch? I want to make sure I give credit to the
> appropriate author when I commit it.
>
> Thanks,
Great job, Adam.
My vote is for the separate dmg image for libraries.
As a normal OSX user you won’t do anything inside the bundle, so I think it is
more easy to just grab the library.dmg and pull contents to the
~/Library/Application Support/kicad/library folder.
Changing things inside the hom
Hi
patch looks good.
Same problem could come up when bundling the standalone apps.
This currently is no problem because when those standalone bundles are moved
into the main kicad bundle the individual Frameworks folder is replaced by a
symlink to main kicad.app Framework folder.
As long as thi
I agree with Wayne’s opinion.
Everything in a single package is a lot less frustrating for new users.
Jean-Paul
AC9GH
On Nov 6, 2014, at 11:36 AM, Wayne Stambaugh wrote:
> On 11/6/2014 11:32 AM, Adam Wolf wrote:
>> Alternatively, what do folks think about packaging the libraries as a
>> dmg? T
First, I patch the source with:
patch -p0 < ../kicad/patches/wxwidgets-3.0.0_macosx.patch
patch -p0 <
../kicad/patches/wxwidgets-3.0.0_macosx_bug_15908.patch
patch -p0 <
../kicad/patches/wxwidgets-3.0.0_macosx_soname.patch
patch -p0 <
> On Oct 29, 2014, at 11:21 AM, Adam Wolf wrote:
>
> Hi folks,
>
> Attached is a patch from the latest revision of KiCad to add a patch in the
> patches/ directory suitable for building wxwidgets 3 on OS X 10.10
> (Yosemite). It does not add it to any build scripts in our tree per Bernhard.
On 11/6/2014 11:32 AM, Adam Wolf wrote:
> Alternatively, what do folks think about packaging the libraries as a
> dmg? The insides of the DMG would have the folder with the content, and
> a link to copy them to their library location in their home directory,
> or for all users.
This makes sense t
> On Nov 6, 2014, at 9:32 AM, Adam Wolf wrote:
>
> Alternatively, what do folks think about packaging the libraries as a dmg?
> The insides of the DMG would have the folder with the content, and a link to
> copy them to their library location in their home directory, or for all users.
>
> I
Alternatively, what do folks think about packaging the libraries as a dmg?
The insides of the DMG would have the folder with the content, and a link
to copy them to their library location in their home directory, or for all
users.
I think I like this better, and will be starting work on it shortly
Hi folks,
After the patch last night, I have been able to have a few people test my
packages.
The top issues reported:
1) I don't actually have the pdf docs in the docs/ portion of the package.
I adjusted the link in the Readme to point directly to the
documentation on kicad-pcb.org, and a
Le 06/11/2014 12:02, LordBlick a écrit :
> In response to a message written on 06.11.2014 10:58, from jp charras:
>> ZONE_CONTAINER::Outline() returns m_Poly, which is a pointer to a
>> CPolyLine, which contains polygons (zone outlines: main outline and
>> holes)
>> -- Jean-Pierre CHARRAS
>
> Than
In response to a message written on 06.11.2014 10:58, from jp charras:
ZONE_CONTAINER::Outline() returns m_Poly, which is a pointer to a
CPolyLine, which contains polygons (zone outlines: main outline and holes)
-- Jean-Pierre CHARRAS
Thanks for info, but I have no idea, what I can make with
"
In response to a message written on 06.11.2014 09:22, from jp charras:
Wayne and I are thinking the main (the only one) purpose of this python
plugin is to allow import of footprint libraries coming from an other
EDA tool,
not to create a new footprint wizard (There is already a more powerful
pyt
Le 03/11/2014 14:14, LordBlick a écrit :
> Hello,
> I'm going to make some GUI zone manager in python, so I've made some
> review. I've found useful methods for areas:
> zone.ClearFilledPolysList() # Clear fill
> zone.BuildFilledSolidAreasPolygons(pcb) # Fill with project rules
> zone.HitTestInside
Le 05/11/2014 23:53, Nick Østergaard a écrit :
> 2014-11-05 23:40 GMT+01:00 LordBlick :
>> In response to a message written on 03.11.2014 15:14, from Jean-Samuel
>> Reynaud:
>>>
>>> Hi All,
>>>
>>> I wrote few months ago an extension to be able to write in python a
>>> footprint library plugin.
>>>
44 matches
Mail list logo
