Presenter>>curor not called by default?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Presenter>>curor not called by default?

Bill Schwab-2
Blair,

Is Presenter>>cursor working as expected?  I tried it with my primary
consumer of emulated widgets (gadgets), and the cursor did not change.  The
presenter appears to be properly connected to the view.  Since the gadgets
exist primarily to limit the number of views I need to create, it's easy
enough to define #cursor in the associated view; that works.

I tried the same thing in scribble, with the same results.  Putting

cursor
 ^Cursor cross

in the presenter has no effect; putting it in the view does what one would
expect.

The VC appears to use presenter/interactor level cursors, but I think it it
might be "cheating" by having the shield forward #cursor back to the VC.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Presenter>>curor not called by default?

Blair McGlashan
"Bill Schwab" <[hidden email]> wrote in message
news:[hidden email]...
> Blair,
>
> Is Presenter>>cursor working as expected?  ...

Erm, given that it doesn't exist, then I suppose so :-). The actual override
point is #onGetCursor:.

Regards

Blair


Reply | Threaded
Open this post in threaded view
|

Re: Presenter>>curor not called by default?

Ian Bartholomew-18
Blair,

> Erm, given that it doesn't exist, then I suppose so :-). The actual
> override point is #onGetCursor:.

I've got one in my 5.1.4 image (packaged in "Dolphin MVP Base").  I
guess you've removed it because it didn't do anything - which Bill has
now confirmed :-)

--
Ian

Use the Reply-To address to contact me.
Mail sent to the From address is ignored.


Reply | Threaded
Open this post in threaded view
|

Re: Presenter>>curor not called by default?

Ian Bartholomew-18
In reply to this post by Blair McGlashan
Blair,

> Erm, given that it doesn't exist, then I suppose so :-). The actual
> override point is #onGetCursor:.

I've got one in my 5.1.4 image (packaged in "Dolphin MVP Base").  I
guess you've removed it because it didn't do anything - which Bill has
now confirmed :-)

--
Ian

Use the Reply-To address to contact me.
Mail sent to the From address is ignored.


Reply | Threaded
Open this post in threaded view
|

Re: Presenter>>curor not called by default?

Blair McGlashan
"Ian Bartholomew" <[hidden email]> wrote in message
news:c3mifs$27725i$[hidden email]...
> Blair,
>
> > Erm, given that it doesn't exist, then I suppose so :-). The actual
> > override point is #onGetCursor:.
>
> I've got one in my 5.1.4 image (packaged in "Dolphin MVP Base").  I
> guess you've removed it because it didn't do anything - which Bill has
> now confirmed :-)
>

Yes, you are right (sorry Bill). Presenter>>cursor should have been
deprecated for #585, or in 5.1. It has been removed from D6.

Regards

Blair


Reply | Threaded
Open this post in threaded view
|

Re: Presenter>>curor not called by default?

Christopher J. Demers
In reply to this post by Bill Schwab-2
"Bill Schwab" <[hidden email]> wrote in message
news:[hidden email]...
> Blair,
>
> Is Presenter>>cursor working as expected?  I tried it with my primary
...

I am glad you mentioned this Bill.  I ran into the same thing a while ago,
it frustrated me a bit, but since it was unimportant I just forgot about it.
Now I have gone back and added an onGetCursor: method and it does exactly
what I want.

Chris