Apple's Cocoa framework header files have permissions 644, or u+w,go-w,a+r. All
of the third-party framework header files I have ever examined have permissions
755, or u+w,go-w,a+rX, instead -- meaning that the headers are marked as
executable. A number of online commentaries say that all
ich is triggered by the button at the top left of an editor window.
I found the preference setting. Go to the Xcode Preferrences Navigation pane,
and choose Uses Separate Window for Optional Navigation and/or Double Click
Navigation. Comments below these settings explain what various kinds
ove the edit area? When you hold down the Option key, does the wording of
anything in the pop-up button change?
Did you set some Xcode preference to make this happen?
--
Bill Cheeseman - wjcheese...@comcast.net
___
Do not post admin requests to the
> On Mar 16, 2016, at 11:22 AM, Ken Thomases <k...@codeweavers.com> wrote:
>
> On Mar 16, 2016, at 9:12 AM, Bill Cheeseman <wjcheese...@gmail.com
> <mailto:wjcheese...@gmail.com>> wrote:
>>
>> "2016-03-15 14:28:14.801 UI Browser[93092:22589120]
> On Mar 16, 2016, at 11:46 AM, Bill Cheeseman <wjcheese...@gmail.com> wrote:
>
>> On Mar 16, 2016, at 11:22 AM, Ken Thomases <k...@codeweavers.com
>> <mailto:k...@codeweavers.com>> wrote:
>>
>> On Mar 16, 2016, at 9:12 AM, Bill Chees
raints problem may be too difficult to
identify and resolve until I accomplish more factoring of my code into separate
view controllers. So I'll be going off the air on this issue for a while.
Thanks everybody for the suggestions.
--
Bill Cheeseman - wjche
> On Mar 17, 2016, at 4:55 AM, Bill Cheeseman <wjcheese...@gmail.com> wrote:
>
> I tried that, but it won't work because the storyboard won't load. That's a
> little discourging: Sorry, bud, you can't debug it because it has a bug in it.
>
>> On Mar 16, 2016, at 7:
look over to the right
side bar in order to see the associated priority setting.
--
Bill Cheeseman - wjcheese...@comcast.net
___
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (Xcode-users@lists.apple.com)
> On Mar 16, 2016, at 5:35 AM, Bill Cheeseman <wjcheese...@gmail.com> wrote:
>
> As to my question, I thought on it overnight and figured out that the only
> affected constraints would be those from any view in the affected scenes to
> their superview
gt; wrote:
>
> Start by giving all your views identifiers, that'll make them easier to track
> down; the error message will use the name and you can search for it in IB.
--
Bill Cheeseman - wjcheese...@comcast.net
___
Do not post admin re
lace every constraint in the
storyboard.
I did try removing and replacing the segues involving the two view controllers,
but it made no difference.
--
Bill Cheeseman - wjcheese...@comcast.net
___
Do not post admin requests to the list. They will be igno
l later, when the project is further
along, it comes up as "Copy Files" instead. They both work just fine if a
framework is the only thing that needs to be copied.
--
Bill Cheeseman - wjcheese...@comcast.net
___
Do not post admin request
y codesigned, and the whole
application package passes all Terminal tests including one using -deep. It's
only when I use the codesigning radio buttons in the General tab of each target
that I run into the wrong-version error.
--
Bill Cheeseman - wjcheese...@comcast.net
> On Oct 14, 2015, at 5:35 AM, Bill Cheeseman <wjcheese...@gmail.com> wrote:
>
> I am certainly not the only person using multiple versions or versions
> labeled other than "A" in shared frameworks.
I discovered more evidence this morning that use of versio
ther than "A" when codesigning an embedded
framework from the target's General tab at build time? If so, what is it? If
anybody knows of any documentation, please refer me to it. Thanks.
--
Bill Cheeseman - wjcheese...@comcast.net
__
what is it? If anybody knows of any
documentation, please refer me to it. (You don't need to respond, John, because
you've already made it clear that you don't have the answer. If you want to
keep talking about other topics, please start a new thread. Thanks.)
--
Bill
alidity tests in Terminal -- despite the fact that the
embedded framework has a single version "M" in it. And the application executes
correctly.
In fact, it makes more practical sense to code sign it when Archiving instead
of every time I build,
framework version to "M", but I'm guessing that I might have overlooked
one. Can somebody please point me in the right direction? (Don't tell me to
change the framework's version to "A"; that would be cheating.)
--
Bill Cheeseman - wjcheese...@comcast.net
their providers and
get a bitcode-compliant framework version for applications developed on Xcode 7.
I'm verging on a rant here, so I'll end it now by asking you (and everybody) if
you can point me to something with some official standing that makes clear
bitcode does not apply to OS X.
--
applications developed in Xcode 6 by setting
ENABLE_BITCODE=NO. What I wonder is whether setting the ENABLE_BITCODE build
setting to NO will work for applications as well as frameworks.
--
Bill Cheeseman - wjcheese...@comcast.net
___
Do not post admin
> On Sep 14, 2015, at 12:33 PM, Jens Alfke <j...@mooseyard.com> wrote:
>
>> On Sep 14, 2015, at 9:17 AM, Bill Cheeseman <wjcheese...@gmail.com
>> <mailto:wjcheese...@gmail.com>> wrote:
>>
>> Does anybody know if Xcode 7 can be used to develop appl
of the ENABLE_BITCODE build setting.
--
Bill Cheeseman - wjcheese...@comcast.net
> On Sep 14, 2015, at 4:00 PM, Alex Zavatone <z...@mac.com> wrote:
>
> Well a good reason would be the time spent downloading the app
___
Do not post admin reque
22 matches
Mail list logo
