Re: NSApplicationShowExceptions - useful on main thread only?

[Keith Duncan]

We use NSApplicationCrashOnExceptions which avoids the silent logging and the 
interface, and just plain crashes, akin to the iOS approach to exceptions.

When we turned this on in one of our products we found (and fixed) four 
unreported issues by merit of the crash reports it generated.

Cheers,
Keith

On 25 Sep 2012, at 01:03, Sean McBride  wrote:

> On Sat, 22 Sep 2012 00:38:36 -0500, Ken Thomases said:
> 
>> I have no inside knowledge, but I think you've misunderstood the purpose
>> of this default.
> 
> I guess I have.  Thanks Ken & Corbin for straightening me out. :)
> 
>> If you want to change how uncaught exceptions are handled more
>> generally, you should look into Exception Programming Topics:
>> Controlling a Program’s Response to Exceptions > developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/
>> Exceptions/Tasks/ControllingAppResponse.html> and NSExceptionHandler. 
>> Of course, you should first strive to make sure your app doesn't raise
>> exceptions, but no amount of programming care or testing can guarantee
>> that it can never happen in the field.
> 
> Yes, I agree with and am aware of all that.  I currently use FeedbackReporter:
> 
> 
> to handle the (mostly rare) exceptions that make it to the user.  I was 
> thinking that NSApplicationShowExceptions was maybe meant to replace such 
> things.
> 
> FeebackReporter works mostly well but I'm unsure of the correct way to handle 
> uncaught exceptions on non-main threads/queues.  It seems to always result in 
> the app being killed no matter what I do.
> 
> Cheers,
> 
> -- 
> 
> Sean McBride, B. Eng s...@rogue-research.com
> Rogue Researchwww.rogue-research.com 
> Mac Software Developer  Montréal, Québec, Canada
> 
> ___
> 
> 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.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/keith%4033software.com
> 
> This email sent to ke...@33software.com


___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?

[Gavin Stokes]

Our app won't build right now because of this:

ld: file is universal (1 slices) but does not contain a(n) armv7s
slice: /projects/libcrypto-device.a for architecture armv7s

But lipo says:

Architectures in the fat file: /projects/libcrypto-device.a are: armv7

I've cleaned the project and deleted intermediate products, but no
dice.  Any ideas?

Thanks!

Gavin
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?

[Roland King]

On 25 Sep, 2012, at 5:26 PM, Gavin Stokes  wrote:

> Our app won't build right now because of this:
> 
>ld: file is universal (1 slices) but does not contain a(n) armv7s
> slice: /projects/libcrypto-device.a for architecture armv7s
> 
> But lipo says:
> 
>Architectures in the fat file: /projects/libcrypto-device.a are: armv7
> 
> I've cleaned the project and deleted intermediate products, but no
> dice.  Any ideas?
> 

armv7s


note the s on the end. 

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?

[Gavin Stokes]

> armv7s
>
>
> note the s on the end.

Thanks.  What is armv7s, and how does one compile for it?  A quick
search didn't reveal any obvious references to it online.  I'm using a
build script for OpenSSL that configures the build for armv7.
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?

[Roland King]

Sorry I was going to type more but sent by mistake and figured you'd probably 
sort it out. 

armv7s is what the iPhone 5 uses. I'm assuming at some point you switched to 
Xcode 4.5 and the latest SDK so the standard compile includes armv7 and armv7s, 
so you need a library with both. 

You can change the build script of the static library so it does both, or it is 
possible to just remove armv7s from your actual final target build and just 
build for armv7, just means that certain operations won't take full advantage 
of the iPhone 5 hardware, whilst you get it figured out. AFAIK apps can be 
submitted like this too, but it's something I would strive for. This is all in 
the build settings. I would have thought just changing the static library build 
script to have the two architectures in the same format the final target build 
has them would 'just work' and build a 2 architecture static library. 

