Frame Meter In Quartz Debug For Mac

Posted on |

For Developers‎ > ‎Coding Style‎ > ‎

Cocoa Dos and Don'ts

Introduction

When writing code using Cocoa, there are rules to follow. Anything that uses Objective-C++ must of course follow the C++ guidelines. However, there are things in Cocoa that are more subtle than they look. Here are a few things to keep in mind.

Banned Practices

Const NSObjects

The use of const NSObjects is prohibited as it makes Clang unhappy. (This is enforced in the presubmit hooks.) See the Mac Clang page for more details.

Atomic properties

The use of atomic properties is prohibited. There are differences between how our compilers handle them, and since we don't need them anyway we don't use them. See the Mac Clang page for more details.

Tracking rects and raw NSTrackingAreas

Tracking rects are tricky to get right. Apple realized that, and in Mac OS X 10.5 introduced the NSTrackingArea object. Unfortunately, that is also difficult to get right, and has historically led to nasty crashes.
The use of -[NSView addTrackingRect:owner:userData:assumeInside:] is prohibited.
The use of raw NSTrackingAreas is prohibited.
You are required to use CrTrackingArea. Find it at ui/base/cocoa/tracking_area.h. There are currently (and unfortunately) lots of current usage of tracking rects and NSTrackingAreas. Please convert them as you encounter them.

YR DOIN IT RONG

There are spots of Cocoa that are tricky. Watch out.

Coordinate conversion

All code that manages views is required to be correct, and that correctness is more heavily tested when running under 'resolution independence' or 'HiDPI', where window coordinates are not the same as view coordinates. (Turn on resolution independence in Quartz Debug.app.)
Any time you need to compute window coordinates based on view coordinates, or vice versa, make sure you use the appropriate conversion calls (i.e. -convertRect:toView: and friends). There is a call for each data type and each conversion direction. Also, remember that views have both a -bounds and -frame. They are in different coordinate systems.
See http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/CocoaDrawingGuide/Transforms/Transforms.html for details.

The 'base' coordinate system

In doing coordinate conversion, you may run into methods on views that convert to and from the 'base' coordinate system. Those are almost certainly not what you are looking for. When talking about views, the 'base' coordinate system is referring to the raw backing pixels. If you need to precisely align to pixels, they are correct, but most of the time they do not do what you think they are doing.
(This problem is compounded by the references in methods on windows to the 'base' coordinate system, which is indeed the window coordinate system.)
See http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/6b989dcbb79e9ba/029eeb633c5287cc for details.

Zero-sized windows

The Mac's windowserver has issues with zero-sized windows, spewing tons of junk to the console, yet it's not immediately obvious when you resize them that it's a problem.
Ensure that you do not resize windows to be empty, either implicitly or explicitly.

The Quartz Compositor (which is part of the Mac OS X windowing system) determines how drawing appears in windows on the display. As you’ve seen, cre-ating and managing Quartz objects is a key aspect of Quartz programming. By understanding the Quartz memory management. Launch Quartz Debug and you should notice new options in the 'Tools' and 'Windows' menus. Should you like to undo the changes and go back to the stock Quartz Debug just type the following in Terminal (followed by Enter): defaults delete com.apple.QuartzDebug QuartzDebugPrivateInterface. A list of working and tested addons for World of Warcraft Wrath of the Lich King 3.3.5a! Download addons for your user interface, boss encounters, and more!

The XQuartz project is an open-source effort to develop a version of the X.Org X Window System that runs on OS X. Together with supporting libraries and applications, it forms the X11.app that Apple shipped with OS X versions 10.5 through 10.7.

Quick Download

DownloadVersionReleasedInfo
XQuartz-2.7.11.dmg2.7.112016-10-29For OS X 10.6.3 or later
X11-2.6.3.dmg2.6.32011-07-20For OS X 10.5.x (final Leopard release)

Important Info for 10.5 Users

Frame Meter In Quartz Debug For Mac Catalina

Frame Meter In Quartz Debug For Mac

OS X Software Updates have included some of the work done by the XQuartz project, but for various reasons, Apple cannot ship the latest and greatest version offered by the XQuartz site. Since the XQuartz X11 package clobbers Apple's X11.app, their software update will clobber the XQuartz X11 package. Because of this, you may experience conflicts after doing a Software Update from Apple. Please re-install the latest XQuartz X11 release for Leopard after installing a system software update to OS X 10.5.x Leopard.

Frame Meter In Quartz Debug For Mac Os

License Info

Frame Meter In Quartz Debug For Macbook

Mac

Frame Meter In Quartz Debug For Macbook Pro

An XQuartz installation consists of many individual pieces of software which have various licenses. The X.Org software components’ licenses are discussed on theX.Org Foundation Licenses page.The quartz-wm window manager included with the XQuartz distribution uses the Apple Public Source License Version 2.