Where are my bytes hiding?

[Gerriet M. Denkmann]

I just did:
> cd 
> /Applications/Xcode.app/Contents/Developer/Documentation/DocSets/com.apple.adc.documentation.watchOS.docset/Contents/Resources/Tokens/C/tag/-
>  
> ls -skl

There are 8 files. Finder → File → Get Info → Size: has for each: xxx bytes 
(Zero bytes on disk), where “xxx” is the same number as reported by “ls -skl”.

First question: 
How does one achieve this phenomenal compression: 0 bytes on disk - but can 
expand to several thousand bytes? If this is not a creatio ex nihilo, then: 
where are these bytes hiding?

Second question:
Finder says about the containing folder: 11,239 bytes (33 KB on disk) for 9 
items
11,239 = sum of TotalFileSizes of the 8 files in this folder.
But where do the “33 KB on disk” come from? 8 times “Zero bytes on disk” should 
be zero, shouldn’t it?

The reason for these questions:
I want to write an app, which counts (for a given folder) the number of bytes 
stored on disk.

Gerriet.


___

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

UIImagePickerController in popover broken on iOS 9

[Matt Reagan]

Hi all,

I've encountered a bug when UIImagePickerController is presented in a popover 
on iOS 9, and have been unable to find a workaround / fix.

It is easily reproducible in a brand new Xcode template (repro steps + sample 
project linked below), but I haven't been able to find much information online. 
I've been able to find partial fixes that depend on the orientation + 
multitasking settings of the app, but when the UIImagePickerController is the 
child of any other view controller (UITabBarController etc.) and the device or 
sim is in Landscape, it always breaks. I'm attempting to find a reliable fix or 
workaround, was hoping someone here may have seen this before?

Bug:
* UIImagePickerController presented in a popover of any kind has a 
broken 'pop' / back navigation animation
* Animated gif:   http://i.imgur.com/na2lprb.gif

Factors:
* The bug itself is impacted by several things:
- Orientation of the device/sim (only reproducible in Landscape)
- Multitasking availability (only Multitasking-capable 
devices/sims AFAICT)
- Multitasking opt-in (whether 'Requires full screen' is 
checked)
- Whether the UIImagePickerController is a child of any other 
controller
* The bug is NOT impacted by the following:
- Whether UIPopoverController or presentViewController: + 
UIModalPresentationPopover style is used

Repro steps (sample project linked below):
- Create a new iOS Xcode project ('Single view application' template)
- Add a button and wire it up to an action method in ViewController.m
- Add code to present a standard UIImagePickerController in a 
UITabBarController (ex. snippet below)
- Run the app on a 9.3 iPad Air 2 Device (or simulator)
- Make sure device/sim is rotated to Landscape
- Tap button (see 'Result' below)

Result:
* The popover is presented in the UITabBarController + popover 
normally, but if the user pushes back within the UIImagePickerController's 
navigation flow, the animation is broken
* Gif: http://i.imgur.com/na2lprb.gif

Example code:

// Bug also reproducible via presentViewController: + 
UIModalPresentationPopover style

- (IBAction)buttonWasTapped:(UIButton *)sender
{
UIImagePickerController *cameraRollController = 
[UIImagePickerController new];

cameraRollController.sourceType = 
UIImagePickerControllerSourceTypePhotoLibrary;
cameraRollController.allowsEditing = NO;

UITabBarController *tabController = [UITabBarController new];
tabController.viewControllers = @[cameraRollController];

UIPopoverController *popoverController = [[UIPopoverController 
alloc] initWithContentViewController:tabController];
[popoverController presentPopoverFromRect:sender.bounds
   inView:sender
 
permittedArrowDirections:UIPopoverArrowDirectionDown
 animated:YES];
}

Example project:
* http://sound-of-silence.com/sos/private/ImagePickerBug.zip

So far I've tried just about everything I can think of to fix the problem. As 
noted above, there are partial "fixes" that work (disabling Multitasking, or 
limiting orientations), but this is true only when the UIImagePickerController 
is presented _directly_ in the popover. When the picker is a child of any other 
view controller (embedded in a tab controller, or added as a child of an 
arbitrary UIViewController) I've been unable to find a fix.

Has anyone seen this before? Any advice/suggestions would be greatly 
appreciated.

Thank you~
___

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: Initial scroller style

[Quincey Morris]

On May 3, 2016, at 21:21 , Quincey Morris  
wrote:
> 
> these scrollers are shown in scroll bar “channels” on the right and bottom of 
> the scroll view

Well, I found out what’s causing this, though not why.

My content view actually consists of (top to bottom):

1. A scroll view, with a size-constrained document view that’s bigger than the 
scroll view.

2. A horizontal rule.

3. A status bar, which happens to be implemented as a horizontal stack view 
with a fixed height of 25.

It’s the horizontal rule that causes the scroll view to show the “wrong” style 
of scroll bars, both in IB and initially at run time. If I delete the 
horizontal rule, or if I enclose it and the status bar in a vertical stack 
view, the problem goes away.

Incidentally, IB undo seems to be severely broken in 7.3.1. IB frequently gets 
into a “won’t undo” state. The Edit menu shows the correct “Undo XXX” menu 
item, but choosing it has no effect. Conversely, when undo does work, it 
doesn’t necessarily update the inspector values to match the change.


