You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've receibed some questions about disable the autocomplete feature for certain elements (or just for all).
For example, there are some users that uses the comments for invalide some parts of the css, and every time you write the /* it autocompletes to */ and you have to delete the autocompleted part and move it to the place you want.
#something {
the user: wants to keep this part;
and: invalide this part;
}
He writes the start of a comment and it's autocompleted:
#something {
the user: wants to keep this part;
/**/and: invalide this part;
}
You have to delete the last part and place it to the end of line:
#something {
the user: wants to keep this part;
/*and: invalide this part;*/
}
Otherwise, if it's more easy to you (and more convenient to the users), you can detect when the user is positioned in a blank space and let the last part is completed, or, if the cursor is behind a line, autocomplete it at the end of the line:
The user writes the start comment:
#something {
the user: wants to keep this part;
/*and: invalide this part;
}
and it is autocompleted to the end of the line:
#something {
the user: wants to keep this part;
/*and: invalide this part;*/
}
Other posible user action is invalide more larger parts of the css, and for that, the autocomplete feature would be disabled. You should have to detect when the user is positioned at the start of an element:
The user starts a comment in the beginning of an element and nothing should happend:
Other thing, is the position of the "}" bracket in the new auto indent feature. Drugoy says that he hates to scrool to much, and I understant it, but for the users that uses the } bracket in a single line would be great if you can add a "Write and Learn functionality". This would work something like this:
The user starts a bracket and it's autocompleted:
#something {|}
Press enter and the cursor is auto indent:
#something {
|}
If he doesn't like this coding style, you can build your own code and, once completed, right cick to the start of an element to the last bracket and select "Use this coding style for brackets".
This is the finished coding style that you can select with right click and USM would learn about it:
#something {
|
}
After that, the coding style would work every time you start a bracket and it's autocompleted.
I don't know if it's possible. I think that it would be a great solution for multiple coding styles. For me, it's much more comfortable the second coding style that I show you, I don't mind if uses much space.
If disable the autocomplete of brackets and comments results more easy to you, it also would be useful.
Anyway, I know you have a lot of work, so, if you want to keep this issue freezed for another version later than 1.1, there isn't problem.
The text was updated successfully, but these errors were encountered:
I've receibed some questions about disable the autocomplete feature for certain elements (or just for all).
For example, there are some users that uses the comments for invalide some parts of the css, and every time you write the /* it autocompletes to */ and you have to delete the autocompleted part and move it to the place you want.
He writes the start of a comment and it's autocompleted:
You have to delete the last part and place it to the end of line:
Otherwise, if it's more easy to you (and more convenient to the users), you can detect when the user is positioned in a blank space and let the last part is completed, or, if the cursor is behind a line, autocomplete it at the end of the line:
The user writes the start comment:
and it is autocompleted to the end of the line:
Other posible user action is invalide more larger parts of the css, and for that, the autocomplete feature would be disabled. You should have to detect when the user is positioned at the start of an element:
The user starts a comment in the beginning of an element and nothing should happend:
Now, he can place the end of the comment where he wants:
Other thing, is the position of the "}" bracket in the new auto indent feature. Drugoy says that he hates to scrool to much, and I understant it, but for the users that uses the } bracket in a single line would be great if you can add a "Write and Learn functionality". This would work something like this:
The user starts a bracket and it's autocompleted:
Press enter and the cursor is auto indent:
If he doesn't like this coding style, you can build your own code and, once completed, right cick to the start of an element to the last bracket and select "Use this coding style for brackets".
This is the finished coding style that you can select with right click and USM would learn about it:
After that, the coding style would work every time you start a bracket and it's autocompleted.
I don't know if it's possible. I think that it would be a great solution for multiple coding styles. For me, it's much more comfortable the second coding style that I show you, I don't mind if uses much space.
If disable the autocomplete of brackets and comments results more easy to you, it also would be useful.
Anyway, I know you have a lot of work, so, if you want to keep this issue freezed for another version later than 1.1, there isn't problem.
The text was updated successfully, but these errors were encountered: