On 12/18/16 12:33:53 PM, Ken Thomases wrote:
On Dec 18, 2016, at 2:15 AM, Kurt Bigler wrote:
But if in Displays I set the resolution to 1920x1200 "More Space", then I can't
get the backing store to match the 2880x1800 physical display resolution. I need my
NSView's backing store scale facto
On Dec 18, 2016, at 12:33 , Ken Thomases wrote:
>
> How did you draw it?
It may also be that “drawRect” is not the correct approach, even with
“wantsLayer”. As I understand it, there are in general *two* copyings (with two
possible scalings) of images drawn in a view. One copies the image into
On Dec 18, 2016, at 12:17 , Frank D. Engel, Jr. wrote:
>
> I had been using @dynamic for object types and @synthesize for basic types
> (such as BOOL and int). It seems I will need to create the accessors then
> for the basic types as I just tried and @dynamic does not work for those.
You hav
On Dec 18, 2016, at 2:15 AM, Kurt Bigler wrote:
>
> But if in Displays I set the resolution to 1920x1200 "More Space", then I
> can't get the backing store to match the 2880x1800 physical display
> resolution. I need my NSView's backing store scale factor to be 1.5, but the
> doc says this is
On Dec 18, 2016, at 09:18 , Andreas Falkenhahn wrote:
>
> Reading the documentation again, it now seems to me that views should
> be created in loadView() instead. The documentation of loadView() says
> that "You can override this method in order to create your views manually."
>
> I've seen lot
I see...
I had been using @dynamic for object types and @synthesize for basic
types (such as BOOL and int). It seems I will need to create the
accessors then for the basic types as I just tried and @dynamic does not
work for those.
Thank you!
On 12/18/2016 10:15, Keary Suska wrote:
On D
On 18.12.2016 at 17:01 Alex Zavatone wrote:
> Allocate them in viewWillAppear: if they are nil.
> Just create a conditionalInit method for the purpose of this and put it
> inside viewWillAppear.
Reading the documentation again, it now seems to me that views should
be created in loadView() instea
Allocate them in viewWillAppear: if they are nil.
Just create a conditionalInit method for the purpose of this and put it inside
viewWillAppear.
On Dec 18, 2016, at 4:51 AM, Andreas Falkenhahn wrote:
> I do not use Interface Builder or Storyboards to create my GUI
> but I do it manually. Curre
> On Dec 18, 2016, at 5:50 AM, Frank D. Engel, Jr. wrote:
>
> My guess is that for some reason the @synthesize methods are not calling
> "willChangeValueForKey" and the like - why would that be the case? I have
> worked on one or two other Core Data projects and I don't remember having to
>
Ok, I think I'm getting closer to understanding this:
When I add new rows to the table, I can update the checkboxes before
exiting the application, and the values stick (though the enabled state
of "a" does not change when I toggle "b").
When I re-open the application after that, the enabled
Hoping this is something simple that is simply escaping me at the moment...
I a view-based table with two columns containing checkboxes.
The table has its content property bound to an array controller's
arrangedObjects, with that array controller being tied to entities in
Core Data.
The che
I do not use Interface Builder or Storyboards to create my GUI
but I do it manually. Currently, I'm setting up all controls
in viewDidLoad() of my UIViewController.
So I'm doing stuff like this in viewDidLoad():
UIButton *button = [UIButton buttonWithType:UIButtonTypeRoundedRect];
...
On 18.12.2016 at 01:19 David Duncan wrote:
>> When I disable the line "[vc release]", I don't get any crashes and it
>> works fine. Can anybody explain why? I was expecting that
>> presentViewController()
>> retained the view controller so that it is safe for me to release it
>> right after makin
I have an NSView whose entire contents consist of a single
programatically-generated CGImage. It is drawn by drawRect: using
CGContextDrawImage. I need the image to be rendered pixel-exact on retina
displays, meaning device-pixel-exact.
I know that I will be encouraged to do this in the ulti
14 matches
Mail list logo