Question in subj.
I have window, and I have ListBox on it. I wanna find particular list item and make it selected.
I've read this
http://www.autohotkey.com/board/topic/17534-selecting-an-item-in-a-listbox/
but it doesn't work - my list dont change selection on key pressing.
So, I need to find item by text in some column and then select it (by clicking or smth else).
Related
Using ag-grid (trying on the demonstration page https://www.ag-grid.com/example.php) how can I use the keyboard to select an entire column?
You can press (on the demo) Shift and down arrow and go all the way down, but it's not practical for 1000s of rows. And as soon as you press Control, the selected cell does become the most bottom cell, but you loose the selection (as if Shift wasn't pressed).
If I was in Excel, I would select the top cell in a column, press Control+Shift+Down arrow, the whole column is selected, I can now do Control+C to copy.
I have seen this article, that adds a new menu item to do it How to select column data in ag-grid . I know I could assign a shortcut to that action too, but ideally I need a keyboard way using the Control (Command on a mac) key.
There's a not-so-straightforward way of doing this.
Click on the top most cell of the column you want to select
Do a Control + A (or Command + A for macOS) to select all of the grid
Now press Shift+ALT+(Left Arrow and/or Right Arrow keys or Shift+Option+(Left Arrow and/or Right Arrow keys in Mac OS
This should work
Have a study of Material-UI's Autocomplete with the playground on https://material-ui.com/components/autocomplete/, I really cannot see any difference with/without includeInputInList property? The document says 'If true, the highlight can move to the input.' I tried it, highlight never move to the input field.
The includeInputInList has 2 associated unit tests.
The description of the tests says:
it considers the textbox the predessor of the first option when pressing Up
it considers the textbox the successor of the last option when pressing Down
This means that with includeInputInList, when you have the focus on the component and you press key up, if it's the first item, the focus will go to the textbox (the input element), before continuing on the items. And if you press down and it's the last item, the focus will also go to the textbox.
Without that option the focus stays on the displayed items and never goes to the textbox, it jumps from the first to the last item (key up), and from the last to the first (key down) while you have the focus on them and just press key up or key down.
You can try on the example provided on the Material UI docs: press tab until you are on the MUI component, and then play with key up or down, with and without the includeInputInList prop on the Autocomplete component.
Suppose we have this org file:
1. first item
description of the first item
2. second item
description of the second item
3. third item
description of the third item
If I move the cursor to all the top items, and click <tab>, it will hide the descrption. And the file will look like this:
1. first item...
2. second item...
3. third item...
But when I open the file all items are open, which is uncomfortable for me. How can I hide them by default, leaving just dots?
That's strange, for me this is the default behavior to hide everything except the top level.
You can either modify it globally via the customize menu : Group org startup -> option org-startup-folded
or for each file like this http://orgmode.org/manual/Initial-visibility.html#Initial-visibility
I have two Excel picture objects linked to different forms, each with a text box and OK/Cancel buttons. In one form, the text cursor is in the textbox when clicking the object which is what I want:
but in another it selects the OK command button rather than have the text cursor in the textbox:
I've gone through the form and textbox/command button properties and see nothing about selection, and the 'correct' macro properties appear to be the same as the 'incorrect' one.
What do I do to change the form such that when it's opened the text cursor goes to the textbox instead of the command button being selected?
Quite easy solution is to change TabIndex Property to 0.
So, 1) go to VBA Editor, 2) select your TextBox in your UserForm and 3) change TabIndex Property in Property window as presented below.
Add an event to the form so that when it is initialized it selects the correct texbox.
Private Sub UserForm_Initialize()
TextBox2.SetFocus
End Sub
Before the form is displayed, you can do soemthing like:
TextBox1.SetFocus
Obviously, replace "TextBox1" with whatever the name of your textbox object is.
This should go in whatever event or macro causes the form to .Show, immediately before the .Show statement.
I have a "search" layout, which has several object boxes for the user to type in search queries. I have Set Tab Order... which works great. However, rather confusingly, pressing enter/return also has the same effect as pressing tab.
I have looked in the Inspector > Go to next object using and see that both the return and enter are unchecked.
What/where else could be causing this behaviour? Ideally I would like the return/enter key to perform a script/act like a button, is this possible?
Note: I am in Find Mode.
If there's no script trigger, try to double check that the enter/return is really off for the field in question. Maybe there are two or more fields stacked on top of each other (sometimes developers do that) and you checked the wrong one.
I was having the same issue. I checked the fields and there were no hidden scripts, triggers, conditional formatting or anything like that; however, the fields were either a drop-down list or a drop-down calendar so after selecting the criteria, the cursor would go to the next field.
I noticed that if I enter the finding criteria and double click the same field (to avoid going to any other field) and then click the return or enter keys, it works. So stay in the field when you click return or enter and it will perform the find.
Are you positive that you're in find mode when you're doing this? The default behavior in find mode is that the return key executes the find.
If the field you've selected has a dropdown list then CLICKING ON IT ONCE will bring the list down but not place the cursor in the field. Selecting the field a second time will place the cursor in the field. Once the cursor is actually visible in the field you will find that the TAB key works as you expect.
Otherwise, with the dropdown list down and the cursor not in the field, the RETURN key will move to the next field when in Find mode. This default behaviour sort of makes sense to me because the RETURN key can't act on the field until the cursor is actually in the field.
I had the same problem as you and it stumped me for a while too.