On 25 Sep, 2012, at 6:21 PM, Gavin Stokes  wrote:

>> armv7s
>> 
>> 
>> note the s on the end.
> 
> Thanks.  What is armv7s, and how does one compile for it?  A quick
> search didn't reveal any obvious references to it online.  I'm using a
> build script for OpenSSL that configures the build for armv7.

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Why does Xcode claim a lib has no ARMv7 "slice", when lipo shows that it's all ARMv7?

[Gavin Stokes]

Thanks.  Yes, I was well on the way to sorting it out, but I was just
waiting for the build to finish to report back.

I was able to easily add armv7s to the build script, and it seems to
be progressing happily.

There's a bunch of info here:

http://www.anandtech.com/show/6292/iphone-5-a6-not-a15-custom-core
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: How to calculate NSToolbar height in fullscreen mode

[Nava Carmon]

It's good to know that I'm not alone in this ordeal :), though it doesn't solve 
the problem.
The height of toolbar (as it returned by the function, that I took from Apple's 
example) before entering the FS is some 50 pix.
Measured height of the same toolbar in FS is 63 pix (both are without title 
bar). So I cannot use the cached toolbar height. That's what I'm asking whether 
there is an API, that returns it?
Because if i set the frame of the window in FS mode to be as NSScreen's frame 
the detached toolbar will cover the upper part of the window (even before 
sliding down with the menu bar), which I want to prevent.

Best Regards,

Nava Carmon,

Moshiach Times Ltd.,

e-mail: ncar...@mac.com
Skype: navacarmon
Phone: +972.52.8157770




On Sep 24, 2012, at 9:07 PM, Lee Ann Rucker wrote:

