On Jul 28, 2008, at 11:48 PM, Jonathan Hess wrote:
On Jul 28, 2008, at 3:29 PM, R.L. Grigg wrote:
On Jul 26, 2008, at 3:15 AM, Michael Ash wrote:
On Fri, Jul 25, 2008 at 11:08 PM, Henry McGilton (Starbase)
<[EMAIL PROTECTED]> wrote:
On Jul 25, 2008, at 6:50 PM, Michael Ash wrote:
In fact
On Jul 28, 2008, at 3:29 PM, R.L. Grigg wrote:
On Jul 26, 2008, at 3:15 AM, Michael Ash wrote:
On Fri, Jul 25, 2008 at 11:08 PM, Henry McGilton (Starbase)
<[EMAIL PROTECTED]> wrote:
On Jul 25, 2008, at 6:50 PM, Michael Ash wrote:
In fact I would go so far as to say that if you ever use
-s
On Jul 28, 2008, at 3:54 PM, Erik Buck wrote:
Is something like this a decent Cocoa approach:
// create the window
myWindow = [[NSWindow alloc] initWithContentRect: ... ];
// insert the existing matrix as it's content view
[myWindow setContentView:myMatrix];
// alter the position
Is something like this a decent Cocoa approach:
// create the window
myWindow = [[NSWindow alloc] initWithContentRect: ... ];
// insert the existing matrix as it's content view
[myWindow setContentView:myMatrix];
// alter the position of the matrix
NSPoint newPoint = ...
On Jul 26, 2008, at 3:15 AM, Michael Ash wrote:
On Fri, Jul 25, 2008 at 11:08 PM, Henry McGilton (Starbase)
<[EMAIL PROTECTED]> wrote:
On Jul 25, 2008, at 6:50 PM, Michael Ash wrote:
In fact I would go so far as to say that if you ever use
-setContentView:, you are very probably doing it wro
On Fri, Jul 25, 2008 at 11:08 PM, Henry McGilton (Starbase)
<[EMAIL PROTECTED]> wrote:
> On Jul 25, 2008, at 6:50 PM, Michael Ash wrote:
>>
>> In fact I would go so far as to say that if you ever use
>> -setContentView:, you are very probably doing it wrong. It is, for the
>> most part, not a very
On Fri, Jul 25, 2008 at 11:08 PM, Henry McGilton (Starbase)
<[EMAIL PROTECTED]> wrote:
> I don't see any value in
> having a content view whose only purpose in life is to act as
> a container for my drawing view.
Not that I have any knowledge about this unfortunately forgotten
feature, but I can f
On Jul 25, 2008, at 6:50 PM, Michael Ash wrote:
On Fri, Jul 25, 2008 at 9:42 PM, Graham Cox <[EMAIL PROTECTED]>
wrote:
Well, it's the usual approach. The content view is something that
the window
owns to act purely as the root of its view hierarchy - there's
usually not
much to be gained
On Fri, Jul 25, 2008 at 9:42 PM, Graham Cox <[EMAIL PROTECTED]> wrote:
> Well, it's the usual approach. The content view is something that the window
> owns to act purely as the root of its view hierarchy - there's usually not
> much to be gained by fiddling with it or putting your own content ther
Well, it's the usual approach. The content view is something that the
window owns to act purely as the root of its view hierarchy - there's
usually not much to be gained by fiddling with it or putting your own
content there directly. For example, when you drag a custom view (or
any view) in
Thats a clever approach! I'll try it.
Thx!
Russ
On Jul 25, 2008, at 6:10 PM, Andrew Merenbach wrote:
Hi!
The content view of a window is, as far as I should think, going to
extend to the window's boundaries. Thus you can't move it up/down
or left/right -- but you can put your content with
Hi!
The content view of a window is, as far as I should think, going to
extend to the window's boundaries. Thus you can't move it up/down or
left/right -- but you can put your content within a *subview* of that
content view, then position it as necessary.
Cheers,
Andrew
On Jul
I've created a NSWindow and set a content view. That displays fine,
but I need to be able to fine tune the position of the content view
within the window.
In the docs for NSWindow -setContentView it says:
"You can modify the content view’s coordinate system through its
bounds rectangle, bu
13 matches
Mail list logo
