When I get a rotation notice via willRotateToInterfaceOrientation, I remove my current constraints and build new ones right there in the willRotateToInterfaceOrientation routine .
Everything seems to work just fine. But I have a niggling memory that I'd read that this is a bad practice.
Can anyone cite specific issues or concerns?
I guess, since there have been no answers or suggestions, that the answer is no one knows of any issues. So, let's accept that a move on.
Related
I have an iOS app and i'm trying to run automated tests on it using Appium.
Some of my tests are failing because some objects are missing from the DOM tree. But when I look at the simulator screen, I see that those objects are there.
What can possibly create those differences? I'm not even sure who's fault is this -
Is it bad iOS code in it? Is it Apple's fault? Or is it Appium's fault?
Help would be much appreciated
Taking your feedback into account, there could be several reasons why a element does not show up in Appium but clearly visible on the screen of the device/emulator you use. The ones I know off or read about:
It's a OS problem. Appium depends on the accessibility layer from the OS. Updating or downgrading your OS could solve this problem, but no warranty here.
The app is using custom controls. A custom control will only be accessible if the devs that made the controls implemented accessibility for it.
There is also the possibility that you encountered a bug, known or unknown. Be sure to check the Appium github issues for known bugs, or to get help from the devs tackling a new one.
If trying another version of the OS or implementing accessibility does not solve the problem or is not possible, you will need to tap your element using coordinates. This is a last resort solution if everything else fails.
A very useful article on the problems mentioned above can be found here. It also contains all the resources to address these specific problems, like how to tap by coordinates the right way.
I've never encountered this one before - my background images are fine on the desktop but completely invisible on mobile. Not even a "bitmappy" version appears, though the space for them is held open, so to speak.
http://www.compassionglobally.org
I've read several similar questions here on StackOverflow but the issue always seems to be the file size (and iOS's enforced limits in that area). But even quite small images - there are four of them down the page - don't show up.
This is a WordPress site, but I feel like that's probably not relevant here... but I guess I should mention that.
Any ideas or suggestions are much appreciated!
This is one of the images not showing, right?
http://localhost/compassionglobally.org/wordpress/wp-content/themes/cg/library/images/site/baby.jpg
Well,
The link above is pointed to an image on the computer that is hosting the site (localhost). That file cannot be found on either your phone, or my laptop.
The fact that "the space for them is held open" is irrelevent, as you've set the div to be 250px high and 250px wide.
To solve the problem, you just need to remove the "localhost/" from the start of the links, like this:
http://compassionglobally.org/wordpress/wp-content/themes/cg/library/images/site/baby.jpg
To quote Bill the Cat... ACK!!!
I'm still fairly new to the "best practice" site-building method of local development, then uploading to the server. Thought I'd worked out a good system but of course I neglected to check my CSS for local references!
Thank you, I'm sure I will solve this fairly obvious-in-retrospect problem quickly now.
This might sound like duplicate question. In all the place I searched, they said merge conflict will occur when more than one person uses storyboard. But no one explained why, how, and when it will exactly occur.
My question is: What is a merge conflict?
Second question is: Why and when it will occur, and why it doesn't occur when we use programmatically?
Each person is going to work on different ViewControllers, so how this conflict occur.
Imagine that there is a little piece of text in the file. Let say, that there is a text "labeltext" and one developer changes it to "label" while you are changing it to "text". The source control system cannot know, which change is the "valid" one. It reports a merge conflict, so you and the other developer can decide, which version to take.
This can happen in code, too. But as a developer you are good in reading source code and likely bad in reading XIBs containing the storyboard. When you know, on which part of the software your colleague works, in many cases it is easy to decide, which version to use. If it is done in a XIB it is often impossible to you to know, even what the change is. You find yourself in the situation the version control system is: "Gmpf, what is the right version?"
Beside this, typically a storyboard is app global. You cannot say to your colleague: "Do not touch this file, I'll work on it today."
This is a much covered subject, however, I am not a coder and have not seen a clear breakdown of how to implement the "webkit-playsinline" tag, particularly in the context of Edge Animate (v.CC 2014.1.1).
I am looking to understand what libraries I may need to import and where to do this, or if I need to initiate something to get the tag to work (some function maybe) - I see there's an additional 'controls' attribute mentioned here: use webkit-playsinline in javascript
If someone will be kind enough to break this down for an idiot it will be much appreciated.
Using PhoneGap everything is working on Android and iPad, just need to try and get video to work inline and not pop into full-screen on iPhone - and apologies for not just jumping on one of the many other threads, only when you try there's a big notice saying not to do this =]
Thank you.
I am wondering if anyone has experience with having 100+ targets in a single xcode project. I have a case right now where we are building many apps that use the same code base. There is some debate internally that if the amount of apps gets to an unmanageable level aka (Maybe a couple of 1000 apps) we are going to have issues.
So my Question: Does anyone have experience with making a xcode project that has a ton of apps/targets (100+) in one project? Is there any issues with this? Is it easier then having a single project for each one and just sharing code with symbolic links?
I have built a project and made about 80 targets. Besides xcode crashing a couple of times while I was creating them (I think this was because I was using hot-keys and going really fast) it seemed like it was fine. I did not see any major performance hits, but since this was not a full project I am skeptical that this was tested fully.
Thanks for any insight.
So I found some information hidden in a post of a site called openradar. I think it will answer my question. I would love to hear from some real world experience through. So if anyone still has input please add it. I will be doing some more research on the subject.
Link to Post: http://openradar.io/15060709
Also I asked apple for comment on this as well and as soon as I get a response back I will post it in this answer.