For work I use Viper-architecture and build module through NSObject that I connect directly via the Storyboard or Nib. This works well, but if you connect through the NSViewController to segue NSWindowsControllers, the application crashes with an error, since it is not called NSObject. Of course, there is the option to collect the module through the "storyboard.instantiateControllerWithIdentifier(identifier:)", but I want to use Nibs, and there optionality error.
Asked
Active
Viewed 62 times
0
-
What is your question? – rocky Sep 06 '16 at 23:39
-
@rocky observing the behavior of the program, I realized that the module is going before to load the controller. It turns out that I pull the techniques before they are declared. Now throw off the sample code on github. – Vladislav Prusakov Sep 07 '16 at 00:15
-
@rocky add example link – Vladislav Prusakov Sep 07 '16 at 00:35
-
@SpectralDragonChan Hey! Did you solve your problem? I faced with it and wonder is there some workaround for it? – Anton K Oct 28 '16 at 04:37