> On Oct 24, 2019, at 5:16 PM, James Walker via Cocoa-dev
> wrote:
>
> On 10/24/19 3:57 PM, Rob Petrovec via Cocoa-dev wrote:
>>> On Oct 24, 2019, at 4:50 PM, Stephane Sudre wrote:
>>>
>>> On Fri, Oct 25, 2019 at 12:38 AM Rob Petrovec via Cocoa-dev
>>> wrote:
If its a ranty bug
>> One of the problems the Mac has is OLD crap software build on legacy
APIs, seeing the black & white Watch Icon makes me want to vomit.
>> I’m thankful Apple is prepared to force laggards, who want to keep Mac
software back in the last century, quit the platform.
Yep, they are very effective at
On 10/24/19 8:45 AM, Ray, Jeffrey R. {Jeff} (AFRC-630) via Cocoa-dev wrote:
I have a multi-platform OpenGL app (most code is c++, a tiny bit is Obj-C++).
It switches between windowed and full screen mode by having an allocated-once
window, and an allocated-and-destroyed full screen that comes
I have a multi-platform OpenGL app (most code is c++, a tiny bit is Obj-C++).
It switches between windowed and full screen mode by having an allocated-once
window, and an allocated-and-destroyed full screen that comes and goes as
needed.
This worked correctly under Xcode 4. Due to local
On 10/24/19 3:57 PM, Rob Petrovec via Cocoa-dev wrote:
On Oct 24, 2019, at 4:50 PM, Stephane Sudre wrote:
On Fri, Oct 25, 2019 at 12:38 AM Rob Petrovec via Cocoa-dev
wrote:
If its a ranty bug report, which apparently happens a lot, it goes into a
black-hole never to see the light of day
> On Oct 24, 2019, at 4:50 PM, Stephane Sudre wrote:
>
> On Fri, Oct 25, 2019 at 12:38 AM Rob Petrovec via Cocoa-dev
> wrote:
>> If its a ranty bug report, which apparently happens a lot, it goes into a
>> black-hole never to see the light of day if it doesn’t just get closed right
>> off
On Fri, Oct 25, 2019 at 12:38 AM Rob Petrovec via Cocoa-dev
wrote:
> If its a ranty bug report, which apparently happens a lot, it goes into a
> black-hole never to see the light of day if it doesn’t just get closed right
> off the bat. So try to keep opinions & criticisms out of it. Just the
> On Oct 24, 2019, at 4:01 PM, Gabriel Zachmann via Cocoa-dev
> wrote:
>
>>>
>>>
>>>
>>> https://developer.apple.com/account/#/feedback-assistant
>>>
>>> https://developer.apple.com/account/#/forums
>>
>>
>> Good luck with that. I've been using OSX/macOS since the Panther days and
>>
>>
>>
>>
>> https://developer.apple.com/account/#/feedback-assistant
>>
>> https://developer.apple.com/account/#/forums
>
>
> Good luck with that. I've been using OSX/macOS since the Panther days and
> quite frankly I don't think Apple cares.
Occasionally, I send a bugreport via
> On Oct 24, 2019, at 11:46 AM, Sandor Szatmari via Cocoa-dev
> wrote:
>
> Is there a flag I can set in Xcode to squash these?
If these are compiler (Clang) warnings, then:
1. Right-click on a warning in the Xcode issues browser
2. Select "Show In Log" — this should take you to the build
> On Oct 24, 2019, at 7:47 AM, Richard Charles via Cocoa-dev
> wrote:
>
> Before September 2014 the developer documentation was excellent. Excellent
> online documentation with downloadable and searchable pdfs. Now all pdfs are
> gone and online documentation is like art on display in a
Migrating some code to 64 bit…
Making a pit stop at Xcode 9.4.1/32 bit as the last stable 32 bit build.
40+ projects with multiple targets make for a lot of i386 is deprecated noise.
I’d like to silence these warnings while I straighten out actual issues.
Is there a flag I can set in Xcode
>>I think you missed a step when learning Cocoa. A great way to start is
with something like Cocoa Programming for Mac OS X by Aaron Hillegass
No, working through the Hillegass books was the first thing we did- first
the current edition for Swift, then the previous one for Objective-C. We
also
>
> This is how you move towards a solution.
>
> https://developer.apple.com/account/#/feedback-assistant
>
> https://developer.apple.com/account/#/forums
Good luck with that. I've been using OSX/macOS since the Panther days and
quite frankly I don't think Apple cares.
I've submitted dozens of
> On Oct 24, 2019, at 7:04 AM, Turtle Creek Software via Cocoa-dev
> wrote:
> Is there a way to fix this stuff?
> For the rest, Apple really needs to listen to developers more.
Some random thoughts.
Before September 2014 the developer documentation was excellent. Excellent
online
>
> These days, Cocoa is pretty much the only tool that creates native
> software for Apple hardware.
There's iOS too which has a lot more devs (outside from Apple) than macOS.
No wonder Apple is "merging" the two SDKs (SwiftUI, Catalyst, etc).
___
On Oct 24, 2019, at 6:08 AM, Turtle Creek Software via Cocoa-dev
wrote:
> Is there a way to fix this stuff?
…
> For the rest, Apple really needs to listen to developers more.
This is how you move towards a solution.
https://developer.apple.com/account/#/feedback-assistant
TurtleSoft has shipped software built with 3 different programming tools:
Excel, HyperCard and CodeWarrior C++/PowerPlant. We started but abandoned
projects using 4 others: FileMaker, Omnis, Serius Developer and Think
Pascal/C++/TCL. There were another 6 app-development tools that we bought
and
Yeah, good points. I solved it better by overriding my NSCollectionViewItem
subclass’ preferredContentSize and setting it from my
itemForRepresentedObjectAt dataSource function when I get access to the item.
Cheers,
Arved
> On 2019-10-22, at 03:41, David Duncan wrote:
>
>
>
>> On Oct 21,
19 matches
Mail list logo
