Bing,
That's not the point. The point is a program has to be ready to handle the
possibility of corrupted, truncated or fragmented data.
Writing a client-server program, particularly at the socket level, is not easy
for that very reason. If you fail to take the possibilities into account, you
On May 28, 2010, at 11:04 AM, Kevin Wojniak wrote:
>> *4)** **I **can't call the printing code*
>>
>> I know, the printing code calls me. But other platforms don't work like
>> this. I eventually used Core Printing and the Cocoa dialogs by sub-classing
>> and faking out NSPrintPanel. Is there a
Apologies for the newbishness of this question, but I've been away
from IB for quite some time (and never went very deep with it in the
first place).
Let's say I want to have two NSButtons (called 1 and 2) that will
cause an NSTabView to switch to tab 1 and 2, respectively. I don't
want
I've got an OpenGL application that implements its own widgets for
text entry and display. The application is a Cocoa application. When
in windowed mode, it uses a subclass of NSView for its GL context. In
full-screen mode, it captures the display with CGL.
I need to support internationa
