I don't know whether this is the expected behavior, but when I create a screen and try to assign it to a task in my process, it doesn't seem to stick.
Specifically, I'm talking about "Screen for input" box in the "Edit Process" page. When I click the dropdown button, it shows my screen's name (strangely with red background). When I select the screen its name is displayed in the box. But when I select another task and then go back to the first, the box is still empty (with the dropdown list opened). I tried saving after selecting the screen, but when I backed out and choose to edit the same process again, the box would still be empty.
Any idea what I messed up?
Related
For as long as I can remember I had a search box near the top of the Assembly Explorer - this afternoon it's gone, and all attempts at restoring it have failed.
Is this a bug or did I somehow closed it? Can I bring it back?
Late answer. You clicked the "Toggle auto-hide of search bar" beside the search box. To get it back type any character when the focus is on the Assembly Explorer window. The click the Pin to keep it visible.
I had the same problem, but I did not find a way to simply bring back the search box.
Instead I reset all settings to default which made the search box appear again:
Go to Tools -> Options
On the bottom left click 'Manage…'
On the top right, click 'Reset All Settings'
Sorry for the confusing title but I can't get my head around to find the right words for this scenario:
We have an iOS app that has a top-left menu button. If you tap it, a side menu opens and most of the screen (incl. the menu button) are slid to the right.
for Calabash I need to track the ID of the view that is slid to the right. Any tap on the whole slid-to-right view area will close the menu. The menu icon itself seems to have no other function than being a visual help and its accessibility ID cannot be found by Calabash while the menu is open.
Does anyone know how iOS handles this kind of navigation? To sum it up:
We have an initial view open with a menu button.
If button is tapped, menu slides in from left and current view is moved to right (mostly out of the screen).
You can now tap any of the remaining visible area of the initial view and the menu will close again (the menu button seems to receive no touch during this).
I need to figure out to what assign an accessibility ID to so that Calabash can 'imitate' a tap on the slid-out, initial view to close the menu.
Have you tried using the Accessibility Inspector in the Developer Tools of Xcode? This might help you in seeing whether or not you can interact with the slid-out menu.
Also if you haven't tried using the calabash command tree - I'd give that a go as well. For that open the menu you're trying to interact with use the command calabash-ios console > console_attach > tree.
You will be able to see the whole view hierarchy here, you can even run tree before and after the menu pops out to see if it makes a difference.
I have an application and I want to test individual ui elements in the application from the inside. The purpose is to verify that display controls such as labels are displaying what they should and that touches trigger the correct results.
And I don't mean any E2E tests (I will use Appium for that), I'm looking for something that would allow me to open the app in a state that I need and test one element(if it is displayed correctly and if it behaves correctly - I will probably split these two actions into two separate tests).
For example:
Let's say I have an app that has a "Hello" button in the middle of the screen and upon clicking on that button a new screen opens that has two other buttons. One has label "Red" the other has label "Blue". If I click on "Red" the background of the application turns red and if I click the "Blue" button the background turns blue.
Now I want to write separate tests that would open the app on:
initial screen and check the "Hello" button is there
initial screen and check that clicking on the "Hello" button opens new screen
second screen and check that there is "Red" button
second screen and check that upon clicking on "Red" button the screen turns red
and so on..
I don't know how to call this testing but for me it sounds like "ui unit testing"
I know this is possible on Android using Espresso so I hope it is possible on iOS too.
Have you looked at the new UI Testing tools (XCUITest) in Xcode 7? With it, you would definitely be able to detect the presence of UI elements, and manipulate them (such as tapping on buttons). However, I'm not sure if you'd be able to confirm that the background view's color changed, unless you set the view's UIAccessibility value to include color information.
UI Testing overview: https://developer.apple.com/videos/play/wwdc2015-406/
potential limitations: https://medium.com/#larcus94/ui-testing-with-xcode-7-221d16bad276
The problem appeared when I tried to save the locale-specific components. The detailed description stayed unchanged.
This was the notification that appeared: "Error
The native string on which the translation is based no longer exists.
There was a problem saving your changes. Please try again later."
How should I solve this problem?
On the same page (the translation page), click the "advanced options" at the top right. On the next screen, click the "Dashboard" tab (top left).
Now, on the top right hand side you'll see a link to "Delete and re-import all strings". Click it and then you should be able to save the changes for the translation.
My universal app has a settings page, wherein the user must choose a theme from a dozen available themes.
Problem is, if I am using a picker-view, it takes up most of the screen on an iPhone.
I think what I want is something like your standard Windows drop-down menu, where it just displays on a single line the current selection, and clicking it expands into a scrollable list of possible items. Selecting an item collapses the list back into the original form.
So my question is: What is my best method for handling this situation? Can anyone point me to pictures or code examples of how this situation is handled successfully?
EDIT:
This is the behaviour I'm looking for:
only the currently selected profile is displayed
when the user taps on this, it expands into a list
when the user selects an item (or taps outside of the view) it collapses back to its original form, now displaying the new selection
ie functionally equivalent to a dropdown.
Firstly, this question is a duplicate of:
(not much good) Picker view as subview
(same) How to make an iPhone dropdown-looking button
(better) How to create drop down list box for an iphone app
(even better) Creating a drop-down list in iPhone app
(that last one links to some handy code)
Secondly, Google image search for 'dropdown control iphone' restricting the image size to 320x480 shows how everyone is doing this.
Basically a picker view scrolls in from the bottom, the same way as the keyboard does.