[The thread is a week old, so it may have gone stale…]
On 7 Jul 2015, at 1:58 AM, Rick Mann rm...@latencyzero.com wrote:
On Jul 6, 2015, at 23:22 , Kyle Sluder k...@ksluder.com wrote:
On Mon, Jul 6, 2015, at 07:57 PM, Rick Mann wrote:
On Jul 6, 2015, at 17:54 , Charles Srstka
On Jul 14, 2015, at 12:49 , Rick Mann rm...@latencyzero.com wrote:
What is my module's name, exactly, in an app target?
Go to the build settings for the target, filter on “Module Name” and you’ll see
it.
Note that you can’t enter the module name into the build settings directly. If
you try,
On Jul 14, 2015, at 12:29 , Fritz Anderson fri...@manoverboard.org wrote:
Blank? Not a placeholder for “Current — Your_Target_Name?” The NIB/storyboard
loading process for Swift needs an absolute module name, and in my
experience, IB’s reference may not survive transfer between projects
On Mon, Jul 6, 2015, at 07:57 PM, Rick Mann wrote:
On Jul 6, 2015, at 17:54 , Charles Srstka cocoa...@charlessoft.com wrote:
I’ve occasionally had issues getting Xcode to connect outlets and actions.
My workaround for it is to open the Assistant view, and drag from your view
into
On Jul 6, 2015, at 23:22 , Kyle Sluder k...@ksluder.com wrote:
On Mon, Jul 6, 2015, at 07:57 PM, Rick Mann wrote:
On Jul 6, 2015, at 17:54 , Charles Srstka cocoa...@charlessoft.com wrote:
I’ve occasionally had issues getting Xcode to connect outlets and actions.
My workaround for it
On Jul 6, 2015, at 7:46 PM, Rick Mann rm...@latencyzero.com wrote:
I'm having a heck of a time connecting UIViews to my classes. I have a
UICollectionViewCell subclass with a bunch of subviews. One of those is
custom.
While I can drag from views to the Swift code for the
I'm having a heck of a time connecting UIViews to my classes. I have a
UICollectionViewCell subclass with a bunch of subviews. One of those is custom.
While I can drag from views to the Swift code for the UICollectionViewCell
subclass, it keeps trying to connect it to a storyboard in a
On Jul 6, 2015, at 17:54 , Charles Srstka cocoa...@charlessoft.com wrote:
I’ve occasionally had issues getting Xcode to connect outlets and actions. My
workaround for it is to open the Assistant view, and drag from your view into
the source file, and let Xcode create an outlet or action