objective c - AutoLayout fails, black background and autoresizing masks show up in any case -

-

i made uiview in storyboard containing 6 uibuttons.
wrote constraints support landscape mode portrait mode , put them in 2 different arrays: portraitmodeconstraints , landscapemodeconstraints. when mode changes, old constraints removed , right array gets added.

when load view in portrait mode there no problem. constraints work fine, wen turn ios-simulator, i'm getting lot of warnings. constraints work, tested them. constraints make problems ones autoresizingmask. turned them of on view controller using

[self.view settranslatesautoresizingmaskintoconstraints:no];

this made no change. debugged little bit , found out there no difference between settranslatesautoresizingmaskintoconstraints:no , settranslatesautoresizingmaskintoconstraints:yes strange , can't understand behaviour. however, deleted constraints manually this:

[self.view removeconstraints:self.view.constraints];

now, constraints worked in both portrait , landscape (the uibuttons @ right positions) background of uiview turned black , background image gone.

edit: when device rotate, function on viewcontroller called:

willanimaterotationtointerfaceorientation:(uiinterfaceorientation)tointerfaceorientation duration:(nstimeinterval)duration;

in there check wether tointerfaceorientation landscape or portrait. when portrait, this:

[self.view removeconstraints:self.landscapemodeconstraints];
[self.view addconstraints:[nsarray arraywitharray:self.portraitmodeconstraints]];
[self.view layoutsubviews];

and when landscape this

[self.view removeconstraints:self.portraitmodeconstraints];
[self.view addconstraints:[nsarray arraywitharray:self.landscapemodeconstraints]];
[self.view layoutsubviews];

stack same problem, when controller embedded in nav controller, , i'm doing self.view.settranslatesautoresizingmaskintoconstraints(false) view black. there no reason set transl..... on self.view. need apply subviews. auto layout guide


Comments

Post a Comment

Popular posts from this blog

css - Which browser returns the correct result for getBoundingClientRect of an SVG element? -

-
this svg contains rect overflows svg element: <svg id='svg' width='10' height='10'> <rect x='-10' y='-10' width='30' height='30'/> </svg> chrome 28 , opera 12 return getboundingclientrect() svg element width , height of 10. firefox 23 reports width , height of 30. correct? jsfiddle the relevant spec cssom , delegates svg spec if svg element not "have associated css layout box". haven't found definition of "having associated css layout box", correct result seem hinge on definition, getbbox returns 30x30 rect in browsers. this firefox bug fixed now, fix in firefox nightlies , should make through firefox 33 released on 14 october 2014. see bug 530985 details.
Read more

gcc - Calling fftR4() in c from assembly -

-
i trying asm fft implementation www.embeddedsignals.com work. running make gives error: undefined reference fftr4(short*, short*, int) at top of asm have .syntax unified .thumb .global fftr4 .type fftr4, %function and there #define's associate c functions arguments registers followed macros fftr4 function uses. after that, fftr4 called .thumb_func fftr4: stmfd sp!, {r4-r11, lr} mov tmp0, #0 // bit reversed counter mov tmp1, #0 .word 0xf3a2fa92 //rbit r3,r2 //rbit r,n lsl r,#3 and c code follows: void fftr4(short *y, short *x, int n); short x[512]; short y[512]; int i; void loop() { (i=0;i<512;i++) x[i]=0; (i=0;i<512;i=i+8) { x[i+0]=16384; x[i+2]=16384; x[i+4]=-16384; x[i+6]=-16384;} fftr4(y, x, 256); serialusb.println(y[128]); serialusb.println(y[129]); serialusb.println(y[384]); serialusb.println(y[385]); // expected results: //y[128]is 8191; y[129] -8190 y[...
Read more

.htaccess - Matching full URL in RewriteCond -

-
i'm trying block post access site (and return 403), except 2 ip's , 1 url ( http://mydomain.com/about-us/contact-us/ ). here's have: rewritecond %{request_method} post rewritecond %{remote_addr} !=1.2.3.4 rewritecond %{remote_addr} !=4.3.2.1 rewritecond %{request_uri} !^http://mydomain.com/about-us/contact-us/$ rewriterule ^ / [f] these rules allowing access ip properly, contact page still not accessible. i'm not sure i'm using request_uri correctly? i've tried variations relative urls rewritecond %{request_uri} !^/about-us/contact-us$ , rewritecond %{request_uri} !^/about-us/contact-us/$ without luck. what doing wrong please? it looks me rule on file name specific. if relax bit, should work. made few other esthetic tweaks. give try: rewritecond %{request_method} post rewritecond %{remote_addr} !^1.2.3.4 rewritecond %{remote_addr} !^4.3.2.1 rewritecond %{request_uri} !about-us/contact-us rewriterule ^ - [f]
Read more