racket/collects/mred/private/wx/cocoa
Matthew Flatt dc912ee6de third attempt to fix 64-bit Lion hidden-window problem
After all the previous attempts, the problem seems almost trivial:
although Apple documents `NSAnyEventMask' as the constant #xFFFFFFFF,
it's actually NSUIntegerMax (and the difference matters in 64-bit
mode).

Merge to 5.2.
2011-10-10 15:48:30 -06:00
..
agl.rkt
bitmap.rkt
button.rkt
canvas.rkt implement 'border style for `panel%' 2011-08-13 07:00:51 -06:00
cg.rkt
check-box.rkt
choice.rkt
clipboard.rkt
colordialog.rkt
const.rkt third attempt to fix 64-bit Lion hidden-window problem 2011-10-10 15:48:30 -06:00
cursor.rkt
dc.rkt
dialog.rkt
filedialog.rkt Revert "another attempt to fix the 64-bit Lion hidden-window problem" 2011-10-10 15:38:42 -06:00
finfo.rkt
font.rkt
frame.rkt cocoa: fix `show #f' on already unshown frame shows it briefly 2011-10-08 16:47:19 -06:00
gauge.rkt
gc.rkt
group-panel.rkt
image.rkt
init.rkt
item.rkt
keycode.rkt
list-box.rkt cocoa, gtk: enable auto list-box% horizontal scrollbars 2011-09-10 11:14:52 -06:00
menu-bar.rkt cocoa: fix application about handler 2011-09-03 10:35:55 -06:00
menu-item.rkt
menu.rkt
message.rkt
panel.rkt implement 'border style for `panel%' 2011-08-13 07:00:51 -06:00
platform.rkt cocoa: make grow-box-spacer zero-width for 10.7 2011-10-04 12:59:18 -06:00
pool.rkt
printer-dc.rkt Revert "another attempt to fix the 64-bit Lion hidden-window problem" 2011-10-10 15:38:42 -06:00
procs.rkt cocoa: make grow-box-spacer zero-width for 10.7 2011-10-04 12:59:18 -06:00
queue.rkt third attempt to fix 64-bit Lion hidden-window problem 2011-10-10 15:48:30 -06:00
radio-box.rkt fix keyboard navigation (all platforms) 2011-09-30 13:44:24 -06:00
README.txt
slider.rkt
sound.rkt
tab-panel.rkt fix keyboard navigation (all platforms) 2011-09-30 13:44:24 -06:00
types.rkt
utils.rkt cocoa: make grow-box-spacer zero-width for 10.7 2011-10-04 12:59:18 -06:00
window.rkt fix keyboard navigation (all platforms) 2011-09-30 13:44:24 -06:00

Allocation rules:

 * Use `as-objc-allocation' when creating a Cocoa object. When the
   resulting reference becomes unreachable, the Cocoa object will be
   released.

 * Use `with-autorelease' in atomic mode around calls that autorelease
   and where the release should take effect immediate. Do not create
   an autorelease pool except in atomic mode.

 * Other autoreleased objects may end up in the root pool installed by
   "pool.rkt". The root pool is periodically destroyed and replaced;
   call `queue-autorelease-flush' if you need to encurage replacement
   of the pool. If you need to use an object htat might be autoflushed,
   be sure that you're in atomic mode.