VSC auto completion starts at wrong position - reactjs

I somehow changed a setting and not sure how to revert it.
usuall when i use emmet abbreviation i type
"back" and it suggests background-color , i click enter and it will auto complete the text and i can start writing the color.
but now every time i click enter my cursor position is in the middle of background-color. e.g
example of wrong cursor position
so i will need click 3 times right and than i can write what i want.
anyone knows what settings this could be?

Related

Elementary Q: In Ride interface, in text edit tab, the search text field doesn't work. Is it the same for you?

I hope that someone responds to very elementary questions as well as the difficut ones. It's more than oe months that i use Ride for RobotFramework and i could never use the Search button on Text editor tab of Ride.
i write a word (not keyword) and i click the search button ( not Apply Changes button) and nothing happens. is it normal?
Thanks for any insight
The Search Button expects to have the text box on its left filled with the words to search.
You can also select the text and press Ctrl-G that will fill the text box an start the search (from the top of the file). Shift-Ctrl-G does the same but backwards.
This is a very rudimentary search function, but allows to find and replace if you have previously put content in memory (Ctrl-C), you can Search and then Ctrl-V.

Dialog close without selecting the value into text fields on on Simulator

I use the dialog to display date range control. On Simulator before selecting the value dialog closes and I'm not able to change or update any value. Please see the code below. Please advise if there is any known issue.
This is probably related to this line:
range.setDisposeWhenPointerOutOfBounds(true);
When you start interacting with the Picker popup, it disposes the dialog because the pointer it outside the bounds of the underlying dialog.
I have made a change to Dialog that will be available in the next update on Friday that will fix this issue.
https://github.com/codenameone/CodenameOne/commit/2c5fbfc9ae06e35911b5832441a685724e9739a0

How can I use AutoHotkay to click "next page" and take a screenshot and repeat until I terminate the process?

I want AHK to do the following:
1. Click in a specific location on the screen
2. Take a snippet of a pre-selected area
3. Save the snippet
4. Repeat the process until I press the "S" key (stop)?
You can use the MouseMove command to move it then send a click. After that you would just make it press the hotkeys for the screenshot and use the MouseClickDrag to form the rectangle. Then you make the script do ctrl+s to save it, and loop that. That's what I would've done. If you want, I could try to make a script for template.

Why does the first button pressed shrink in codenameone?

I am a novice programmer working on a project that has buttons change color when pressed (among other things). I am having a problem that the first button I click shrinks (the padding increases?) when it is clicked, but it still works and does everything it is supposed to. I have tried looking through theme.res to find a way to stop the button from shrinking when pressed and I have tried looking for an answer online, but have not found a solution. Thanks!
In the Resource Editor(theme.res), go to "Themes" -> "Unselected" tab. Right click over the style you use for the button and press Derive All.

Text blurring at any text options

After clicking, for example, on a button with no handler (that is no any reation axcept button clicking animation) I have this ugly effect on my eyes:
Blurring of the text on the button goes off in a second (from the first picture to the second and so on to the sharpness), then the text gets sharpness. I have this effect at any combinations of "TextOptions" options in XAML including TextOptions.TextFormattingMode="Display".
If I click on a button which raises, for example, select file dialog window, everything seems well.
How to escape this blur? Have you ever seen this effect?
In addition. This effect appears only with TextSize=11 and Aero is disabled. With TextSize equals any another value all goes well. But 11 is a default value so everybody can see this bug!
I don't know if you've fixed this yet or not, but the solution is to use the flag UseLayoutRounding="True". Throw that on the button style and it will be fixed.

Resources