I'm trying to create a very, very simple QuickTime viewer in Cocoa.
I create a new Application, add QTKit and Quicktime frameworks, and
drag a QuickTime Movie View into the main window.All is well if I
run now (although the movie view is blank).
Going back into Interface Builder, I sele
Bah, yes, I missed Michael Ash's correct answer at the end of
yesterday's digest.Setting the window backing store to "buffered"
fixed the control drawing and even a coupe of other interface issues I
hadn't realized were related.
Thanks to everyone for your he
addSubview:ctl];
[aWindow makeKeyAndOrderFront:nil];
[NSApp run];
return 0;
}
Clearly I'm missing something critical here (and "artistic talent"
isn't what I'm looking for). What important step am I missing to make
the event loop handle the drawing of my win
ckbox should keep toggling the value of
the checkbox and updating the screen, right? I don't have to do
anything special to turn this on, or implement the drawing myself?
--Christopher Kempke
On May 3, 2008, at 8:47 PM, Kyle Sluder wrote:
On Sat, May 3, 2008 at 7:08 PM, Christopher Kempke
<
doesn't even turn blue.
--Christopher Kempke
On May 3, 2008, at 3:10 PM, Nathan Kinsinger wrote:
On May 3, 2008, at 3:42 PM, Christopher Kempke wrote:
Then I draw the window with:
[iWindow makeKeyAndOrderFront:nil];
And run it as a modal dialog with:
[
g" some event the system needed, but no go. I don't have
mouseAnything: handlers on the checkboxes; in fact, I'm not even
subclassing them.
I'm guessing I've missed a step, something that provides the context
flush and the throb heartbeat. Anyone care to take pit
I'm working on some code for a client, whose users (handicapped
children, mainly) are using non-standard mousing devices. These are
(often literally) single-switch input devices: there's no notion of
position with them at all, basically just a mouse button sans actual
mouse. (On-scree
