-
Notifications
You must be signed in to change notification settings - Fork 18
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support C "if" statements (hints for big if statements) #4
Comments
You can configure Bracketeer to always show you the hints (in the preferences: Bracketeer->Hints. See the "Min lines between brackets". Configuring it to 0 will cause the hints to always be shown). Also, you can configure (in the same preferences page), the length of a hint and how to "strip" it (See "Max length"). In the next version of Bracketeer you would also be able to see the hint when hovering over a closing bracket. |
The problem is that i do not see hints with the configuration above for if statements (min lines = 0, max length = 100) in default and if (only to be sure)). The size of the if statements seems to do not matter. Maybe therefore i do not see any hint for else... if (test >= 2) hints are working for defines and loops like for and switch. |
this is very strange, I just checked this, and got the hints, as expected (the comments are hints, I didn't write them in the code): if( prio1 == 1) Please note 2 things:
Hope this helps. |
Hmm very strange. I checked some places (different files) in our code now and there are absolutly no hints for if and else. I only see them for loops like e.g. for or defines. I have the same issue on another computer in a different project. There is always nothing written after the closing bracket. We use the following versions: Eclipse C/C++ Development Tools Eclipse Platform PS: I see no hints for your code example too (comments are removed). I created a new empty project with your code example... |
I think I found the problem. |
Ah okay. We always use C projects for embedded systems. Thank you very much. |
Hints should always be visible independant of the size of the statement. If the statement is too big, strip the statement to something like "// if (...)", because sometimes it is useful to know if the bracket matches an if or for if they are e.g. nested.
The text was updated successfully, but these errors were encountered: