You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When used Swift 2.2 I could once initialize a property agrume in my view controller so that when I opened Agrume somewhere inside that view controller via showFrom(_:) I could access to that property without instantiating a new Agrume view controller. It used to work well until I migrated to Swift 3 and Xcode 8.
Now when I use this scenario weird things happen, Agrume seems to be shown, but it is invisible (shown in visual debugger though).
BUT when I switched to a different scenario (instantiating a new Agrume view controller), everything worked as expected.
So, the question is, is Agrume designed in a way such that I have to create a new instance every time I want to open it?
The text was updated successfully, but these errors were encountered:
broadwaylamb
added a commit
to lanit-tercom-school/grouplock
that referenced
this issue
Aug 23, 2016
When used Swift 2.2 I could once initialize a property
agrume
in my view controller so that when I opened Agrume somewhere inside that view controller viashowFrom(_:)
I could access to that property without instantiating a new Agrume view controller. It used to work well until I migrated to Swift 3 and Xcode 8.Now when I use this scenario weird things happen, Agrume seems to be shown, but it is invisible (shown in visual debugger though).
BUT when I switched to a different scenario (instantiating a new Agrume view controller), everything worked as expected.
So, the question is, is Agrume designed in a way such that I have to create a new instance every time I want to open it?
The text was updated successfully, but these errors were encountered: