Why won't Robotium acknowledge checkboxes with higher index values that are further down the page? - robotium

My test keeps returning junit.framework.AssertionFailedError: 6 CheckBoxs are not found!
when call
if(!solo.isCheckBoxChecked(5)){
solo.clickOnCheckBox(5);
}
I don't understand why it is doing this because it scrolls down by itself (while watching the phone this is apparent). Based on the documentation I think this should make it like solo.clickOnText which scrolls around until it either finds it or gives up. Also I have used the exact same if statement with several check-boxes with lower index values and it never failed. There are 7 check-boxes on the page.

Index is not the best way to identify views. If I'm not wrong, robotium indexes only visible views, so if you scroll down, indexes for views will change. This way, you have always visible views (different) but with the same indexes. Try to use text or R.id, if you have different for every checkbox.
For instance you can see 3 checkboxes (indexes 0-2), scroll down, you still see 3 checkboxes (indexes 0-2), but different, indexes are rewritten to the visible ones. I may be wrong, but I don't think I am.

Related

RedisInsight: Configuring graph visual display/results?

Is there a way to configure the display of RedisGraph results in RedisInsight.
May be an option to edit the CSS directly is good too.
The reasons :
The color of the nodes is awful
The font-size is too small
nice to be able to change color of nodes with property value X
it will be good to be able to specify the default-property that will be displayed instead of node ID. Also on mouse-over too. (i know i can changed but it becomes tedious to do it for every result).
same for relationships
ERR: If some of the nodes in the result does not have the property you want to switch to (for display), then the 'switch' does not work i.e. all nodes still display IDs
for my screen it just happen that the +/- zoom is hidden i.e. I have to scroll back and forth. It will be good if we can use the keyboard to zoomin/zoomout
once you select something you have to click outside of the graph area to be able to scroll, supper annoying
command history on the query editor would be nice
ability to pin the result-area so that the new result does not spawn yet another area .. it is nice to have the option for multiple result-areas, but the normal interaction is refining queries rather than writing new query every time. (tabs would have been better)
if possible select-area to zoom will be nice. (by holding mouse down and selecting area )
!! double-click outside a node, may Zoom, instead of doing nothing
!! local zoom/search : typing in search-bar (there is space for it after +/-) to zoomin on the node with that have property and/or value f.e. val:3 , word:test , ...
Posting this here because couldn't find a place to give feedback on RedisInsight !

Buttons and Drop Downs duplicating in IE11 Word Add-in

I have a Word 2016 Add-in (Office.js) built with Bootstrap 3 and jquery.
Windows 7 users are reporting (and I've seen) duplication and even triplication of buttons and dropdown menus when they return to Word 2016 after letting it sit for 45 minutes or so.
If you just refresh the page you get a correct, single version of these buttons and dropdowns.
Somehow IE11 is deciding on its own to update the page and, in doing so, creating duplicates.
The buttons and dropdowns all work. Refresh returns the page to the correct state.
Anyone have any direction to go or ideas on this?
Thank you for the detailed response & interest - apologies for the long delay in responding.
I've only seen this with one user, in the UK, running Windows 7 and Word 2016. I screenshared with him and saw the triplication in person...unfortunately didn't think to take screenshots of his experience. His IE11 install didn't have the "Install new versions automatically" checkbox that I have (Windows 10).
(Side note: the permutations of Word 2016 and IE11 are ending up being quite a handful - I have many institutional users and they don't control updates to one or both...hard to even figure out what they're using).
He had three versions of every Favorite button and three versions of each Group Drop Down.
A simple refresh of the page returned things to normal.
The buttons all worked while the dropdowns had all 3 sets of choices in the first iteration of the dropdown; the second and third iteration of a dropdown was empty.
He described the situation as resulting after he "lets Word sit without using it or my solution for 40+ minutes." He has used my solution extensively and hasn't reported seeing it during use.
The screenshot below shows things as they are normally.
In his situation, that first button (for example) named 'Link' would repeat after the list of buttons along with every single other blue Favorite button.
The Dropdowns (Argument etc.) would be similarly duplicated or triplicated (he hasn't seen 4 yet).
My code is pretty simple jquery/javascript. When you load the page or refresh it pulls content and builts these buttons and dropdowns dynamically. I don't understand a situation where the browser somehow reloads or duplicates content...

Intellisense - Iterate list using different key other than Up/Down Arrows

I was wondering if its possible to customize the behavior of IntelliSense in VS 2012. I also have Resharper installed if that can do it. My desire is to minimize the amount of movement of my hands from the core keys. Typically when IntelliSense comes up I start typing and it narrows the list down to say 3-4 items. Then I need to move my right hand to the Down Arrow Key. I was wondering if I could use the Space key to cycle through the short list of 3-4 items and then hit Enter or ; to select the value I wanted. I can always keep typing the item I want but sometimes that will take 6+ keystrokes since the names are similar. Anyway just wondering as I would think that would be an improvement in speed.

TranslateAnimation resetting views occasionally

I am busy developing my first android app which is essentially a bubble burst type of game.
So far everything works except when I want to update a text box with a score.
Views are moved using translateanimation and all works as expected as long as a simple .setText() is not used.
When this is added occasionally some views that have been moved around previously suddenly move back to their original position. Additionally some variables also are set back to their original value.
I have tried updating the score via asyntask as well as runonuithread but the same issue occurs.
Thanks
I sorted it out.
I had the text box which I use for the score in a seperate xml and in that xml I had a include statement pointing to another xml file which had all the controls which are used as bubbles/blocks.
By including the score text box in the same xml the issue was sorted out.
There must be some rules that Android has regarding animating/updating controls across two seperate layouts.

LINQPad: Anyway to make the Dump() results be initially collapsed?

Couldn't find it anywhere (google or stackoverflow).
Is there a way to force Dump()'s output to be automatically collapsed?
Update:
Some more info, to bring more focus to the question.
As mentioned below Collapsing can be done after the output as rendered via keyboard shortcust (Alt+1, Alt+2, Alt+3)
And can rendering depth can be determined by passing an int depth param, but that does not allow to expand the results.
Is there some way to change the CSS formatting? I'm not that fluent in CSS, so this might be the solution.
Why I need this:
What I want is to make the output 'cleaner', and dive in when something of interest show's up.
I'm running a query repeatedly, and don't need all of the output all the time, but still using my human abilities to detect change, instead of coding the detection.
Update: November 2013
As Joe (the author himself!) mentions in the comments, LINQPad no longer has the limitation described.
It is now possible to state 0 and collapse the information after it's rendered.
No, although you can call Dump with a number to force it to display to that nesting depth:
.Dump(0)
You can also use the formatting shortcuts (Alt+1, Alt+2, Alt+3) to collapse the whole display to one, two or three levels.
Another option is to dump to grids. Call Dump(true) or use the toolbar button. Grids show only one level and subsequent levels are shown upon demand with hyperlinks.