Re: Carbon -> Cocoa

On 22. Aug 2018, at 19:40, Alastair Houghton wrote: > Are they? kqueue() supports monitoring of fds, Mach ports and timers, so > there’s really no reason that CFRunLoop would have to spawn a background > thread just to monitor some file descriptors. As far as I can tell, the > current CFRunLoo

Re: Carbon -> Cocoa

On 18. Aug 2018, at 20:19, Stephane Sudre wrote: > Regarding the complexity of porting from C++ Carbon to Cocoa, there's > also the important question of what your minimum OS target is. > > Maybe one of the reasons why you kept a Carbon version alive so long > is that the application needs to kee

Re: Carbon -> Cocoa

On 16. Aug 2018, at 13:54, Casey McDermott wrote: > I am curious, are there other developers on this list working on conversions > from C++ Carbon to Cocoa? > > If so, how is it going? I've worked on a few in previous jobs, it was definitely a lot of work, but most of that was due to the lack o

Re: is there a way to determine if an NSButton is toggleable ?

> On 20. Aug 2018, at 12:04, Guillaume Laurent > wrote: > > Hi all, > > > For a custom UI I’ve had to write a custom control deriving from NSButton, > which highlights itself in a special way on mouse-over. In the method which > does the highlighting, I check if the button’s state is eithe

Re: Carbon -> Cocoa

Sent from my iPhone > On Aug 22, 2018, at 10:40, Alastair Houghton > wrote: > >> On 22 Aug 2018, at 17:53, Jens Alfke wrote: >> >>> On Aug 21, 2018, at 8:33 AM, Alastair Houghton >>> mailto:alast...@alastairs-place.net>> wrote: >>> >>> So, for instance, it’s not so good on macOS or iOS if

Re: Carbon -> Cocoa

> On Aug 22, 2018, at 10:40 AM, Alastair Houghton > wrote: > > Well, yes and no. If the network library works that way, it’ll fire its > callbacks on the background thread, which makes life awkward if you’re > interacting with the UI Then you write glue around the callbacks that dispatches

Re: Carbon -> Cocoa

On 22 Aug 2018, at 17:53, Jens Alfke wrote: > >> On Aug 21, 2018, at 8:33 AM, Alastair Houghton > > wrote: >> >> So, for instance, it’s not so good on macOS or iOS if its event dispatcher >> is based on select(), (e)poll() or kqueue() because what you really

Re: Carbon -> Cocoa

> On Aug 21, 2018, at 8:33 AM, Alastair Houghton > wrote: > > So, for instance, it’s not so good on macOS or iOS if its event dispatcher is > based on select(), (e)poll() or kqueue() because what you really want on > macOS/iOS is for the event dispatch to go via CFRunLoop; if it doesn’t, >