Bummer. I was writing a Workflow script to do stuff and just wanted it
to be able to return me back to where I started when it's done, instead
of having to do it by hand. I didn't figure there was a way, but it
would have been helpful.
Daniel Phillips wrote:
> No this is all out of your control.
re you were can be
more efficient?
Eric Shepherd
Sent from my iPhone
___
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 cocoa-dev-admins(at)lists.
Anyone have awesome templates to share? :)
Eric Shepherd
Sent from my iPhone
> On Jun 8, 2014, at 9:04 PM, Shane Stanley wrote:
>
>> On 9 Jun 2014, at 10:16 am, Graham Cox wrote:
>>
>> I really wish Xcode would allow us to make our own templates, even for NSxxx
for newbies,
who learn Bad Things by following advice given in the comments in the existing
templates.
Eric Shepherd
Sent from my iPhone
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
Try implementing rightMouseDown: instead for that.
Eric Shepherd
> On May 15, 2014, at 12:39 PM, Tim Hewett wrote:
>
> I have a NSMenuItem with a custom view (inheriting from NSImageView) which
> needs to react to mouseDown: events. An NSTrackingArea has been setup for the
>
There's a lot to be said for spreading lots of NSLog through your code. It's
amazing how many bugs you can nail down using this old-school form of debugging.
Eric Shepherd
> On Apr 23, 2014, at 6:36 PM, Jerry Krinock wrote:
>
> Try some bonehead debugging with NS
isted,
so it wasn't adapted to the new Cocoa order of things, and was doing it
wrong.
Thanks everyone for letting me bounce this stuff off you (and for a lot of
good insights into debugging this kind of code).
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
On Tue, Apr 22, 2014
So, here's a weird thing I've just now noticed:
When the cursor is at the top edge of my window, the Y value is off by 10
pixels.
When the cursor is at the bottom edge of my window, the Y value is off by
40 pixels.
What the...?
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: shepp
de that assumes
that (0,0) is the top-left corner of the window. So this is as-expected.
What's not expected is that converting [theEvent locationInWindow] to view
coordinates using [myGLView convertPoint:where fromView:nil] is giving Y
values that are skewed by approximately 40 pixels in fu
ng) is ‘where.y - self.bounds.origin.y’ — or
> something similar if the coordinates aren’t flipped.
I've checked -- [self bounds].origin.y is 0. And yeah, self is the
NSOpenGLView.
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
___
Cocoa-dev
On Mon, Apr 21, 2014 at 7:03 PM, Ken Thomases wrote:
> In case you missed it, Noah Desch reported no problems using an
> NSOpenGLView in a window with a toolbar. I'm pretty sure some Apple sample
> projects use NSOpenGLViews in windows with toolbars, too.
>
Yeah, that's why I'm so confused. I'
viously. This is the means that Apple
docs said to use to convert the window coordinates to view coordinates...
am I missing something?
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
On Mon, Apr 21, 2014 at 7:05 PM, Quincey Morris <
quinceymor...@rivergatesoftware.com> wrote:
&
w
but the Y value is not what it should be at the edge.
Is there a responsible way to get the current height of the toolbar so I
can use that to adjust the calculations here?
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
On Mon, Apr 21, 2014 at 3:43 AM, Quincey Morris <
qu
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
On Sun, Apr 20, 2014 at 4:23 PM, Quincey Morris <
quinceymor...@rivergatesoftware.com> wrote:
> On Apr 20, 2014, at 12:54 , Eric Shepherd wrote:
>
> Nope. :(
>
>
> The only *technical* suggestion I can add
nd in the
view's, just in case that does it later.
Also, I've finally gotten to a point where I was able to move my toolbar
into my nib. No change though; this same issue happens at the bottom edge.
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
__
rbon hybrid
app.
Once I get the entire app ported to Cocoa, I expect to be able to switch to
having my toolbar in the nib, but trying to test when parts of the window
content can't be clicked is tricky in the meantime. :)
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
On Sat, Apr 19,
Still stumped by this one. I've read about every method that has "resize"
or "toolbar" in its name, among others, without finding anything. :)
Eric Shepherd
Gmail: the.she...@gmail.com
Twitter: sheppy
On Thu, Apr 17, 2014 at 8:55 AM, Eric Shepherd wrote:
> I
ursor acts correctly, turning into the resize cursor at the edge of the
window, and once the toolbar is on again, the cursor also behaves properly).
Anyone know what I'm missing here? This is very weird, and I've been
beating myself against it for a while now.
Thanks,
Eric Shepherd
Gmail
18 matches
Mail list logo