___

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: Very basic need, very difficult to achieve.

[Alex Zavatone]

Considering that we all will need to perform this joyous process when we least 
expect it and have the least time to do it. Would it be possible to bulletpoint 
the process to serve as a reference?

One thing I have noticed with some of the more recent versions of OS X (10.9 I 
think) is that once upgraded, HFS will no longer recognize volumes from 
previous incarnations of the Mac OS.

This caused great panic on my end since it was unexpected, but it is important 
to note if you are trying to install a prior OS to a volume where the format or 
partition or whatever is not recognized by the HFS version of the OS you are 
trying to install.

Just a nice detail.

To mitigate this pain, I keep several VMWare Fusion VMs around at 40 GB a piece 
and when a new OS comes out, I duplicate the latest one, upgrade it, install 
Xcode on it and move forward.

This way, I can always spoil up an older OS with a working version of Xcode on 
it if needed.

Keeping these on a cheap and large HD and moving the one needed to an SSD is a 
cost efficient manner of keeping working older OSes with functional Xcode 
installs around if needed.

Hope this helps anyone who might have to go through Graham's lovely ordeal.

Cheers,

Alex Zavatone

Sent from my iPhone

> On May 4, 2016, at 7:41 AM, Sandor Szatmari  
> wrote:
> 
> Glad you got it to work.  I have seen the installer 'could not be verified' 
> before.  The only time I saw that was after using command line copy (cp) to 
> copy the installer app.  But except for that one experience, using 
> createmediainstaller has worked well.  I also copy the installer to someplace 
> outside /Applications like Phil (sqwarqDev) suggested before letting it run.  
> Basically the installer app that I archive is a pristine, never been run, 
> download.  And then I make USB sticks directly off of those archived apps.
> 
> Sandor
> 
>> On May 4, 2016, at 01:33, Graham Cox  wrote:
>> 
>> 
>>> On 3 May 2016, at 8:28 PM, Graham Cox  wrote:
>>> 
>>> So probably a redownload isn’t going to help, but I’m doing it anyway.
>> 
>> 
>> Success! Finally.
>> 
>> I created a new bootable installer using createinstallmedia and a fresh 
>> Mavericks download. I did the Pacific Daylight Time change just in case 
>> (though it sounds like voodoo, I’m prepared to believe anything at this 
>> point…)
>> 
>> I was able to install from that disk without further problems and now have a 
>> working Mavericks OS.
>> 
>> What didn’t work was trying to use the InstallESD.dmg directly. Creating a 
>> copy of it using DU/Restore worked, but it only created a pure copy of the 
>> disk image. That image was not bootable, and I was unable to make it so 
>> using createinstallmedia nor the Ars instructions (which apply to earlier 
>> versions of the OS anyway). It looks like the InstallESD approach is defunct 
>> from 10.9, though there may be something I’m missing.
>> 
>> Thanks to everyone for their help.
>> 
>> It certainly shows that upgrading as new versions of the OS are released 
>> should not be done without a great deal of thought. Leson learned.
>> 
>> —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/admin.szatmari.net%40gmail.com
>> 
>> This email sent to admin.szatmari@gmail.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/zav%40mac.com
> 
> This email sent to z...@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: Very basic need, very difficult to achieve.

[Sandor Szatmari]

Glad you got it to work.  I have seen the installer 'could not be verified' 
before.  The only time I saw that was after using command line copy (cp) to 
copy the installer app.  But except for that one experience, using 
createmediainstaller has worked well.  I also copy the installer to someplace 
outside /Applications like Phil (sqwarqDev) suggested before letting it run.  
Basically the installer app that I archive is a pristine, never been run, 
download.  And then I make USB sticks directly off of those archived apps.

Sandor

> On May 4, 2016, at 01:33, Graham Cox  wrote:
> 
> 
>> On 3 May 2016, at 8:28 PM, Graham Cox  wrote:
>> 
>> So probably a redownload isn’t going to help, but I’m doing it anyway.
> 
> 
> Success! Finally.
> 
> I created a new bootable installer using createinstallmedia and a fresh 
> Mavericks download. I did the Pacific Daylight Time change just in case 
> (though it sounds like voodoo, I’m prepared to believe anything at this 
> point…)
> 
> I was able to install from that disk without further problems and now have a 
> working Mavericks OS.
> 
> What didn’t work was trying to use the InstallESD.dmg directly. Creating a 
> copy of it using DU/Restore worked, but it only created a pure copy of the 
> disk image. That image was not bootable, and I was unable to make it so using 
> createinstallmedia nor the Ars instructions (which apply to earlier versions 
> of the OS anyway). It looks like the InstallESD approach is defunct from 
> 10.9, though there may be something I’m missing.
> 
> Thanks to everyone for their help.
> 
> It certainly shows that upgrading as new versions of the OS are released 
> should not be done without a great deal of thought. Leson learned.
> 
> —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/admin.szatmari.net%40gmail.com
> 
> This email sent to admin.szatmari@gmail.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: Very basic need, very difficult to achieve.

[Mark Allan]

___

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