On 8/22/08 4:25 PM, Jason Coco said:
>It also appears that Leopard has added some support for this within
>AppKit itself... three new methods were added to NSView:
>
>-(BOOL)enterFullScreenMode:(NSScreen *)screen withOptions:
>(NSDictionary *)options;
>-(void)exitFullScreenModeWithScreen:(NSScreen
On Aug 22, 2008, at 2:46 PM, Charles Srstka wrote:
On Aug 21, 2008, at 10:02 PM, Ricky Sharp wrote:
(1) never ever ever capture the display when using AppKit.
This appears to be incorrect, as Apple seems to endorse and even
provides sample code for capturing the screen while using AppKit:
On Aug 22, 2008, at 2:13 PM, Charles Srstka wrote:
On Aug 21, 2008, at 10:02 PM, Ricky Sharp wrote:
Creating a non-movable, non-titled window is _trivial_. Just
create a tiny subclass and away you go. I do this myself, along
with following the guidelines of that technote.
Why would it b
Am 22.08.2008 um 05:31 schrieb Kyle Sluder:
. In my mind, I have a
choice: either make the control interface a standard OS X app,
allowing users the full functionality of the computer, or make a kiosk
app that runs on some stripped-down Linux distribution in single-user
mode. I still haven't
On Aug 22, 2008, at 15:46 , Charles Srstka wrote:
On Aug 21, 2008, at 10:02 PM, Ricky Sharp wrote:
(1) never ever ever capture the display when using AppKit.
This appears to be incorrect, as Apple seems to endorse and even
provides sample code for capturing the screen while using AppKit:
On Aug 22, 2008, at 3:13 PM, Charles Srstka wrote:
On Aug 21, 2008, at 10:02 PM, Ricky Sharp wrote:
Creating a non-movable, non-titled window is _trivial_. Just
create a tiny subclass and away you go. I do this myself, along
with following the guidelines of that technote.
Why would it b
On Aug 21, 2008, at 10:02 PM, Ricky Sharp wrote:
(1) never ever ever capture the display when using AppKit.
This appears to be incorrect, as Apple seems to endorse and even
provides sample code for capturing the screen while using AppKit:
http://developer.apple.com/documentation/Cocoa/Conc
On Aug 21, 2008, at 10:02 PM, Ricky Sharp wrote:
Creating a non-movable, non-titled window is _trivial_. Just create
a tiny subclass and away you go. I do this myself, along with
following the guidelines of that technote.
Why would it be necessary to make a subclass? Shouldn't it be possib
On Aug 21, 2008, at 8:31 PM, Kyle Sluder wrote:
On Thu, Aug 21, 2008 at 11:18 PM, Steve Christensen
<[EMAIL PROTECTED]> wrote:
The great majority of Mac applications do not run in kiosk mode so
for most
cases preventing window movement *is* wrong because you take
control away
from the user
Greetings, Mike,
I'm not sure when I have told anyone that they were outright wrong --
heaven knows, I've been wrong enough about various things myself. I
don't recall saying at any point that you were "wrong," and in fact
(as you may clearly note) I said that you must have a good reason f
If you don't have the ability to figure out everything you need on
your own, then please refrain from polluting the mailing list with
attacks on people who want to help you. Andrew specifically did *not*
say you were wrong, and he asked a polite question. Nobody has all
the answers. If y
On Thu, Aug 21, 2008 at 11:18 PM, Steve Christensen <[EMAIL PROTECTED]> wrote:
> The great majority of Mac applications do not run in kiosk mode so for most
> cases preventing window movement *is* wrong because you take control away
> from the user.
Hold on, I don't agree with that. Taking contro
Kinda hair-trigger on the defensiveness, dontcha think, especially
since Andrew didn't actually say you were wrong?
The great majority of Mac applications do not run in kiosk mode so
for most cases preventing window movement *is* wrong because you take
control away from the user. Had you fi
On Aug 21, 2008, at 9:46 PM, Mike wrote:
Yeah, I've read that technote and am familiar with it. It doesn't
have what I need.
And there's no setting in IB to create a window without a titlebar
(and I don't want to create one programatically).
Then you're out-of-luck.
Creating a non-movab
On Aug 21, 2008, at 8:10 PM, Mike wrote:
Is there any way to prevent a Cocoa window from being dragged while
it is onscreen?
I believe you can override -constrainFrameRect:toScreen: to achieve
what you're looking for.
Cheers,
Ken
___
Cocoa-dev
Yeah, I've read that technote and am familiar with it. It doesn't have
what I need.
And there's no setting in IB to create a window without a titlebar (and
I don't want to create one programatically).
Jason Coco wrote:
On Aug 21, 2008, at 22:37 , Mike wrote:
For a Kiosk application.
Ah,
On Aug 21, 2008, at 22:37 , Mike wrote:
For a Kiosk application.
Ah, that makes sense... well, I'm not really sure about Cocoa. I think
you can override the drag method in Carbon, but not really sure about
that either.
In case you haven't seen it yet, there is a technote about kiosk stu
What I am doing is definitely not "wrong".
My application is a kiosk application, I put up shielding windows on all
attached monitors, and I enter kiosk mode. I then have a totally black
display with a single window - mine - which is the size of the main
display but which I want to be immovable.
For a Kiosk application.
Jason Coco wrote:
Wow, I hope not :) Why would you want to do this?
On Aug 21, 2008, at 21:10 , Mike wrote:
Is there any way to prevent a Cocoa window from being dragged while it
is onscreen?
Thanks,
Mike
___
Cocoa-dev m
Hi, Mike,
Unfortunately, I'm not sure as to the exact answer to your question.
Do bear in mind, however, that -- even if there is a way -- you'll
have to take into account that the user might very well switch Spaces,
rendering your window no longer visible. While I won't tell you right-
Wow, I hope not :) Why would you want to do this?
On Aug 21, 2008, at 21:10 , Mike wrote:
Is there any way to prevent a Cocoa window from being dragged while
it is onscreen?
Thanks,
Mike
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
Is there any way to prevent a Cocoa window from being dragged while it
is onscreen?
Thanks,
Mike
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at co
22 matches
Mail list logo
