On 21.01.2016 13:06, "Torsten Hüter" wrote:
> Hi,
>
> Lorenzo:
>
> Sorry, perhaps I've expressed it not correctly in my latest mail, I've just
> written down my subjective impressions, while working on the code, that are
> mostly rhetoric questions.
>
>>> Stackless coroutines:
>>>
Hm, is this really something we want to get into? Nice to remove the
dependency, but when something breaks in the future, do we have any/many
developers who can support x86 assembly code?
I really think that if we're going to have to support this, it should be
something conceptually simpler,
Hi Chris!
I am a bit short on time, currently, but will test your code asap
next week, I hope. Thanks for taking care about that!
On 2016-01-21 04:44, Chris Pavlina wrote:
> - Hotkeys that are *not* handled by the main hotkey code (for example,
> menu keys like Alt+F to call up the File menu)
Le 21/01/2016 04:44, Chris Pavlina a écrit :
> There is an old bug that people turned up while testing my new hotkey
> editor, attached is a patch that fixes it. This patch pokes into the
> main hotkey handling code, so I really want as many people to test it as
> possible - it's a relatively
Hi,
Lorenzo:
Sorry, perhaps I've expressed it not correctly in my latest mail, I've just
written down my subjective impressions, while working on the code, that are
mostly rhetoric questions.
>> Stackless coroutines:
>> -
>>
>> * Relative easy to handle, because based
Hi,
This patch replaces boost::context with a small library called
libcontext (derived from boost::context sources). It drops the
dependency on boost for the cost of one additional header file and cpp
file (taking inspiration from ClipperLib).
I've tested the new context switching code on Linux,
Lorenzo Marcantonio writes:
> OTOH I never did that on Win32/64 so maybe it's totally undependable to work
> :D
> Isn't there some MSDN article on doing that?
On windows, fibers can be used, and seem to work well. On most other
platforms, ucontext can be used (only
On Wed, Jan 20, 2016 at 11:58:56PM +0100, "Torsten Hüter" wrote:
> * It's very tricky to get stackful implementations to run stable. Any small
> fault results in a crash or deadlock.
What's strange in that? When doing pointers even small faults give you a crash
(if you are lucky :D).
> * The
There is definitely no way to do that in wxwidgets, any and all keys
that are received generate wxEVT_CHAR_HOOK, which I am receiving. There
may be a way to do it in X11, I don't know, but it would require
significant system-specific bodgery.
Also it'll tick people off, since if they've
Hi Tom,
thanks for your point of view - I'm guessing I've missed that you're working
already on your variant of boost::context. This is of course a feasible way.
I'm not the biggest fan of that either, because the (low level) assembler code
has to be maintained, tested on all platforms, but
Hi, Chris!
On 2016-01-21 15:16, Chris Pavlina wrote:
> There is definitely no way to do that in wxwidgets, any and all keys
> that are received generate wxEVT_CHAR_HOOK, which I am receiving. There
> may be a way to do it in X11, I don't know, but it would require
> significant system-specific
On 21.01.2016 15:03, Chris Pavlina wrote:
> Hm, is this really something we want to get into? Nice to remove the
> dependency, but when something breaks in the future, do we have any/many
> developers who can support x86 assembly code?
>
Concerning the support: I can do that, but there is
On 21.01.2016 15:20, Lorenzo Marcantonio wrote:
> On Thu, Jan 21, 2016 at 09:03:59AM -0500, Chris Pavlina wrote:
>> Hm, is this really something we want to get into? Nice to remove
>> the dependency, but when something breaks in the future, do we
>> have any/many developers who can support x86
Regression fixed in 6505, feel free to continue testing :)
On Thu, Jan 21, 2016 at 12:05:51PM +0100, jp charras wrote:
> Le 21/01/2016 04:44, Chris Pavlina a écrit :
> > There is an old bug that people turned up while testing my new hotkey
> > editor, attached is a patch that fixes it. This
Interestingly this regression seems to be older, a bisect indicates it
dates all the way back to 6479 (specifically 6478.1.1, as 6479 was a
merge). I'm surprised nobody has found that yet! Working on fixing it.
On Thu, Jan 21, 2016 at 12:05:51PM +0100, jp charras wrote:
> Le 21/01/2016 04:44,
On Thu, Jan 21, 2016 at 09:03:59AM -0500, Chris Pavlina wrote:
> Hm, is this really something we want to get into? Nice to remove the
> dependency, but when something breaks in the future, do we have any/many
> developers who can support x86 assembly code?
boost::context is broken anyway so
On 21 January 2016 at 13:42, Tomasz Wlostowski
wrote:
> Hi,
>
> This patch replaces boost::context with a small library called
> libcontext (derived from boost::context sources). It drops the
> dependency on boost for the cost of one additional header file and cpp
>
Fair enough, and it's nice to fix the boost issue. I suppose if support
ever becomes an issue we can consider replacing it _then_.
On Thu, Jan 21, 2016 at 03:21:41PM +0100, Tomasz Wlostowski wrote:
> On 21.01.2016 15:03, Chris Pavlina wrote:
> > Hm, is this really something we want to get into?
On Thu, Jan 21, 2016 at 03:21:41PM +0100, Tomasz Wlostowski wrote:
> Have a look at the discussion between Lorenzo, Kristian and Torsten.
> Emulating coroutines with threads can only bring more problems.
Fully agree. The boost::context is more or less an ad-hoc setjmp/longjmp
so it should work as
Hi,
Am 21.01.2016 um 14:42 schrieb Tomasz Wlostowski:
> I've tested the new context switching code on Linux, OSX (El Capitan) &
> Windows (all OS 32-bit and 64-bit Intel). Supported compilers are GCC
> and Clang.
Wouldn't that kill all non-Intel platforms? IIRC there are a number of
people
On 21.01.2016 17:34, Simon Richter wrote:
> Hi,
>
> Am 21.01.2016 um 14:42 schrieb Tomasz Wlostowski:
>
>> I've tested the new context switching code on Linux, OSX (El
>> Capitan) & Windows (all OS 32-bit and 64-bit Intel). Supported
>> compilers are GCC and Clang.
>
> Wouldn't that kill all
On 21.01.2016 17:34, Simon Richter wrote:
> Hi,
>
> IIRC there are a number of
> people running KiCad on ARM based systems,
Patch for 32-bit ARM (tested on a raspberry pi) attached.
Tom
>
>Simon
>
>
>
> ___
> Mailing list:
Hi Mark,
I was going to create a more fancy external tools section akin to the
made with kicad pages.
did you get a chance to add a section to kicad site for external tools?
thank you
Maurice
On 15/12/2015 00.34, easyw wrote:
Hi Mark
It is not a kicad feature, in fact it doesn't
even run
Hi Tomasz
This sounds promising, but I just have a small comment reading this. I
have not yet tested the patces, and I won't have time until... maybe
next week.
But is it your intention to use F9? That is currently assigned to the
switch to legacy canvas in pcbnew.
Nick
2016-01-21 23:30
On 21.01.2016 23:50, Nick Østergaard wrote:
> Hi Tomasz
>
> This sounds promising, but I just have a small comment reading this. I
> have not yet tested the patces, and I won't have time until... maybe
> next week.
>
> But is it your intention to use F9? That is currently assigned to the
>
Hi,
any objections or problems with this patch so it didn’t get applied yet?
Or, did it just get lost in some inboxes…
Regards,
Bernhard
> On 17 Jan 2016, at 22:00, Bernhard Stegmaier wrote:
>
> Hi,
>
> current mainline pinch-to-zoom support on OS X only works with
26 matches
Mail list logo