iphone - Button's background on ios7 is squeezed, ios6 ok -

-

i updated xcode 5. buttons in app ok in ib , on ios 6 device, on ios 7 device (they should cover whole black space):

enter image description here

i have images both non-retina/retina.

i have no idea do, because didn't change in code or ib.

edit:

now found out, if change type of button custom system , set background instead of image, correct size strange shadow on it.

edit2:

now set button's tint color "clear color" , seems ok (shadow disappeared). still not sure has changed in ios 7 related this.

the human interface guidelines outline how system-style uibuttons work default. it explains system button:

  • has no border or background appearance default ...
  • supports custom decoration, such border or background image (to add custom appearance, use button of type uibuttontypecustom , supply custom background image).

however uibutton hig page provides little more information, specifically:

if not explicitly set tint color, button inherit superview’s tint color.

this explains why, after changing button uibuttontypesystem, have reset (remove) tint colour. in ios7, (almost) everything has tint colour. uibuttontypesystem more appropriate needs in ios7 (a bit of pain if there's lot manually change though...)

as why buttons shrink in ios7... agree @joseph's comment regarding uiviewcontroller view frames in ios7. have set relation size of buttons not play nicely when viewcontroller's frame changes in ios7 (see this question discussion). advised there, check out ios7 transition guide see if you're doing in ib going against new ios7-grain.


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