Hi Bernhard,
I looked around through the application bundle you posted and had some
questions about the proposed layout. It seems there is some arbitrary
placement of files in the bundle. I know it ultimately doesn’t matter to most
users as long as it runs and behaves properly but it doesn’t
Sent from my iPad
On Oct 2, 2014, at 12:58 PM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
Yes, I didn’t do anything about documentation yet.
It should be pretty easy to add if there is a way to copy/fetch/build it from
CMake and put it to the bundle - just like the templates,
Hi all,
I finally had a chance to build and try out the new all-inclusive OS X
application bundles and I’ve encountered a couple of issues that tend to reduce
the usability a bit for me.
First, an observation unrelated to the new bundles. I noticed with mainline
builds on OS X, some of the
” there is possibly a way to set the application icon
of window dynamically using wxWidgets.
Something to try… I guess behavior is the same on Linux/Windows, so the might
als benefit.
Regards,
Bernhard
On 04.10.2014, at 09:30, Garth Corral gcor...@abode.com wrote:
Hi all,
I finally had
is the same on Linux/Windows, so the
might als benefit.
Regards,
Bernhard
On 04.10.2014, at 09:30, Garth Corral gcor...@abode.com wrote:
Hi all,
I finally had a chance to build and try out the new all-inclusive OS X
application bundles and I’ve encountered a couple of issues
wxWidgets.
Something to try… I guess behavior is the same on Linux/Windows, so the
might als benefit.
Regards,
Bernhard
On 04.10.2014, at 09:30, Garth Corral gcor...@abode.com wrote:
Hi all,
I finally had a chance to build and try out the new all-inclusive OS X
application
On 04.10.2014, at 09:30, Garth Corral gcor...@abode.com wrote:
Hi all,
I finally had a chance to build and try out the new all-inclusive OS X
application bundles and I’ve encountered a couple of issues that tend to
reduce the usability a bit for me.
First, an observation unrelated
On Oct 6, 2014, at 5:39 PM, Andy Peters de...@latke.net wrote:
Hi, guys -- I have been doing daily builds on OS X, and I haven't had any
build issues. Now, I did build and install the various prerequisites (glew,
whatnot). Do recent builds use what's installed on my system, or does the
On Oct 10, 2014, at 3:13 PM, Bernhard Stegmaier stegma...@sw-systems.de
wrote:
I noticed the caching problem about 1 year ago when I played around with the
retina setting in the Info.plist for KiCad.
I had built KiCad and launched it = non retina settings (OK, was not
correctly
No.
On Oct 12, 2014, at 3:01 PM, Nick Østergaard oe.n...@gmail.com wrote:
So are you able to reproduce now?
2014-10-12 23:44 GMT+02:00 Garth Corral gcor...@abode.com:
This is not new; I saw it as far back as 5151. I didn’t correlate it with
any sort of launch order, though, and I wasn’t
Hi, guys.
After the recent eeschema dialog commit, my build of wxFormBuilder won’t allow
me to do anything with dialog_eeschema_options_base.fbp. It will open it just
fine, but after that I can’t use the UI; clicking on anything does basically
nothing. Just prior to this commit I was able
.x branch (also tried the 3.4.2 and
3.5.0 tags) which should be roughly 3.5.x.
Garth
On Oct 16, 2014, at 9:48 AM, Brian Sidebotham brian.sidebot...@gmail.com
wrote:
On 16 October 2014 17:30, Garth Corral gcor...@abode.com wrote:
Hi, guys.
After the recent eeschema dialog commit, my build
the same problem.
Best Regards,
Brian Sidebotham.
On 16 October 2014 17:56, Garth Corral gcor...@abode.com wrote:
Thanks for the quick reply.
Yes, already tried a sample of files; 1.11, 1.12 and 1.13 files open and
seemingly work just fine. This is the only file that I’ve had
Here’s my thoughts from an outsiders perspective.
Using proper version numbers is definitely the right way to go. Using commit
numbers is a horrible way to version a project in my opinion. Overlapping
numbers aside, the commit numbers are arbitrary and have no meaning with
respect to the
I agree with all points here, with one exception and one caveat.
The exception is that it will not work well with git (not an issue here). Git
commit IDs are not ordered and trying to use them as versions is a world of
pain. You’ll just have to trust me on that.
The caveat is that if you’re
On Oct 20, 2014, at 10:15 AM, Nick Østergaard oe.n...@gmail.com wrote:
2014-10-20 19:00 GMT+02:00 Garth Corral gcor...@abode.com:
I agree with all points here, with one exception and one caveat.
The exception is that it will not work well with git (not an issue here).
Git commit IDs
Hi all,
I have a set of changes that I've been maintaining locally for my kicad builds
that add support for trackpad gestures for panning and zooming on OSX, and
generally improving the usabilitiy of a trackpad or mousewheel with kicad on
this platform.
In trying to clean these up to be less
whether to include it with the other patches. In the mean time I’ll see
if I can dig up a trac bug that goes with this.
Garth
wxWidgets-3.0.0_scrolledwindow.patch
Description: Binary data
On Oct 23, 2014, at 7:26 AM, Wayne Stambaugh stambau...@verizon.net wrote:
On 10/22/2014 2:39 PM, Garth
Hi guys,
I have a a few questions for someone more familiar with the code than me.
Mostly about preferences, but also one random question that has me scratching
my head, bearing in mind that I’m not a C++ guy. I’ll start with that one.
Is there a reason that WX_VIEW_CONTROLS coerces it’s
off of
EDA_DRAW_PANEL_GAL as they are in EDA_DRAW_PANEL.
Thanks, again,
Garth
On Oct 27, 2014, at 1:44 AM, Maciej Sumiński maciej.sumin...@cern.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/27/2014 04:00 AM, Garth Corral wrote:
Hi guys,
I have a a few questions
I just stumbled across a tiny nit in wxwidgets-3.0.0_macosx.patch.
The following change omits the ‘y’ of ‘overlay’ in the object file name.
@@ -17792,6 +17792,9 @@
monodll_osx_cocoa_notebook.o: $(srcdir)/src/osx/cocoa/notebook.mm
$(MONODLL_ODEP)
$(CXXC) -c -o $@ $(MONODLL_OBJCXXFLAGS)
Hi, all
I’ve pushed a branch containing some changes that I use to make kicad more
livable for me on OS X. This is mostly for Apple Magic Trackpad users, but I’d
be curious to hear from mousewheel users on OS X, or even Linux and Windows
users if they were inclined to try out these changes.
];
^ ~~~
Any insights to this? I don't know enough objc to know what's going on here.
On Fri Oct 31 2014 at 10:45:59 AM Garth Corral gcor...@abode.com wrote:
Hi, all
I’ve pushed a branch containing some changes that I use to make kicad more
livable
.
It not only makes panning more OSX like, but also is a great usability
improvement (at least on OSX where nowadays all mice/trackpads do have x/y
scrolling capability).
Regards,
Bernhard
On 31.10.2014, at 18:45, Garth Corral gcor...@abode.com wrote:
Hi, all
I’ve pushed a branch
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
it. From the screen
shot it looks like you are using OSX. If that is the case, then I will
need one of the OSX developers to test this for me.
On 11/6/2014 1:41 PM, Garth Corral wrote:
If you inadvertently select the Hotkeys sub-menu (not an item within it)
from the Preferences menu of any
, and fixes the problem (tested with rev. 5249).
Regards,
Bernhard
On 06.11.2014, at 20:25, Bernhard Stegmaier stegma...@sw-systems.de wrote:
I can check on OSX…
On 06.11.2014, at 20:19, Wayne Stambaugh stambau...@verizon.net wrote:
On 11/6/2014 2:01 PM, Garth Corral wrote:
Yes, sorry, OS
Hi, it’s late so maybe I’m just confused, but the newly added yosemite patch
appears to add a patch that would patch the intended file, rather than doing
the patching itself.
=== added file 'patches/wxwidgets-3.0.2_macosx_yosemite_webview_webkit.mm.patch'
---
it won't affect Windows or Linux! :)
Unfortunately, I can't take a look at this until Monday.
Adam Wolf
Cofounder and Engineer
WL
On Sat, Nov 8, 2014 at 2:27 AM, Garth Corral gcor...@abode.com
mailto:gcor...@abode.com
mailto:gcor...@abode.com mailto:gcor...@abode.com wrote
Interesting. When I had replied in the past that I was unable to reproduce
this, I had been building with a local patch that set macosx-version-min to
10.7 for everything. When I read this I tried building again without that
patch and sure enough, red blob. When I rebuilt with version-min
I agree with Bernhard here. Putting this at the same level as the kicad.app
bundle presumes that everyone will install the entire Kicad directory from the
dmg. I, for one, simply install the kicad.app bundle directly in
/Applications.
All the work that Bernhard did was aimed, I thought, at
Comments inline
On Nov 18, 2014, at 5:15 AM, Adam Wolf adamw...@feelslikeburning.com wrote:
Well, folks, I guess I can put them inside of kicad.app, but I'm not really
sold on it.
0) To reiterate, I'm suggesting including the help in the dmg, but not inside
the kicad.app. The
If I get a chance this weekend I’ll try out your changes to
download_boost.cmake. I think I’m one of the last holdouts still using it to
build boost. This is my preference for the very reasons you state; I get to
control what’s in it. Especially important if you’re making binaries for use
On Feb 17, 2015, at 5:05 PM, Maciej Sumiński maciej.sumin...@cern.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Andy,
In GAL mode there are no scrollbars by design, it is not a Mac OS X
issue. Do users miss them?
No. In fact I’ve disabled them for the default canvas
Using PYTHON_SITE_PACKAGE_PATH is documented as being for this purpose, and it
works on OS X because the libraries end up in the application bundle and all
the paths are set up properly during the build and packaging.
From Documentation/compiling/build-config.txt:
…
PYTHON_SITE_PACKAGE_PATH
Hi, Nick
There were a couple of things that prevented me from requesting a merge. The
first was simply that it had little to no testing on other than OS X, and I
wanted to get more flight time on other platforms and pointing devices to make
sure it behaves well.
The other thing that I can
your
issues.
Garth
On Feb 19, 2015, at 9:47 AM, Bob Gustafson bob...@rcn.com wrote:
OK Garth/Bernard
I will do the 'merge' with the current head and give it another try.
Bob G
On 02/19/2015 11:06 AM, Garth Corral wrote:
Thanks, Bernhard.
Bob, at one point I updated Documentation
:
2015-02-19 5:10 GMT+01:00 Garth Corral gcor...@abode.com
mailto:gcor...@abode.com:
Hi, Nick
There were a couple of things that prevented me from requesting a merge.
The first was simply that it had little to no testing on other than OS X,
and I wanted to get more flight time
: If I don't see the General Settings in Preferences, I don't see how.
Lets see what happens at the end of my make.
Bob G
On 02/19/2015 12:16 PM, Garth Corral wrote:
Bob, you shouldn't need to merge anything. Yes, it's a few revisions
behind the trunk but there's nothing in those commits
Thanks, Bernhard.
Bob, at one point I updated Documentation/compiling/mac-osx.txt on that branch.
It should have the additional things you need. There’s an additional patch
for wxWidgets and another configuration flag to pass to cmake. After that, as
Bernhard said, there’s a configuration
, but to me it seems like this was just a switch
in behaivour of using zooming for scroll or having to hit ctrl or
shift (depinding on what mode was set in settings). It does not seem
to break any behaviour I usually expect.
2014-11-05 9:18 GMT+01:00 Garth Corral gcor...@abode.com:
Thanks
regardles of setting it is like it is zooming
way too much. When I just zoom one pinch I can't see my board. But on
my normal branch it works fine.
2015-01-10 18:23 GMT+01:00 Garth Corral gcor...@abode.com:
Thanks very much for trying this out, Nick. To be honest, it’s been so long
since I used
toolbar in the 3D view window.
2015-01-11 19:40 GMT+01:00 Garth Corral gcor...@abode.com:
Hi, Nick. Thanks for the feedback. I’m know there are some differences with
3d panning zooming that could potentially be an issue, but I’m a little
confused, though. When you say pinch, do you mean
needs to know where
it is installed before you can use it either by installing wxPython into
your python library path, adding the path programmatically during python
scripting initialization, or using PTYHONPATH.
On 2/15/2015 6:39 PM, Garth Corral wrote:
I build wxPython as part of my kicad
that it will be instaled on the system, and I
think that’s wrong.
Garth
On Feb 15, 2015, at 4:16 PM, Wayne Stambaugh stambau...@gmail.com wrote:
On 2/15/2015 7:06 PM, Garth Corral wrote:
Well, yes, you’ve sort of explained the problem. Unless wxPython is on the
library path or using PYTHONPATH it isn’t
I’m pretty sure you do not understand what I’m saying.
On Feb 15, 2015, at 4:41 PM, Wayne Stambaugh stambau...@gmail.com wrote:
On 2/15/2015 7:27 PM, Garth Corral wrote:
I think perhaps we’re having a miscommunication. I don’t think it’s
thin ice at all to build a version of a dependency
Hmm… So, unless I’m missing something, the new wxPython version check isn’t
ever going to work for me. I don’t have wxPython installed as part of my
system install so importing wxversion is always going to fail unless I point it
to my wxPython that I build as part of my kicad builds. Anyone
selection initialization only happen when you
configure your build with KICAD_SCRIPTING_WXPYTHON=ON.
On 2/15/2015 6:30 PM, Garth Corral wrote:
Hmm… So, unless I’m missing something, the new wxPython version check isn’t
ever going to work for me. I don’t have wxPython installed as part of my
stambau...@gmail.com wrote:
On 2/15/2015 7:42 PM, Garth Corral wrote:
I’m pretty sure you do not understand what I’m saying.
Perhaps you are right. To better understand how you would use CMake to
ensure the the correct version of wxPython is somewhere on you system
and gets installed along
On Mar 14, 2015, at 11:47 AM, Wayne Stambaugh stambau...@gmail.com wrote:
As you all know we are currently working towards a stable release. I
need to get and idea of what open items are left before I declare a
feature freeze. Here is the list of things I know about:
* Environment
Not sure what causes it, have’t looked. It isn’t anything you need to worry
about, though. When the build system bundles the module it doesn’t bundle it
as an egg anyway, so that file isn’t needed. That shouldn’t be fatal. Is it?
Garth
On Mar 10, 2015, at 2:15 PM, Andy Peters
dependency. Everyone has plenty of warning so if
you depend on this to build dependencies on your platform, now is the
time to start working on what ever dependency builders you need.
On 2/25/2015 1:47 PM, Garth Corral wrote:
I do use it but I'm not opposed to removing it if that's what you want
out tonight's nightlies to make sure
they're still affected.
Adam Wolf
On Sun, Feb 22, 2015 at 6:36 PM, Garth Corral gcor...@abode.com wrote:
Yeah, not shipped with OS X. It would be something that was built.
Presuming that the new build configured exactly like the old build it
would
I do use it but I'm not opposed to removing it if that's what you want. It
does still seem to work and is convenient if you don't want to use installed
dependencies. I can just as easily move that to a script, though.
Garth
On Feb 25, 2015, at 10:30 AM, Bernhard Stegmaier
dependency. Everyone has plenty of warning so if
you depend on this to build dependencies on your platform, now is the
time to start working on what ever dependency builders you need.
On 2/25/2015 1:47 PM, Garth Corral wrote:
I do use it but I'm not opposed to removing it if that's what you
is your build machine/cluster?
Regards,
Bernhard
On 22 Feb 2015, at 21:12, Garth Corral gcor...@abode.com
mailto:gcor...@abode.com wrote:
I can only speculate, but by the looks of that stack, I’m going to guess
that somewhere in the pixman rendering code there is conditionally compiled
I can only speculate, but by the looks of that stack, I’m going to guess that
somewhere in the pixman rendering code there is conditionally compiled
instruction extensions, such as SSE*, that your cpu does not support. The
nightly builds probably compile this in based on some configuration
that comes with OS X? If not, I installed it
with brew. I can uninstall it and reinstall it, and capture that log.
Let me know.
Adam Wolf
On Feb 22, 2015 5:47 PM, Garth Corral gcor...@abode.com
mailto:gcor...@abode.com wrote:
More interesting would be the build log for pixman which
Sorry for being so silent, folks. I'll try to send a summary later tonight
with my take on these changes and the impediments to getting them in.
Garth
On Feb 24, 2015, at 11:17 AM, Nick Østergaard oe.n...@gmail.com wrote:
True, but it is quite some time ago, although not a first
On Feb 24, 2015, at 2:33 PM, Garth Corral gcor...@abode.com wrote:
Sorry for being so silent, folks. I'll try to send a summary later tonight
with my take on these changes and the impediments to getting them in.
Garth
On Feb 24, 2015, at 11:17 AM, Nick Østergaard oe.n...@gmail.com wrote
Okay, I munged things in my builds to point to uninstalled dependencies without
USE_OSX_DEPS_BUILDER. I still need to script up these builds but that's
outside the scope of this. You may now count me in the I don't use it camp.
Garth
On Feb 25, 2015, at 2:17 PM, Garth Corral gcor
It seems like option #1 is the saner option.
If I’m understanding the change, once the variables are edited they become
configuration variables. Typical precedence for configuration is usually
something like, command line - environment - local config files - global
config files, from highest
Sigh, I only replied to Nick.
Begin forwarded message:
From: Garth Corral gcor...@abode.com
Date: April 2, 2015 at 11:57:03 AM PDT
To: Nick Østergaard oe.n...@gmail.com
Subject: Re: [Kicad-developers] Bob's Mac Usability Problems
Thanks, Nick. If you can point me to a build of this I
On Apr 25, 2015, at 9:41 PM, Blair Bonnett blair.bonn...@gmail.com wrote:
Hi all,
I've been going through the code removing redundant conditionally compiled
blocks for versions of wxWidgets before 3.0 as per the 'Conversion to
wxWidgets 3.0' section of the roadmap [1]. For the most
This plan to deprecate the old diode type seems… uh... poorly thought out.
Yanking these out from under everyone and every project in exiistence and then
sending out a message that says, “hey, guess what I did?” doesn’t seem like the
best way to handle this. It is most certainly not the way
-library/issues/153, a great
initiative taken by Kerusey.
Regards,
Carl
On Fri, Apr 24, 2015 at 7:21 PM, Garth Corral gcor...@abode.com
mailto:gcor...@abode.com wrote:
This plan to deprecate the old diode type seems… uh... poorly thought out.
Yanking these out from under everyone
Hi, Adam. Sorry I hadn’t looked at this previously, I’ve not seen this issue.
I likely won’t have a chance to look at this until late today at the earliest,
but just a quick glance makes me suspect a deployment target issue. I don’t
have a system on which to verify at the moment, but I don’t
of 10.10, this will compile in the
fchmodat call. Subsequently linking kicad with the 10.7 deployment target
would likely give the errors you’re seeing. The deployment target for boost
needs to match kicad.
Garth
On Apr 27, 2015, at 8:56 AM, Garth Corral gcor...@abode.com wrote:
Hi, Adam
The diagonal panning is the issue I found. As Andy points out, the reverse
scrolling is configurable in system preferences. This was added to OS X
expressly to accommodate the trackpad.
Garth
On Apr 8, 2015, at 2:47 PM, Adam Wolf adamw...@feelslikeburning.com wrote:
Additionally, the
It's a wxWidgets bug for which we have a patch.
Garth
On Apr 8, 2015, at 3:45 PM, Andy Peters de...@latke.net wrote:
On Apr 8, 2015, at 3:21 PM, Garth Corral gcor...@abode.com wrote:
The diagonal panning is the issue I found. As Andy points out, the reverse
scrolling is configurable
merge’ seems to bring me up to date with the product branch.
Garth
On Apr 5, 2015, at 2:04 PM, Garth Corral gcor...@abode.com wrote:
As I said, merging up to 5571 was fine; all the changes look sane. Merging
just 5572 after that introduces the changes listed, which is not correct
-3.0.0_macosx_magnify_event.patch file ?
You could save the r5571 merged file and then build and test that.
I think you are pretty close!
Have fun
Bob G
On 04/05/2015 02:44 PM, Garth Corral wrote:
Thanks, Wayne. To be honest I’m still trying to figure things out, both
with this merge and with bazaar
On Apr 4, 2015, at 8:15 AM, Bob Gustafson bob...@rcn.com wrote:
Testing report on this nightly build:
Application: kicad
Version: (2015-04-03 BZR 5572)-product Release build
wxWidgets: Version 3.0.2 (debug,UTF-8,compiler with C++ ABI 1002,GCC
4.2.1,STL containers,compatible with 2.8)
Is it just me or did this commit clobber a bunch of files it probably shouldn’t
have?
Not being super familiar with bazaar I’m not quite sure what I’m seeing.
For example, if you browse the code to Documents/compiling/mac-osx.txt in
launchpad it claims that the latest rev is 5572, but the
On Apr 5, 2015, at 1:13 AM, Nick Østergaard oe.n...@gmail.com wrote:
2015-04-05 10:11 GMT+02:00 jp charras jp.char...@wanadoo.fr
mailto:jp.char...@wanadoo.fr:
Le 05/04/2015 06:02, Garth Corral a écrit :
Is it just me or did this commit clobber a bunch of files it probably
shouldn’t have
will
try to fix it.
On 4/5/2015 5:01 AM, Garth Corral wrote:
Yes. Thanks, Nick. Sorry, I should have been more clear.
I only noticed this, though, when I merged trunk into my branch and got
a bunch of diffs that didn’t seem right. There were diffs that
seemingly wanted to revert changes
-i686.exe
Nick
P.S. you sent this only to me, but I think it contain way too much
information to miss the list.
2015-04-02 20:57 GMT+02:00 Garth Corral gcor...@abode.com:
Thanks, Nick. If you can point me to a build of this I will do what I can
to look into the issues reported by Wayne
On Jun 22, 2015, at 11:02 AM, Wayne Stambaugh stambau...@gmail.com wrote:
On 6/22/2015 1:55 PM, Andy Peters wrote:
On Jun 22, 2015, at 10:47 AM, Wayne Stambaugh stambau...@gmail.com wrote:
On 6/22/2015 1:45 PM, Andy Peters wrote:
On Jun 22, 2015, at 8:58 AM, Tomasz Wlostowski
+kicad-developers
Hoping you meant for this to go to the list.
On Jun 24, 2015, at 10:41 AM, Andy Peters de...@latke.net wrote:
On Jun 24, 2015, at 10:27 AM, Garth Corral gcor...@abode.com wrote:
Regardless of any wxWidgets issues, shouldn't this dialog be modal anyway?
Garth
Regardless of any wxWidgets issues, shouldn't this dialog be modal anyway?
Garth
On Jun 24, 2015, at 3:03 AM, Johannes Maibaum jmaib...@gmail.com wrote:
I’m pretty sure that is OSX only. At least it does not happen on my Arch
Linux machine.
I just filed a bug report, as I was not able
the changes.
On 6/11/2015 3:24 PM, Garth Corral wrote:
I think that can go. Though it looks like there’s some code in
osx_fixbundles.sh that ostensibly migrates kiface modules inside the
bundle, that code looks out of date and inert. Perhaps Bernhard has
some insight into what that’s supposed
and there in some old CMake code, but IMHO
it can just be deleted with every reference to it.
Regards,
Bernhard
On 11 Jun 2015, at 21:24, Garth Corral gcor...@abode.com
mailto:gcor...@abode.com wrote:
I think that can go. Though it looks like there’s some code in
osx_fixbundles.sh
While we’re on the topic. There are other places where hotkeys are less than
optimal on OS X. For example, F11 and F12 are taken for OS functions and never
reach kicad, so selecting the canvases has to be done through the menus.
Conversely, Cmd-C in kicad launches the calculator, so you
On Jul 1, 2015, at 12:22 PM, jp charras jp.char...@wanadoo.fr wrote:
Le 01/07/2015 20:38, Garth Corral a écrit :
While we’re on the topic. There are other places where hotkeys are
less than optimal on OS X. For example, F11 and F12 are taken for OS
functions and never reach kicad, so
wrote:
Le 01/07/2015 20:38, Garth Corral a écrit :
While we’re on the topic. There are other places where hotkeys are
less than optimal on OS X. For example, F11 and F12 are taken for OS
functions and never reach kicad, so selecting the canvases has to be
done through the menus
While poking at function keys in response to the earlier thread about, uh,
function keys. I stumbled on a crash caused by switching to the default canvas
from the default canvas. I was only able to to repro this when I performed the
switch (whether by menu or key) immediately after startup,
scripting widely available.
I need to check the mac scripting builds, do they allow to run commandline
scripts ? (not using the console, I mean).
Adam: thanks for maintaining the OSX side!,
Garth Corral wrote:
Hi, Adam. Funny you should ask that now. I just noticed that some changes went in recently
On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.com wrote:
On 7/1/2015 4:17 PM, Garth Corral wrote:
The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for
kicad users. There are many such issues in kicad where OS X specific issues
must be worked around
On Jul 4, 2015, at 2:02 PM, Garth Corral gcor...@abode.com wrote:On Jul 1, 2015, at 2:31 PM, Wayne Stambaugh stambau...@gmail.com wrote:On 7/1/2015 4:17 PM, Garth Corral wrote:The Cmd-C issue may well be a wxWidgets bug, but it is still an issue for kicad users. There are many such issues in kicad
On Jun 22, 2015, at 10:54 AM, Andy Peters de...@latke.net wrote:
On Jun 22, 2015, at 5:00 AM, Johannes Maibaum jmaib...@gmail.com wrote:
Hey OSX devs,
And I just came across another minor UI glitch in pcbnew: When running the
DRC, the dialog
window loses focus to the main window
Hi, Adam. Funny you should ask that now. I just noticed that some changes
went in recently that completely breaks python scripting on OS X. I haven’t
had a chance to look too deeply at it, but it looks like a check was added on
the return of wxversion.select(), which was likely always
On Jul 2, 2015, at 10:42 AM, jp charras jp.char...@wanadoo.fr wrote:
Le 02/07/2015 18:04, Garth Corral a écrit :
On Jul 2, 2015, at 12:37 AM, jp charras jp.char...@wanadoo.fr wrote:
Le 01/07/2015 22:21, Garth Corral a écrit :
On Jul 1, 2015, at 12:22 PM, jp charras jp.char
On Jul 2, 2015, at 12:37 AM, jp charras jp.char...@wanadoo.fr wrote:
Le 01/07/2015 22:21, Garth Corral a écrit :
On Jul 1, 2015, at 12:22 PM, jp charras jp.char...@wanadoo.fr
wrote:
snip
The issue relative to Ctrl / Cmd is not clear for me.
Is it just the name Ctrl which should
On top of that, the hotkeys list is mostly wrong on OS X in that it shows Ctrl-
as the modifier key when in fact it is Cmd- on OS X.
Garth
On Jun 30, 2015, at 10:43 PM, Nick Østergaard oe.n...@gmail.com wrote:
On a side note: Please note that the right click context menu shows
the
Looks like the OS X install is trying to copy the nonexistant cvpcb.app into
the main bundle, killing the build.
Patch attached
kicad_CMakeLists.txt.patch
Description: Binary data
smime.p7s
Description: S/MIME cryptographic signature
___
/11/2015 4:16 AM, Garth Corral wrote:Looks like the OS X install is trying to copy the nonexistant cvpcb.app into the main bundle, killing the build.Patch attached___Mailing list: https://launchpad.net/~kicad-developersPost to : kicad-developers
the stable release :)
Adam Wolf
On Thu, May 21, 2015 at 2:24 PM, Garth Corral gcor...@abode.com wrote:
Hi, Orson. This is not the controversial set of changes to which you
refer, it is only the subset that does pinch-to-zoom.
It is 100% conditionally compiled so will be inert unless
.
Scrollbars are not a problem, as I did not manage to enable them for OS
X in GAL canvas.
Regards,
Orson
On 05/21/2015 07:33 PM, Garth Corral wrote:
I’m not going to flog the dead trackpad horse again, but could we at least
get my pinch-to-zoom changes in? I committed this separately from
Nice job, Adam. It was a good crowd and a happy coincidence that your talk was
back-to-back with another KiCad talk. It was nice to meet you and Matthew in
person as well as your family, especially the little guy.
Garth
On May 19, 2015, at 8:18 AM, Adam Wolf adamw...@feelslikeburning.com
On Jul 7, 2015, at 10:53 AM, jp charras jp.char...@wanadoo.fr wrote:
Le 05/07/2015 23:39, Garth Corral a écrit :
On Jun 22, 2015, at 10:54 AM, Andy Peters de...@latke.net wrote:
On Jun 22, 2015, at 5:00 AM, Johannes Maibaum jmaib...@gmail.com wrote:
Hey OSX devs,
And I just came
1 - 100 of 127 matches
Mail list logo