> 
> On Sep 24, 2012, at 5:50 AM, Nava Carmon wrote:
> 
>> Hi,
>> 
>> I have to perform custom animation for NSWindow transition to full screen 
>> mode. The window have a NSToolbar in icons-only mode with custom items.
>> How to calculate properly the final frame of such a window in full screen? 
>> Seems, that the height of the toolbar in the fullscreen is not the same as 
>> in regular mode (not including title).
>> 
>> Thanks
>> 
>> Best Regards,
>> 
>> Nava Carmon,
>> 
> 
> 
> rdar://12144703
> 
> http://openradar.appspot.com/12144703
> 
> In window:startCustomAnimationToExitFullScreenWithDuration:, I know the 
> target contentRect but I can't use -frameRectForContentRect: to find the 
> target frameRect because the window style is still fullscreen, and can't use 
> +frameRectForContentRect:styleMask: because it doesn't know about the toolbar.
> Because all the windows using the same toolbar get updated when the toolbar 
> style changes, I can't just save the window and/or toolbar size before going 
> into fullscreen because it may not be valid when I exit.
> 
> Though if you always keep the same toolbar style and size you should be able 
> to cache the toolbar height from before you enter FS and restore it coming 
> out; even if it is different in FS (something I've never seen) it's the 
> standard window you care about. The FS window always covers the entire 
> screen; the toolbar slides down over it and you don't need to worry about it. 
> It's not even a child of your window at that point, it's got a special window 
> it lives in.

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: autosavesInPlace and sandbox

[Mike Abdullah]

On 23 Sep 2012, at 19:59, Georg Seifert  wrote:

>> Another alternative would be to ask the system to autosave to an alternative 
>> location which you do have write access to. Your users lose the ability to 
>> easily spot the autosaved copy of the doc, but otherwise it should perform 
>> fine.
> 
> Can someone give me a hint on how to do that?

Reimplement -autosaveDocumentWithDelegate:didAutosaveSelector:contextInfo: 
yourself to call through to 
-saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo: with a 
custom URL of your choosing.

>> That said, I would strongly encourage you to adopt autosave-in-place. You 
>> describe the problem in two parts:
>> 
>>> you do not like that any mouse click might change your document
>> 
>> 
>> Surely this applies to either saving system?
> 
> No, with the new style autosaving, the file changes on disk without asking 
> the user.

That's kinda the point though; that the user no longer has to differentiate 
between what's in memory and what's on disk. There's just "the document" and 
that's it.
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: How to calculate NSToolbar height in fullscreen mode

[Lee Ann Rucker]

On Sep 25, 2012, at 5:07 AM, Nava Carmon wrote:

> It's good to know that I'm not alone in this ordeal :), though it doesn't 
> solve the problem.
> The height of toolbar (as it returned by the function, that I took from 
> Apple's example) before entering the FS is some 50 pix.
> Measured height of the same toolbar in FS is 63 pix (both are without title 
> bar). So I cannot use the cached toolbar height. That's what I'm asking 
> whether there is an API, that returns it?
> Because if i set the frame of the window in FS mode to be as NSScreen's frame 
> the detached toolbar will cover the upper part of the window (even before 
> sliding down with the menu bar), which I want to prevent.

Are you using the default NSApplicationPresentationOptions?  I implement the 
window delegate method to return AutoHideToolbar and I make my FS windows cover 
the whole screen. I haven't used the visible toolbar option but it does seem 
odd to me that you'd have to do the window size adjustment yourself; the FS 
side of window handling seems pretty good in that respect.

One thing you might experiment with is adding a fullScreenAccessoryView, then 
looking at its position onscreen when you're in FS. There's also 
window:willUseeFullScreenContentSize: which I haven't looked at because I don't 
need it.

But no, there are no APIs because NSToolbar is older than fullscreen and we 
didn't need them before now.

> 
> 
> 
> 
> On Sep 24, 2012, at 9:07 PM, Lee Ann Rucker wrote:
> 
>> 
>> On Sep 24, 2012, at 5:50 AM, Nava Carmon wrote:
>> 
>>> Hi,
>>> 
>>> I have to perform custom animation for NSWindow transition to full screen 
>>> mode. The window have a NSToolbar in icons-only mode with custom items.
>>> How to calculate properly the final frame of such a window in full screen? 
>>> Seems, that the height of the toolbar in the fullscreen is not the same as 
>>> in regular mode (not including title).
>>> 
>>> Thanks
>>> 
>>> Best Regards,
>>> 
>>> Nava Carmon,
>>> 
>> 
>> 
>> rdar://12144703
>> 
>> http://openradar.appspot.com/12144703
>> 
>> In window:startCustomAnimationToExitFullScreenWithDuration:, I know the 
>> target contentRect but I can't use -frameRectForContentRect: to find the 
>> target frameRect because the window style is still fullscreen, and can't use 
>> +frameRectForContentRect:styleMask: because it doesn't know about the 
>> toolbar.
>> Because all the windows using the same toolbar get updated when the toolbar 
>> style changes, I can't just save the window and/or toolbar size before going 
>> into fullscreen because it may not be valid when I exit.
>> 
>> Though if you always keep the same toolbar style and size you should be able 
>> to cache the toolbar height from before you enter FS and restore it coming 
>> out; even if it is different in FS (something I've never seen) it's the 
>> standard window you care about. The FS window always covers the entire 
>> screen; the toolbar slides down over it and you don't need to worry about 
>> it. It's not even a child of your window at that point, it's got a special 
>> window it lives in.
> 

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Just to confirm: no way to get/set wifi programmatically on iOS, right?

[Rick Mann]

I'm fairly sure this is the case, but is there any way to get and/or set the 
wifi settings of an iOS device from an app? It would be a big step to at least 
be able to know the wifi network and password used to connect. This is for an 
app that will configure a hardware accessory's wifi connection.

-- 
Rick




___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: drawGlyphsForGlyphRange layout issue

[Aki Inoue]

> 1. Why is -drawWithRect:options:attributes: more compatible with 
> NSLayoutManager?
It's not about either is compatible.  When using line fragment origin layout, 
we're using typesetter behavior 10.2 compatibility for historical reasons.  
NSLayoutManager, by default, uses the latest behavior.  That difference causes 
baseline position differences depending on selected fonts.
By explicitly specifying the baseline origin via 
-drawWithRect:options:attributes:, you're preventing the typesetter behavior 
difference to affect the layout.

> 2. I thought the core text route would be more efficient. I have cached my 
> CTLineRefs. Doesn't -drawWithRect:options:attributes: require instantiating 
> an NSLayoutManager on each call?
We don't instantiate NSLayoutManager on each call.  In some cases, caching 
CTLine could be more efficient.  In other cases, using NSStringDrawing methods 
are more efficient.

You should sample with your particular app before making the decision.

Aki

On 2012/09/24, at 12:01, jonat...@mugginsoft.com wrote:

> On 24 Sep 2012, at 19:19, Aki Inoue  wrote:
> 
>> To be compatible with NSLayoutManager, you should use 
>> -drawWithRect:options:attributes: here instead of using CT.
> Using -drawWithRect:options:attributes: works.
> 2 questions:
> 
> 1. Why is -drawWithRect:options:attributes: more compatible with 
> NSLayoutManager?
> 2. I thought the core text route would be more efficient. I have cached my 
> CTLineRefs. Doesn't -drawWithRect:options:attributes: require instantiating 
> an NSLayoutManager on each call?
> 
>> 
>> Your source of trouble is using -drawAtPoint: which uses 
>> NSStringDrawingUsesLineFragmentOrigin option (layout glyphs from the top 
>> instead of the glyph origin).
>> 
> Why does the vertical offset only appear for some fonts, not others?
> 
> Regards
> 
> Jonathan Mitchell
> Mugginsoft LLP
> 
> 
> ___
> 
> 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.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/aki%40apple.com
> 
> This email sent to a...@apple.com


___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

NSWindowController and nib in framework

[Quincey Morris]

Here's an except of some code in a window controller:

> - (id) init {
>   self = [super initWithWindowNibName: @"MyWindow"];
>   …
>   return self;
> }
> 
> + (MyWinController*) myWinController {
>   return [[MyWinController alloc] init];
> }

The key point here is that the MyWinController class, and the MyWindow nib 
file, are both in a private framework, hence not in the main bundle.

On some Macs (10.7 and 10.8) this throws an exception some of the time:

> 9/25/12 6:39:49.700 PM MyApp[1040]: -[MyWinController loadWindow]: failed to 
> load window nib file 'MyWindow'.

According to the documentation, the window controller initWithWindowNibName 
should try to find the nib file in [NSBundle bundleForClass: [self class]], but 
this was apparently returning nil. When I logged this expression, the problem 
vanished. It seems that referencing (creating?) the NSBundle object was enough 
to make the window control init work. That is, this alternative:

> + (MyWinController*) myWinController {
>   [NSBundle bundleForClass: [self class]];
>   return [[MyWinController alloc] init];
> }

seems to fix the problem. Anyone have an idea what's going on here, and what I 
should really do to avoid/fix the problem?




___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Core Data - nil-ing a relationship to a missing object

[Steve Steinitz]

Hi,

If a Core Data to-one relationship is missing its target entity (and so 
throwing can't-fulfill-fault exceptions), how can I set the relationship to nil?

If I do

object.missingObject = nil;

or

[object setValue: nil forKey: @"missingObject"];

Core Data throws (when it tries to maintain the inverse relationship i.e. 
remove object from missingObject.objects).

If I do

[object setPrimitiveValue: nil forKey: @"missingObject"];

Core data doesn't seem to know to save the object.  At least that's what I 
think is going on - in any case the relationship is not nil-ed in the store.

At present I have to delete the object (as the doc recommends), but I'd prefer 
to keep the object and just nil the broken relationship.  

I'd prefer to not discuss preventing the situation.

Cheers,

Steve


-

Avoid loud and aggressive persons for they are vexatious to the spirit - 
Desiderata


___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: nstableview without nsscrollview

[Alfian Busyro]

Thanks for the answer.

Just leave it in a scrollview, and set it to not scroll in any direction, and 
size the scrollview to the table's height/width. That's it.

Actually I did it, In IB I deselect "Show Horizontal Scroll" and "Show 
Vertical Scroll" the table view won't scroll but still bouncing if I try 
to scroll it within the scrollview.

I ended up using a custom list view that can with customizable section.

-- Alfian

On 12/09/13 6:41, Corbin Dunn wrote:

On Sep 10, 2012, at 6:08 PM, Alfian Busyro  wrote:


>Kyle, thanks for your solution.

>>Think very hard about this. Why would you want to do this? What would
>>you do if your table view gained enough data that it no longer fit in
>>the available space?

>So I planning to make two tables in one view but I don't want to separate that 
two tables with scroll,
>and make only the view (parent view of two tables) is scrollable.

Just leave it in a scrollview, and set it to not scroll in any direction, and 
size the scrollview to the table's height/width. That's it.


>The purpose is if user scroll down that parent view these two tables also have 
to be scroll down too.
>Like sectional table view but with multiple tables, because I don't want to 
make it sectional.

>>Yes, table views can live outside of a scroll view, but it's not a
>>simple task. -[NSTableView tile] loves to resize the table view to
>>snugly fit its contents, and -tile will be called at arbitrary times.
>>You can't call -setFrameSize: on a table view and expect it to stick.

>it seems pretty annoying.

That table has to control its frameSize; there is no way around this if you 
think about it.

corbin





___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: nstableview without nsscrollview

[Gary L. Wade]

There's an elastic setting, which I don't recall the exact name or settings, 
but you just turn those off to get rid of the bounce.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/

On Sep 25, 2012, at 9:55 PM, Alfian Busyro  wrote:

> Thanks for the answer.
>> Just leave it in a scrollview, and set it to not scroll in any direction, 
>> and size the scrollview to the table's height/width. That's it.
> Actually I did it, In IB I deselect "Show Horizontal Scroll" and "Show 
> Vertical Scroll" the table view won't scroll but still bouncing if I try to 
> scroll it within the scrollview.
> I ended up using a custom list view that can with customizable section.
> 
> -- Alfian

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: nstableview without nsscrollview

[Andy Lee]

setVerticalScrollElasticity:

As it happens I just noticed this existence of this property today.

--Andy

On Sep 26, 2012, at 1:32 AM, Gary L. Wade  wrote:

> There's an elastic setting, which I don't recall the exact name or settings, 
> but you just turn those off to get rid of the bounce.
> --
> Gary L. Wade (Sent from my iPhone)
> http://www.garywade.com/
> 
> On Sep 25, 2012, at 9:55 PM, Alfian Busyro  wrote:
> 
>> Thanks for the answer.
>>> Just leave it in a scrollview, and set it to not scroll in any direction, 
>>> and size the scrollview to the table's height/width. That's it.
>> Actually I did it, In IB I deselect "Show Horizontal Scroll" and "Show 
>> Vertical Scroll" the table view won't scroll but still bouncing if I try to 
>> scroll it within the scrollview.
>> I ended up using a custom list view that can with customizable section.
>> 
>> -- Alfian
> 
> ___
> 
> 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.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/aglee%40mac.com
> 
> This email sent to ag...@mac.com

___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: NSWindowController and nib in framework

[Graham Cox]

On 26/09/2012, at 12:35 PM, Quincey Morris 
 wrote:

> Anyone have an idea what's going on here, and what I should really do to 
> avoid/fix the problem?


Is the app sandboxed?

I ask because I've had reports of this same error from the odd user but have 
been unable to reproduce it so far. It's ONLY happening since we sandboxed 
though.

--Graham
___

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.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com