Pushing the Limits of Cocoa
Pushing the Limits of Cocoa
- Subject: Pushing the Limits of Cocoa
- From: Philip Dow <email@hidden>
- Date: Sun, 31 Jul 2005 03:54:24 +0200
Hiya,
The third post to the list, so please excuse my rashness. If I'm out
of place, let me know. I'm just interested in this stuff.
Transition should be smooth. Controls and views that move should
glide and fade into place rather that push each other out of the way.
Draws and sheets exhibit this kind of behavior.
I would like to slide an NSRulerView into place on an NSTextView. I
am already intercepting the toggleRuler: method in my subclass. From
here I think I can use an NSViewAnimation to smooth the transition
between the two views. Either I can fade the ruler in as I slide the
textview & enclosing scrollview down or I can slide rather than fade
the ruler into place. When finished I would pass toggleRuler: to the
super class to make sure everything is in agreement.
My problem: I need the ruler to already exist and have a frame before
I can transition it in. Either the ruler must cover the area of the
screen it would occupy after activating it, but hidden, so I can fade
it in, or the ruler must be in a shrunken frame that will expand in
accordance with the viewanimation dictionaries.
Is it possible to get an nsrulerview ready without it actually
displaying, toggling it on so to speak while keeping it hidden?
According to NSRulerView documentation,
initWithScrollView:orientation: is the only way to initialize the
view programmatically. That method screw me up for two reasons: it
does not take a frame and it associates the ruler with a scrollview,
which automatically adjusts the ruler's frame.
Is there any way to make this transition happen without subclassing
and gutting NSScrollView and NSRulerView?
-Phil
http://phildow.net
Am Jul 29, 2005 um 10:00 PM schrieb SA Dev:
Erik:
..... "Nuh uhhhh!!!" :-D
To *also* keep it cocoa-related, I've noticed that most questions
posted here have either a simple "read the docs here:..." answer (a
matter of the OP either not looking or not knowing what to look
for), or they're very involved 'oddities'. Those in-between seem
not to be doing anything that really push the limits of Cocoa or
they're just too damn good to bother asking. :-)
Either way, if it makes you feel better, I'll always answer every
one of your posts. Just say the word and I'll set up an auto-
responder ...
On Jul 29, 2005, at 2:05 PM, Erik Buck wrote:
I have noticed that I seem to have made the last post in most of
the discussion threads in which I have participated. Even when
mine was not the last post, it is often the last post in a sub-
thread.
There is nowhere else in my life where I ever get the last
word :) What am I doing right or wrong here ?
To keep it Cocoa related instead of just meta-list related, what
is it about Cocoa questions that they are seemingly answered
immediately or drag on for days with 20 or more posts ? Is Cocoa
perceived to be an onion with easy outer layers and inscrutable
inner layers ? Or, more likely, do some questions stand alone on
factual answers and other questions get side tracked by
philosophy ? There is a lot of philosophy encapsulated in Cocoa;)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40silentalcove.net
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden