ios - Swift/CoreData - Variable reference changes after initializing -

-

i'm getting feet wet coredata using swift , coming across doesn't make sense me.

basically i'm building simple map app user can drop pin, select info button annotation view, , add location "favorites" list. want keep list between sessions.

i have in appdelegate:

func application(application: uiapplication, didfinishlaunchingwithoptions launchoptions: [nsobject: anyobject]?) -> bool {     // override point customization after application launch.      self.datacontroller = datacontroller()      return true }

datacontroller() code located deals with....you guessed it. data. have init() , 1 other function adds data.

this code takes info , uses function in datacontroller class add data data set

let defaultaction = uialertaction(title: "ok", style: .default, handler: { (action) -> void in             let appdelegate = uiapplication.sharedapplication().delegate as! appdelegate             appdelegate.datacontroller.additemtodata(self.locationinfo.address, city: self.locationinfo.city, zip: self.locationinfo.zip, country: self.locationinfo.country, latitude: self.locationinfo.lat, longitude: self.locationinfo.long)         })

this gets weird. screenshot when app on "let appdelegate =...."

appdelegate initialization

and when app running next line down

appdelegate.datacontroller....

as can see images, datacontroller has value @ first, when try use 1 line down equals nil , appdelegate has different value. app errors out "fatal error: unexpectedly found nil while unwrapping optional value" because of that. has else seen or know may going on?


Comments

Post a Comment

Popular posts from this blog

c# - How Configure Devart dotConnect for SQLite Code First? -

-
can configure following sample code ? when run following code, error : no entity framework provider found ado.net provider invariant name 'devart.data.sqlite' setting in machine.config <system.data> <dbproviderfactories> <add name="dotconnect sqlite" invariant="devart.data.sqlite" description="devart dotconnect sqlite" type="devart.data.sqlite.sqliteproviderfactory, devart.data.sqlite, version=4.6.287.0, culture=neutral, publickeytoken=09af7300eec23701" /> </dbproviderfactories> </system.data> after add below block code in app.config <?xml version="1.0"?> <configuration>   <configsections> <!-- more information on entity framework configuration, visit http://go.microsoft.com/fwlink/?linkid=237468 --> <section name="entityframework" type="system.data.entity.internal.configfile.entityframeworksection, entit...
Read more

c++ - Clear the memory after returning a vector in a function -

-
i have function processes , stores lot of data in , returns results vector of class. amount of data stored in function tremendous , want clear storage memory of function after finished job. necessary (does function automatically clear memory) or should clear memory function? update: vector<customers> process(char* const *filename, vector<int> id) { vector<customers> list_of_customers; (perform actions) return list_of_customers; } variables defined locally within function automatically released @ end of function scope. destructors objects called, should free memory allocated objects (if objects coded correctly). example of such object std::vector . anything you've allocated new must have corresponding delete release storage. try avoid doing own allocation , use raii instead, i.e. containers or smart pointers.
Read more

erlang - Saving a digraph to mnesia is hindered because of its side-effects -

-
updated the digraph library in erlang implements data type side-effectful. each operation on data type saves new state in ets table -- instead of returning altered version of itself, more common in functional languages. the problem usage perspective, impedes effort store or pass around state in convenient way requiring me first "collect" state before can start juggle around. the closest solution have seen far serializer/deserializer , these have drawback tied current structure of digraphs instead of operating on abstract type -- prevents future proof solution. update pascal pointed out serializer utilizes interface of digraph, , hence eliminates drawback mentioned above. better, albeit still inconvenient, see no better alternative. what recommendation on how store digraphs? should go different data type altogether? thanks. i not sure understand concern. fact digraph stored in ets transparent in user interface, might want chnge either exchange digr...
Read more