I think this is just a short term issue (famous last words) until the
next stable release of wx. I haven't seen too many distros package 3.1
yet so I don't think we should make that transition until that happens.
Hopefully some time during v6 development we can make this transition
without too much pain and suffering.
I did see that there is already a stable point release (4.0.1) of the
Phoenix project so it looks like wxPython (Phoenix) will be in better
shape than the current situation.
On 02/09/2018 10:06 AM, Bernhard Stegmaier wrote:
> Worst part for macOS is that we still need the patched overlay stuff for the
> legacy canvases.
> There has been something added to master recently, but it unfortunately
> doesn’t work (it does, but is slow as hell).
> I would be surprised if this gets usable for 3.1.
> So, getting rid of legacy canvases (in pcbnew and eeschema) is probably the
> biggest step for also being able to use a stock wxWidgets an macOS.
> The remainder is more or less just “cosmetic” stuff that will eventually get
> fixed (hopefully)...
> wxPython is the next story then, as Adam said.
>> On 9. Feb 2018, at 15:37, Adam Wolf <adamw...@feelslikeburning.com> wrote:
>> Part of the issue with wx is that we are using a legacy version of
>> wxpython. I know there has been some motion towards getting the new
>> version of wxpython working with KiCad, but it does not seem like it
>> will be super easy. There is no real guarantee that the next version
>> of wx will work with the legacy/non-maintained version of wxpython
>> we're using.
>> I consider getting away from this legacy version of wxpython
>> relatively critical so we don't get in trouble--for instance, if some
>> new OS release doesn't work with the legacy wxpython.
>> Adam Wolf
>> On Fri, Feb 9, 2018 at 8:27 AM, Wayne Stambaugh <stambau...@gmail.com> wrote:
>>> On 2/9/2018 1:41 AM, Carsten Schoenert wrote:
>>>> Am 09.02.2018 um 01:35 schrieb Jeff Young:
>>>>> Any thoughts on patching wxWidgets for other platforms?
>>>> If you are talking about other Linux platforms then please do this in a
>>>> way the user hasn't to deal with changes to system folders, this isn't
>>>> really possible nor usable on systems which using package managers for
>>>> dealing with installed software. And I know only LFS (Linux from
>>>> Scratch) which hasn't a package manager.
>>>> And, please upstream any changes, if upstream don't want to accept your
>>>> changes they probably have strong and good reasons to not apply your
>>>> changes (at least for this specific released version).
>>> I second this motion. We really shouldn't be in the business of
>>> maintaining our own custom version of wxWidgets. I relaize macos is a
>>> problem child for wx but we should be helping ourselves by getting wx to
>>> accept and maintain any issues that have not already been fixed
>>> upstream. Hopefully the next release of wx will be a bit more usable on
>>> macos than the 3.0 branch and that the current situation of maintaining
>>> our own wx branch for macos is temporary.
>>> Mailing list: https://launchpad.net/~kicad-developers
>>> Post to : firstname.lastname@example.org
>>> Unsubscribe : https://launchpad.net/~kicad-developers
>>> More help : https://help.launchpad.net/ListHelp
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : email@example.com
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~kicad-developers
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp