uinavigationbar - iOS 7 navbar colours not showing properly on iPhone 4 -

-

my navigation bar colours appear in ios 7

deploying ios 6.0, if system version ios 7.0 or later, of navigation bar colouring doesn't display on iphone 4. works fine in iphone 5.

here's how doing it:

if (system_version_greater_than_or_equal_to(@"7.0")) {     self.edgesforextendedlayout = uirectedgenone;     [self.navigationcontroller.navigationbar setbartintcolor:[uicolor bluecolor]];     [self.navigationcontroller.navigationbar settranslucent:yes]; }   #define system_version_greater_than_or_equal_to(v)  ([[[uidevice currentdevice] systemversion] compare:v options:nsnumericsearch] != nsorderedascending)

maybe last line problem (settranslucent) since have heard iphone 4 has problems translucency, i'm pretty sure set navbar translucent in ios 6 well. try getting rid of out next , update if fixes anything.

edit: looks bar colour disappears after dismiss presented view controller. doesn't screw on iphone 4.

get rid of [self.navigationcontroller.navigationbar settranslucent:yes]; , should work fine.

if want, can check device model (see here: determine device (iphone, ipod touch) iphone sdk)

and adjust view accordingly.


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