I see that Apple's Mac OpenGL mailing list is no more. Not too surprising, as OpenGL is now deprecated, but it will be a long time before I can move to Metal.

For reasons that we need not get into, sometimes my code disassociates an NSOpenGLContext from an NSView and destroys the context, and at some later time creates a new NSOpenGLContext and sets the same NSView as its drawable. The weird problem is that at the moment that -[NSOpenGLContext setView:] is called, the view draws the image that was last drawn by the deceased NSOpenGLContext. Any idea how to prevent that? I came up with a somewhat distasteful way: Just before destroying the old NSOpenGLContext, I set its surface order to -1, so that if it shows up again, it's hidden behind my window.

Many thanks for starting this group, and being so responsive.

Thanks! Joined.

Hello, I've just joined on Ann's recommendation to the Carbon-dev list - thanks, Ann. And thanks to Jens for making this place.

It would be awesome to still have somewhere to ask Carbon questions.

By request I’ve created two new subgroups, carbon and jxa.

I vote for having a separate carbon sub-group. There may not be many of us, but the latest discussion shows there's still interest in carbon, and it's great to have a specific place we can go to for help and/or consolation.

Also, since it's quite possible some of the carbon folks haven't stumbled across the info about apple-dev.groups.io, I'm posting this to the Apple Carbon group as well. The more people who know that Apple is discontinuing their discussion lists, the better.

Ann

But it's also very low volume...

On the other hand, it's easier to fand something when everything is relevant and without unrelated topics.

If there are more than a dozen people, maybe we should have a separate carbon topic.

igor

On 5 Jul 2017, at 20:06, James Walker <jamesw@...> wrote:

On 7/5/2017 11:19 AM, Luther Baker wrote:

I've been on that list for a bit now and from what I can see, discussions cover a pretty wide range. It is a specialty topic and I think the audience would largely be the same for the various possible lists.

That said, if other related lists exist on lists.apple.com, I'd be all for mirroring the same structure so as to minimize confusion. I'm just not aware of another such list.

Also, that list doesn't get pounded so I think you'd be safe starting with coreaudio-api and waiting for someone "in the know" to ask for more granularity.

Regarding mirroring the structure: Apple has a "QuickTime-API" list, which lately has had a fair amount of discussion of AV Foundation. Maybe just add a "video" list?

Some of Apple’s lists have odd names that are quite hard to figure out without grokking a lot of history. e.g. the apple-cdsa list.

I’d vote for list names as generic as possible. So audio, video, security, etc. Or audio-api etc if you think it’d help.

Chris

I've been on that list for a bit now and from what I can see, discussions cover a pretty wide range. It is a specialty topic and I think the audience would largely be the same for the various possible lists.

That said, if other related lists exist on lists.apple.com, I'd be all for mirroring the same structure so as to minimize confusion. I'm just not aware of another such list.

Also, that list doesn't get pounded so I think you'd be safe starting with coreaudio-api and waiting for someone "in the know" to ask for more granularity.

Regarding mirroring the structure:  Apple has a "QuickTime-API" list, which lately has had a fair amount of discussion of AV Foundation.  Maybe just add a "video" list?

On Wed, Jul 5, 2017 at 12:17 PM, Jens Alfke <jens@...> wrote:

> On Jul 4, 2017, at 9:49 PM, lutherbaker@... wrote:
>
> Would you mind creating something for Core Audio and Core MIDI?

Sure, that sounds like a great idea, especially as I occasionally do audio coding myself.

What about higher level APIs like AVFoundation? Do you think those should be on-topic for this list too, or should there be a separate list?

—Jens

On Jul 4, 2017, at 9:49 PM, lutherbaker@... wrote:

Would you mind creating something for Core Audio and Core MIDI?

Sure, that sounds like a great idea, especially as I occasionally do audio coding myself.

What about higher level APIs like AVFoundation? Do you think those should be on-topic for this list too, or should there be a separate list?

—Jens

Would you mind creating something for Core Audio and Core MIDI?

Maybe something akin to 

coreaudio-api@...

Thanks,
-Luther

On Jun 8, 2017, at 2:25 AM, Jeremy Hughes <moon.rabbit@...> wrote:

Those lists seem to be run by Apple - are they (especially swift-users) not also threatened by the mailing-list cull?

They’re run by the Swift open-source project, and they’re pretty high-priority as they’re the main way that people communicate, including the developers of Swift. Whereas lists.apple.com has been pretty much ignored by Apple for … at least five years? With periodic near-death experiences.

I’m confused about what is happening. As far as I know, the only list whose closure has been announced is xcode-users. Are Apple closing down all their mailing lists, or just xcode-users?

Only xcode-users as far as I know, but it wouldn’t make sense for them to close one list but not the others. It may just be that xcode-users is the only one where an Apple person decided to let the members know what’s going to happen.

Anyway, those lists have been on life support for years, and the listserv software they run is ancient. Groups.io has easily browsable archives, web forum access, wikis, calendars, and all the bells and whistles you could want. It seems like a much better home.

—Jens

On 8 Jun 2017, at 16:25, Jeremy Hughes <moon.rabbit@...> wrote:
the only list whose closure has been announced is xcode-users.

It does seem weird that they would cull the xcode-users group alone.

I can only imagine that they’re waiting to get back from WWDC before pulling the plug out of that whole rusty server in the basement.


Best


Phil
@sqwarq

On the end of this January, Apple mailing lists halted. So we had contact with Apple people. They did not understand or make action to recover MLs. They did not understand what happened. It took about 2 weeks to recover MLs.

So, most of us had an anxiety about Apple employee’s intelligence and operability.

We needed backup plan to communicate with. This ML seemed a good backup.


--
Takaaki Naganoya
maro@...
http://piyocast.com/as/

Those lists seem to be run by Apple - are they (especially swift-users) not also threatened by the mailing-list cull?

I’m confused about what is happening. As far as I know, the only list whose closure has been announced is xcode-users. Are Apple closing down all their mailing lists, or just xcode-users?

Jeremy

--

Can we have a Swift group?

Jeremy

--