P: Support for native full-screen mode on macOS

You are completely right. But I also don't think this is acceptable excuse for the biggest software development companies in the world. Sometimes companies get into sticky situations because of backwards compatibility - but we also see again and again from some of these companies that if there is enough will, anything is possible.

I'm just hoping that Adobe is still one of those companies that puts users above their convenience.

Considering Adobe purchased Macromedia the competition I find their approach very similar to a dictatorship, I'm surprised the European Union hasn't investetgated them. Our way or the highway isn't good enough, full screen mode is a standard OSX feature, please support it!

I am also a software developer and I concur with John. This is not as trivial as it sounds. In addition to the technical issues described above, they have to consider how this affects all their users, how it might limit their ability to introduce other features, how it makes the Mac and Windows versions diverge, etc.

We're all asking for this feature because we want it, so Adobe should give it the proper priority, but let's not trivialize the effort.

Finished?

Tone curve bug.
Unexplained slowdowns on some systems.
Slow web rendering.
Slow 5DIII response.
Auto CA improvements.
Auto tone makes big exposure errors.

And that's just the tip of the iceberg.

@Gaerraty: I'm not complaining that we have them! :)

Basically what I was trying to say is that they are not essential. And they are not even that good. This is a professional program that is for professional users. I dare say most of us will use these features for tinkering, but not for real work because if we make money with video or 3D, we will be using dedicated video or 3D software (I use Modo for 3D and FCPX for video)...

All I am saying is that in my eyes, the development time would have been better spent on features that benefit the core users on an everyday basis.

Since you aren't a software developer, and I am, I can tell you that this is actually not an "easy" needle to thread.

Lion /significantly/ changed certain pane/window interactions such that handling the requests for various screen resizes across mutliple monitors, virtual screens, various sleep modes, etc, is, to put it plainly, a nightmarish mess.

Apple has release several tweaks to the core display and window server stuff in the Lion timeframe to address some of these problems.

Software development is not just about fixing some obvious defect, but about managing how that fix changes all affected components across all supported configurations.

There will have to be a significant amount of rewrite and retest to fully support these new APIs to the level Adobe users expect. Rewriting is tricky, because you don't want to re-introduce old bugs, or introduce new ones, and yet you still have to make the new stuff work right. Consider for a moment that this is not an easy task, and one that takes time and planning to get right.

I'm afraid that, unless you have this background, you are not in the best position to assess the whole story. This is not a criticism, but a statement of fact.

@43542: Oh, and thanks for noting about VLC. I've missed the whole feature. It is really nice addition.

Surely. It would be odd if there weren't anything else to do.

I'm glad that there is discussion about this topic.

@4087053 Jay: Those are already finished. This option would take just a few lines of code.

Perhaps because about a thousand other things are more important, and therefore higher priority?