hout X.
> If the kicad binaries are not 2-way fat then there’s no reason the bundled
> libs should be either.
>
> Garth
>
>> On Feb 28, 2015, at 3:18 PM, Marco Serantoni
>> wrote:
>>
>> Wayne,
>> At the time we were in a timeframe where was ppc f
Wayne,
At the time we were in a timeframe where was ppc finishing his fading out, i386
in mid term, x86_64 was not already fully adopted.
KiFace work begin was forcing a migration from the old default behavior of
static linking to dynamic.
Now:
i386 fading/faded out completely.
Good Job Guys..
> On 24/feb/2015, at 06:58, Johannes Maibaum wrote:
>
> Hi Adam,
>
> I just tried your build, and it works like a charm. I'm now looking forward
> to regularly
> using the Kicad OSX nightlies. Again, thank you for all your effort improving
> the Kicad
> experience for OSX user
On 11/giu/2014, at 21:13, Dick Hollenbeck wrote:
> On 06/11/2014 02:07 PM, Dick Hollenbeck wrote:
>> On 06/11/2014 01:54 PM, Jean-Paul Louis wrote:
>>> Thank you Bernhard.
>>>
>>> I would much prefer to apply your patches to the last kicad BZR at least
>>> until someone
>>> from the dev team h
On 07/giu/2014, at 22:46, Jean-Paul Louis wrote:
Mac Keyboard has both HOME and END, you were probably referring to
compact/notebook one that requires the fn key.
Apple doesn’t hates no “button", just optimize the keyboard for common use and
documents how to use them.
I can assure as PC noteb
On 07/giu/2014, at 13:11, Nick Østergaard wrote:
Nick,
OSX has not menus icons by design, good hint.
wx-widgets ignores them too.
> Hello
>
> I am no an OSX user, but I know that OSX generally don't use these
> menu icons. It is also described in [1], see the section "Using Icons
> in Menus".
On 29/mag/2014, at 18:21, jp charras wrote:
> Le 29/05/2014 11:45, Bernhard Stegmaier a écrit :
>> Hi,
>>
>> build on OSX is broken since rev. 4895 (I guess)…
>> The include is not found because __DARWIN__ is not set. Moving the
>> include of glcanvas.h from the .cpp to the beginning of the
A lot more picky, you got correct, that have to be a bitwise comparation.
Being Cocoa UI API vectorial, misses pixel logical operations, the "erase"
made with XOR on the pixels has been substituted with a trasparent Overlay
that guests "immediate" draws, for immediate i mean "moving components or
On 29/mag/2014, at 20:44, jp charras wrote:
Jp,
Should be not mistakes ;)
> Le 29/05/2014 19:11, Bernhard Stegmaier a écrit :
>> Hi,
>>
>> oh, sorry for that… I have some other small changes in my local repository.
>> I guess that's why.
>
> I just need to be sure there was no mistake.
> A w
the machine/account itself.
>>
>>
>> Regards,
>> Bernhard
>>
>> On 23.05.2014, at 16:27, Jean-Paul Louis lou...@yahoo.com [kicad-users] <
>> kicad-us...@yahoogroups.com> wrote:
>>
>> Hi Bernhard,
>>
>> I use OS X 10.9.2 and I
jp, probably he wants an incremental DRC.
Could be usefully check and signalate the error during the drawing, such
kind of feature could avoid an feedback/reiteration phase.
--
Marco
On Mon, May 19, 2014 at 12:05 PM, jp charras wrote:
> Le 19/05/2014 10:55, Tomasz Wlostowski a écrit :
> > On
On 08/mag/2014, at 08:10, Dick Hollenbeck wrote:
> On 05/07/2014 02:17 AM, jp charras wrote:
>> Le 07/05/2014 05:07, Jean-Paul Louis a écrit :
>>> Hi Marco,
>>>
>>> I just finished building BZR4854 according to your instructions, and
>>> still kicad does not work properly on OSX.
>>>
>>> See s
On 08/mag/2014, at 20:52, Dick Hollenbeck wrote:
> On 05/08/2014 01:21 PM, jp charras wrote:
>> Le 08/05/2014 18:28, Jean-Paul Louis a écrit :
>>> Hi Developpers,
>>>
>>> I found a weird error that I never noticed before. The screenshot below
>>> was taken just after clicking on the last button
ow to modify the Finder app to see the /Library directory.
>>
>> My $0.02,
>> Jean-Paul
>>
>>
>> Sent from my Verizon Wireless 4G LTE smartphone
>>
>>
>> Original message
>> From: Marco Serantoni
>> Date:2014/
Adam,
I'm for /Library & ~/Library, first because they are coherent with the
enviroment and wxStandardPaths.
We have discussed about that with Wayne not much months ago, we agree from
much time about the correctness to use that class without reinvent the
wheel, the differences were about ::GetUserC
o the cmake.
> I need to learn more about the cmake.
>
> Jean-Paul
> AC9GH
>
> On Apr 30, 2014, at 6:18 AM, Marco Serantoni
> wrote:
>
> Jean-Paul,
> About missin kifaces, that was the reason why i've asked you to use r4835,
> that does that links.
>
> - Ab
on of Kicad.
> So they go use other CAD software like Eagle, GEDA, and many others that
> are nowhere near the performance
> of Kicad.
>
> Jean-Paul
>
>
> On Apr 28, 2014, at 4:46 PM, Marco Serantoni
> wrote:
>
>
> On 28/apr/2014, at 19:25, Jean-Paul Louis wrote:
| grep BZR
> #define KICAD_BUILD_VERSION "(2014-04-25 BZR 4830)"
> jean-pauls-mbp:Soft_Dev jean-paullouis$
>
> Will you help to fix this?
>
> Jean-Paul
>
>
>
>
> On Apr 28, 2014, at 8:26 AM, Marco Serantoni
> wrote:
>
>> realized
, but this time it is not enough (everything compiles fine
> on my machine).
> I see that you have already changed the conflicting define. Does it solve the
> problem? If so, I would suggest one more minor modification (in the
> attachment).
>
> Regards,
> Orson
>
&g
a distribution process for OS X users that
> cannot or do not want to build, but would like to use Kicad on OS X
> natively.
>
> Jean-Paul
>
>
> On Apr 27, 2014, at 8:25 PM, Marco Serantoni
> wrote:
>
>
> On 27/apr/2014, at 23:36, Dick Hollenbeck wrote:
>
> D
On 27/apr/2014, at 23:36, Dick Hollenbeck wrote:
>> Dick
>> I’m there, i wish ask to you and bug reporters to send a mail in CC directly
>> to me if there are urgent and important things about OSX.
>> I’ven always the time to read the Developer ML during my work peaks, sorry.
>>
>>> Marco (or
On 27/apr/2014, at 15:01, Marco Serantoni wrote:
Should be both fixed.
I’ve done a quick fix to the issue #1, please if responsible developer doesn’t
like they can reject or rework.
Jean-Paul please take a look.
I’ve Accepted the Dick hint to symbolic link kiface libraries to the owner
On 24/apr/2014, at 15:40, Dick Hollenbeck wrote:
I’m sorry for the late, but i’ven’t received any bug report about this issue.
There are two issues at the moment:
The first is probably caused by the update of the developer tools shipped the
11 April (Command Line Developer Tools 5.1.0).
The se
On 24/apr/2014, at 17:55, Dick Hollenbeck wrote:
Dick
I’m there, i wish ask to you and bug reporters to send a mail in CC directly to
me if there are urgent and important things about OSX.
I’ven always the time to read the Developer ML during my work peaks, sorry.
> Marco (or in his continued
Happy of that,
You are signalating a Known issue when using kicad.app.
There was a thread 2-3 months ago about it, this is the best we can do with
this code arrangement, this should disappear once k-way will be fully
deployed.
If you have suggestions/patches on how to fix it we will review it toget
Jean-Paul,
You got right, i forgot that.
Fixed
—
Marco
On 23/mar/2014, at 02:43, Marco Serantoni wrote:
>
> On 22/mar/2014, at 22:03, Jean-Paul Louis wrote:
>
> Jean-Paul,
> You choose the hard way, and the one i can’t control.
> You need only compiler, bzr and cmake d
On 22/mar/2014, at 22:03, Jean-Paul Louis wrote:
Jean-Paul,
You choose the hard way, and the one i can’t control.
You need only compiler, bzr and cmake downloaded from the respective sites and
follow the indication
in Documentation/compiling/mac-osx.txt
Libraries and dependencies are downloaded
On 22/mar/2014, at 07:00, Dick Hollenbeck wrote:
Here where was a couple of issues.
The pcb_plot_params_keywords i think is a multi platform issue that happens
only on scratch new checkouts using an high parallelism (like make -j12)
Doesn’t happens on not “fresh” rebuilds because we found the pr
make review).
Also please be aware that some paths will need an adjustment.
--
Marco
On Mon, Mar 17, 2014 at 6:03 PM, Adam Wolf wrote:
> (I agree with Marco.)
>
>
> On Mon, Mar 17, 2014 at 12:01 PM, Marco Serantoni <
> marco.serant...@gmail.com> wrote:
>
>> Jean-Pa
Obliusly a second .dmg with only libraries to avoid confusion and adding
the possibility for the user to be archived if needed.
--
Marco
On Mon, Mar 17, 2014 at 6:01 PM, Marco Serantoni
wrote:
> Jean-Paul,
> I don't agree with "Programs".
> Until now OSX has suppor
>
> I'm glad you agree that .pkg is not a good option. How do you suggest we
> get data into /Library/Application\ Support/kicad? Should we have users
> drag a folder into there?
>
> Adam Wolf
> Wayne and Layne, LLC
>
>
> On Mon, Mar 17, 2014 at 10:03 AM, Marco Seranton
t; libraries and leave the default libraries unchanged.
>> >
>> >>
>> >> What is the best route to do just that?
>> >
>> > You should be able use git to create your own branch form
>> > https://github.com/KiCad/kicad-library. The CMake installer
Your contribution is appreciated probably i'll ask to you two a bit more
Efforts for making the new icns files
Pleshanka,
Marco
> Il giorno 14/mar/2014, alle ore 13:49, Барановский Константин
> ha scritto:
>
> I not wanted and not want to make a problem, but I want to make a
> contribution in
On 14/mar/2014, at 20:00, Wayne Stambaugh wrote:
>>
>> The idea of keeping Kicad libs in Github is great, but if the
>> first-time-ever user has to set it up in some system config files or run
>> bash scripts (think of Windows users!), it will ruin his experience
>> (sorry for sounding Steve Job
I strongly agree with Tomasz, helping the user just firsts steps just after
the download is the key for a quick adoption.
When someone downloads Kicad for the first time is because have an idea in
mind that wish to trasfer in the reality or just to comparate its software
with the OpenSource one.
M
gt; Adam Wolf
> W&L
>
>
> On Thu, Mar 13, 2014 at 6:31 PM, Marco Serantoni
> wrote:
> I’m Working on it.
> Recently there was a compiler update (two days ago),
> And it becomes a lot more choosy and restrictive and affects a lot of
> projects.
>
> please ex
I’m Working on it.
Recently there was a compiler update (two days ago),
And it becomes a lot more choosy and restrictive and affects a lot of projects.
please execute before the building:
export CPPFLAGS="-Qunused-arguments"
clang: error: unknown argument: '-mno-fused-madd'
[-Wunused-command-li
Nobody has noticed that ohloh.net was pointing to old testing and not
product ? ;)
--
Marco
On Mon, Feb 24, 2014 at 9:02 AM, Lorenzo Marcantonio <
l.marcanto...@logossrl.com> wrote:
> On Sun, Feb 23, 2014 at 11:59:10PM +0100, Fabrizio Tappero wrote:
> > I would like to share with you a very rec
iff and lzma.h. Wxwidgets's
> configure says it finds everything it needs, but when it goes to build, it
> can't find my lzma.h.
>
> This is on a 10.9 machine, relatively vanilla, with homebrew.
>
> Adam Wolf
> Wayne and Layne LLC
> On Feb 26, 2014 9:13 AM, "M
Adam,
Perfect, your build is done correctly.
wxwidgets is build directly by wxpython the wxOverlay patch is already
included.
Which is your need and why you wish to change the configuration ?
--
Marco
--
Marco
On Wed, Feb 26, 2014 at 5:03 AM, Adam Wolf wrote:
> Hi folks,
>
> Working on inco
Nice work, really :)
--
Marco
On Thu, Feb 20, 2014 at 6:06 AM, Henner Zeller wrote:
> On 19 February 2014 17:30, Kaspar Emanuel
> wrote:
> > Thanks for this patch! I was working on a new schematic all day today
> > using the new dialogue and it felt super snappy. A joy to use!
>
> Thanks for
> - In other places in the code that has to do with redraws, there is
> some special handling with the USE_WX_OVERLAY macro. I can't really
> test this properly in my installation of wxWidgets, so I don't know if
> I always do what would be needed in this case.
>
Henner,
This is my code, for
On 08/feb/2014, at 13:57, Wayne Stambaugh wrote:
> Marco,
>
> Not a problem. Please keep in mind that downloading and building
> dependencies like wxPython or swig from source should be the last option
> even on OSX. Always use find_package() first to see if it is already
> installed on the sy
Sorry Wayne,
I apologize with you, wasn’t mine intention put dependencies on other platforms
nor change
the way other developers and other platforms wants to build their binaries.
This was an huge work propedeutic to others work, intentions are to take enough
advantage to fix it and have the tim
Sorry,
Was mine error.
There was a long work full of pitfalls, all those libraries and the related
libraries are needed by OSX to let him carry the external libraries
not provided to OS into the executable bundle and make it self-contained.
This is not required on other platforms, but was left g
Fabrizio,
Nice set, they looks much cleaver than older ones.
--
Marco
On Thu, Feb 6, 2014 at 12:17 AM, Fabrizio Tappero <
fabrizio.tapp...@gmail.com> wrote:
> Dear Jean-Pierre,
> since I believe you have not yet committed my previous icon patch, please
> neglect it and used instead this new se
ommunity libraries
> (I guess) probably it's a matter of including easy_python or pip in the
> build in the future. Anyway I believe
> it's a good thing, having the same as Brian built for windows.
>
>
>Good work! :)
>
>
> ---
> irc: ajo / mangelajo
> Migue
Sorry, I forgot to reply to all
Miguel,
As you can see i've committed the part to make possibile the linking of Kicad
also with dynamic linking and making binaries portable
(scripts/osx_fixbundle.sh )
I'm in those days working on wxPython, i'm confident to release a similar
mechanism for Python
erienced
> with the subject. I believe this has to end up with some speed up in KiCad.
>
> Regards,
> Orson
>
>
> On 01/14/2014 10:59 AM, Marco Serantoni wrote:
>
>> Only the warning: keep attention that boost::context doesn't support the
>> context switch fo
Only the warning: keep attention that boost::context doesn't support the
context switch for the vector registers
(mmx*/v*).
If needed i can help you to implement.
--
Marco
On Mon, Jan 13, 2014 at 7:48 PM, Vesa Solonen wrote:
> 13/01/14 10:04, Maciej Sumiński kirjoitti:
>
> > I fully support t
On 06/gen/2014, at 21:27, Maciej Sumiński wrote
>
> Thank you for the explanations. I expected that boost comes with KiCad to
> make building easier for some users, but I did not even think of bugs related
> to version of the library.
Many of the issues I had on OSX are related to to wrong com
Dick,
I’ve to support multiple processors,I’ve just ended to spit blood implementing
it in boost for PPC32 an PPC64 in asm to add support in boost::context. (
https://svn.boost.org/trac/boost/ticket/8266 ).
Now i’m building all for three platforms, then i’ll try to do a more extensive
testing of
Dick,
I was able to compile also the GIT plugin.
Now i’ve a couple of problems to show you
* i’ve a clean machine so i have the problem to populate the Library table with
my old legacy modules, could you implement an automatic “insert” of rows when
it is empty using the Library Paths or add a b
Sadly,
Despite was a great idea use -fvisibility the llvm compiler seems doesn’t like
this option.
So i’ve to disable it, sorry Dick was as good idea.
ld: bad codegen, pointer diff in ___cxx_global_var_init19 to global weak symbol
__ZN8wxStringD1Ev for architecture i386
clang: error: linker com
Nick,
I’ve listened your complain about the wrong result in version.h and therefore
in the kicad application title when you checkout a previous revision of the
code.
I personally found your patch functionally correct, if no one will disregard in
the next days with your patch I think we could pro
Fabrizio,
Since 2008 i maintain binaries for kicat at
http://www.mdx4.org/index.php?/categories/5-Kicad
On 07/nov/2013, at 20:08, Fabrizio Tappero wrote:
> Hello Guys,
> some people have been asking for the OS X distribution of KiCad. Can I
> please be directed to some webpage?
>
> thank you
As usual in those times i release of the OSX port, I’m shipping in this moment
the STABLE tree for ppc, i386 and x86_64 that should have resolved some issues.
Going to the Testing tree and the state of the Art,I’ve seen the improvements,
really a great job and I wish have some feedbacks from yo
I agree with Jean Pierre,
In OSX you need to have high rescalable icons (ICNS), is requested to
provide (application) icons starting from 512px passing by 256, 128, 32 and
16 pxs and is important have a good Alpha Channel, i prefer have SVG
masters to do this operations.
--
Marco
On Tue, Oct 29
Begin forwarded message:
> From: Marco Serantoni
> Subject: Re: [Kicad-developers] OSX Support for EESchema (still?)
> experimental?
> Date: 10 maggio 2013 18:48:13 GMT+02:00
> To: Travis Ayres
>
> I was thinking i was on the ML, is not a problem if i forward ?
>
On 06/dic/2012, at 20:58, Dick Hollenbeck wrote:
> On 12/06/2012 12:44 PM, Marco Serantoni wrote:
>> Sure Dick,
>> Seems that fseek returns 0L, as that is where the internal buffer points.
>> The setvbuff destroys the internal buffer and when is used the read call,
>
it out has almost no impact on
performance.
Hoping this makes now more sense,
--
Marco
On 06/dic/2012, at 19:17, Dick Hollenbeck wrote:
> On 12/06/2012 12:03 PM, Marco Serantoni wrote:
>> On 27/nov/2012, at 15:29, Dick Hollenbeck wrote:
>>
>> Dick,
>> Sadly it doe
On 27/nov/2012, at 15:29, Dick Hollenbeck wrote:
Dick,
Sadly it doesn't work, i'll just revert to the old code and add an #ifndef to
exclude the setvbuff call.
Cleaner and simpler :)
Marco
>
>> I know Dick, is "dirty" for this reason, but knowing that the problem is
>> more systemic
>> i've
I wish to discuss about my patch #3817, that comes to me from some
signalations of problems in cvpcb and i've applied that is a probably a
dirt workaround for a more deep problem that i wish to describe.
The code parsing the netlist does more or less this:
[Reads the header to identify the netlis
Miguel,
Is a well know problem you should add to CXXFLAGS
-D__ASSERTMACROS__
error is already defined in the OSX headers otherwise.
Please look to the instructions we have already done with jerry.
http://bazaar.launchpad.net/~kicad-testing-committers/kicad/testing/annotate/head:/Documentation/compi
On Mon, May 14, 2012 at 8:32 AM, Lorenzo Marcantonio <
l.marcanto...@logossrl.com> wrote:
> On Sat, May 12, 2012 at 04:59:58PM +0200, Marco Serantoni wrote:
> > - Not with CAIRO on windows, since
> http://trac.wxwidgets.org/ticket/14194 was closed 4-5 weeks ago and tests
>
On 10/mag/2012, at 15:22, Dick Hollenbeck wrote
>
> Will the real Jep please stand up who is Jep?
Is a friend of Godot :)
>
>
> Torsten, do you know about
>
>
> http://www.hackintosh.com
>
>
> Somebody I know is running the OSX stack under a VM on a Windows machine.
>
> This person
On 10/mag/2012, at 10:46, Torsten Hüter wrote:
Torsen,
I'm still stuck but i can wait, which is the deadline for the shipment of the
GAL in the trunk ?
I'm proposing this approach because is a viable way to start to redesign the
drawing code before GAL is ready.
I recall well that we have don
ows and show if we
can pass for this way to enhance kicad.
If someone has enough time, compiling CAIRO should also possible test how
performs its OpenGL backend on windows.
I wish do it, but i haven't a windows platform under my hands, so there is any
volunteer ?
On 08/mag/2012, at 06:16, Lorenzo Marcantonio wrote:
> On Mon, May 07, 2012 at 02:18:57PM -0500, Dick Hollenbeck wrote:
>> OSX
>
> OSX is handled in GRSetDrawMode (as it should be). GRSetColorPen uses
> MakeColour which only sets the alpha from the upper bits (are you referring
> to this?)
>
On Tue, May 8, 2012 at 8:01 AM, Dick Hollenbeck wrote:
>
> This means that we eventually, we'll no longer need all the wxT() stuff,
> since we
> basically never put anything but ASCII characters in those wrappers and to
> convert from an
> ASCII string to UTF8 is simply a matter of copying bytes
On 10/dic/2011, at 08:14, jean-pierre charras wrote:
> Le 10/12/2011 02:18, Martijn Kuipers a écrit :
>> Hi,
>> On Dec 9, 2011, at 8:51 PM, Marco Serantoni wrote:
>>
>>> Hi folks,
>>> I'm as usual doing my semestral build of Kicad, one is for Xmas
Hi folks,
I'm as usual doing my semestral build of Kicad, one is for Xmas.
I've noticed that icons were changed i wish to compliment with the author for
the enhancement, i appreciated the KDE style but i'm afraid that could be
confusing for operations like New, Open and Save that are usually code
On 27/nov/2011, at 23:44, Vladimir Uryvaev wrote:
>
>> So it is not clear to me that a function written by you for this purpose
>> would serve previously stated goals.
>>
>> If you are insistent on no exponents in the number, I am insistent on the
>> smallest files including trailing zero remova
at least two of whom
> are reading this use or want to use Kicad to design PCBs for it.
>
> One of my biggest fans is a Mac fan, which is how I ended up with a
> Mac, he'll be happy if it works reasonably on them too.
>
> Regards,
>
> Fred.
>
> On Tue, Jul 19, 2011
On 15/lug/2011, at 15.39, Fred Cooke wrote:
Fred,
About which version you are referring to, picked from where ?
And which test you have done ?
Cause is Know,
wx-widgets related vs XOR (un)support on OSX, workarounded with wxOverlay that
is not correctly implemented under wxCoccoa too.
ask to wx
On 28/gen/2011, at 18.46, Wayne Stambaugh wrote:
> I am pretty much done removing USE_WX_ZOOM and all of the unused code
Is ok for me :)
--
Marco
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad
On 12/gen/2011, at 22.00, Wayne Stambaugh wrote:
> On 1/12/2011 3:31 PM, Marco Serantoni wrote:
>>
>> On 12/gen/2011, at 00.41, Wayne Stambaugh wrote:
>> There are some problems with the refresh on pcbnew initially and zooming in
>> and out the screen remains completl
with some forced Refresh(), will impact on performace but
for me is GO.
Marco
> Marco,
>
> Thanks for taking a look a this on OSX. Let me know if you find any
> problems and I do my best to fix them.
>
> Wayne
>
> On 1/11/2011 6:37 PM, Marco Serantoni wrote:
>>
On 11/gen/2011, at 19.34, Wayne Stambaugh wrote:
Wayne, i had some problems with WX_ZOOM some time ago, expecially with
printing, there was some fixes of wxwidgets latelly, i'll compile and check it
on all 3 OSX main platforms ASAP.
Anyway i'm interested too to simplify the code and reuse the w
Seen,
Mercì Jean-pierre
On 12/nov/2010, at 19.53, jean-pierre charras wrote:
> Le 12/11/2010 19:06, Marco Serantoni a écrit :
>>
>>
>> On 12/nov/2010, at 11.02, Jerry Jacobs wrote:
>>
>> Jerry i'm working on it.
>
> I committed some changes (mainl
On 12/nov/2010, at 11.02, Jerry Jacobs wrote:
Jerry i'm working on it.
> [ 70%] Building CXX object cvpcb/CMakeFiles/cvpcb.dir/cvpcb.cpp.o
> /Users/jerry/Projects/kicad/testing/cvpcb/cvpcb.cpp: In member
> function ‘virtual bool WinEDA_App::OnInit()’:
> /Users/jerry/Projects/kicad/testing/cvpcb/
On 27/ott/2010, at 22.58, Wayne Stambaugh wrote:
>>
>> So why you don't cleanup that ?
>
> That was done a long time ago.
>
>> You have a rotten egg, is correct yell and trash it if nobody complains.
>
> This assumes that someone has the time to go back and get rid of it. Maybe
> publishing
On 27/ott/2010, at 21.55, Wayne Stambaugh wrote:
>>>
>> No, definitelly, i'm not proposing to create a custom internal scripting
>> language, and in case, the SCREEN is not the best place to start with.
>> I also think that bind command events is not a good way, being too much gui
>> tied you
On 26/ott/2010, at 21.10, Dick Hollenbeck wrote:
>> Indeed,
>> Here is the patch, let's chat :)
>
> Thanks for your patience, and willingness to accept feedback.
>
> We might need to wait a day or two for folks to comment.
>
> I know English is not your favorite language, but it would be easier
kicad-events.diff
Description: Binary data
On 26/ott/2010, at 20.54, Dick Hollenbeck wrote:
> On 10/26/2010 01:50 PM, Marco Serantoni wrote:
>> In those days i was thinking about to add an internal event generation for
>> some kicad classes.
>> Adding internal events at
In those days i was thinking about to add an internal event generation for some
kicad classes.
Adding internal events at wxAUIManager could be a good start to implement
"external frames" and utilities (plugins) , making possible plug-in new
functionalities and probably reorganizing some parts of
On Oct 20, 2010, at 12:18 AM, Martijn Kuipers wrote:
> Hi Devs,
>
> I just noticed that the overflow button in the about-menu crashes with
> accessing a null-pointer. Easy fix would be to just remove
> wxAUI_NB_WINDOWLIST_BUTTON from the line below in common/dialog_about_base.fbp
>
> name="s
On Oct 13, 2010, at 8:17 AM, Dick Hollenbeck wrote:
>
>> I wonder if it occurred to others - if the inch had been defined as 25.6
>> instead of 25.4/mm this
>> problem would have been quite different.
>
> I thought the inch was defined first.
>
>> I do think the inch will die out someday.
On Oct 11, 2010, at 6:09 PM, Alex G wrote:
>
> On 10/11/2010 06:41 PM, Marco Serantoni wrote:
>> Surelly, do you have an OpenGL printer or SVG writer ?
>>
> About the OpenGL printer:
> Setup a framebuffer any resolution you'd like, render whatever you need
> to
On Oct 11, 2010, at 4:40 PM, Alex G wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/11/2010 05:23 PM, Marco Serantoni wrote:
>> Alex,
>> The only issue i'm aware of is the #648289
> Marco,
>
> Here's the issue I'm referring
On Oct 11, 2010, at 5:17 PM, Alex G wrote:
>
>
> On 10/11/2010 05:54 PM, Marco Serantoni wrote:
>> I wish make the point we are at the moment, seen the number of newcomers.
>> We have 2 main platforms: Windows and Linux, there is also a third
>> platform at the
I wish make the point we are at the moment, seen the number of newcomers.
We have 2 main platforms: Windows and Linux, there is also a third platform
at the moment that is OSX.
The accelerated APIs on this platforms are provided by:
Linux: GTK/CairoLib
Windows: GDI+ / Direct2D
OSX: Quartz 2D (Cor
On Sun, Oct 10, 2010 at 4:49 PM, Alex G wrote:
>
> I never questioned kicad's decision to use wxWidgets. I do think,
> however, of the 3d-viewer crashing on non-nvidia cards or nvidia cards
> with nouveau. I can reproduce it 100%. Are these and similar sort of
> issues common with wx? Would it be
On Sun, Oct 10, 2010 at 11:35 AM, Vesa Solonen wrote:
> On Sat, 9 Oct 2010, Dick Hollenbeck wrote:
>
> We are essentially rewriting eeschema very soon.
>>
>
> Any plans going metric on the way? I know it doesn't actuallu matter much,
> but "now or never (tm)". Brainstorming ahead, is the wxWidge
On Thu, Oct 7, 2010 at 3:40 AM, Dick Hollenbeck wrote:
>
> It occurs to me that if you had the assignment operator in place for
> COMPONENT or copy constructor, you could simply assign to the containing
> component when seeing an "inherit" token using the base component.
>
> (component A
> (inhe
On Tue, Sep 28, 2010 at 10:49 PM, Alex G wrote:
> > I think we are reaching the point where we need a separate branch for
> > visual c++.
> I'm sorry to just jump in, but what was the problem with Blinded C++ in
> the first place?
> Is it not compiling? I wouldn't like to see kicad deviate from s
On 23/set/2010, at 21.50, Dick Hollenbeck wrote:
>>
>> We could use a "base library" that is referred from "specific parts library"
>> as "father" using its symbol like classes (inherance).
>> So who wants heavy libraries has its parts, who keeps its library light has
>> its part fallbacking to
On 23/set/2010, at 19.40, Wayne Stambaugh wrote:
>
> I don't see how aliases can be used for heavy libraries. Aliases do not have
> fields (unless you count the information in the document file) so you cannot
> assign different default or user specified field values to them. Once you add
> fiel
On 15/set/2010, at 19.51, Jonathan Stroud wrote:
Jonathan,
Sorry for the late response, i were in the middle of some adjustments of the
OSX code and i've commited the changes you suggested.
I'm waiting for feedbacks.
--
Marco
> I can fix this problem and check in a patch. I just discovered Ki
On 09/set/2010, at 22.46, Martijn Kuipers wrote:
Libraries should go in /Library/Application Support/kicad or in
$HOME/Library/Application Support/kicad
--
Marco
> I managed to create the DMG-files for kicad on OSX. Next I wanted to add the
> libraries, but where should they be stored?
> I w
100 matches
Mail list logo
