|
You're not ready.
Everybody will let you work for free. If you were "ready", you'd know this.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I installed VS2019 on a new PC and when I open the code there are these "structure lines" all over the place. They're dotted horizontal and vertical lines that seem to "match up" code blocks.
Bloody annoying as @*@&.
I've Googled and went through the Settings but I can't figure out how to turn this "feature" off.
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
Tools > Options... > Text Editor > General and uncheck "Show structure guide lines" at the bottom (VS2017).
|
|
|
|
|
It's already unchecked
I've toggled it on/off multiple times. It seems to have no effect
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
modified 6-Jul-21 14:35pm.
|
|
|
|
|
I'm at a loss. A hack might be going to
Tools > Options... > Environment > Fonts and Colors > Structure Guide Lines
and setting their color to that of your window background 
|
|
|
|
|
are you using ReSharper, or something similar?
|
|
|
|
|
I love those structure lines. If I could marry them, I would.
|
|
|
|
|
Not sure about the marrying part, but 'I do' like them. 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
My kids actually used to say that all the time to me.
Me: I really love that car!
kids: Do you love it so much that you would marry it?
cute
|
|
|
|
|
So what do they say when you tell your kids you love them?
|
|
|
|
|
Queue up 'Dueling Banjos- YouTube'[^]
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
And I though it was a Monkey Island 3 video...
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
Well that took an unexpected turn...
|
|
|
|
|
Ah, thought at first you were referring to the colored crap on the scrollbar that makes it difficult to see the handle when there's been lot's of changes. IMHO, the structure bars are very useful.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
I haven't seen them, but maybe "too many structure lines" indicates "not enough structure"?
|
|
|
|
|
You probably also want to turn off highlighting the current line.
|
|
|
|
|
I'm working on the rasterizer portion of my truetype code, for which I found some public domain code that partially works - the parts I need anyway.
it's really hard to follow C code, so I'm porting it to C# before backporting it to C++ so that I can really understand it.
This isn't the only time I've done that. In fact, I often find myself going this route when coding something based on a codebase I don't understand at first.
Do you do this?
More I guess I'm curious how y'all go about decoding code that is either more complicated than you can readily understand, or too ugly to readily understand?
I port.
Real programmers use butterflies
|
|
|
|
|
What I like to do is create some integration tests that exercise the code paths and then debug the code to see what it's doing. The advantage of that is, with minor changes to the integration tests, I can verify my new code. That said, I do live in a world where integration testing is probably easier.
|
|
|
|
|
If I was wiser and more disciplined that's what I would do. 
Real programmers use butterflies
|
|
|
|
|
I find C much easier to understand than either C# or C++
GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I did too - until I "got into it", then C# is a whole load easier to read (and write).
One nice thing is that it prevents "silly mistakes" whereas C just shrugs it's shoulders and goes "Eh. He knows best, I'm sure" - leaving you with a PITA debug session becuas eyou read what you meant to write instead of what you did write (or I do).
Plus, the libraries are much better organised, and it supports large projects a lot easier as well.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I do the same thing. It's like being bilingual, when trying to read, listen or speak a second language, your mind interprets to your first language before you understand what is being communicated.
"When you are dead, you won't even know that you are dead. It's a pain only felt by others; same thing when you are stupid."
Ignorant - An individual without knowledge, but is willing to learn.
Stupid - An individual without knowledge and is incapable of learning.
Idiot - An individual without knowledge and allows social media to do the thinking for them.
modified 19-Nov-21 21:01pm.
|
|
|
|
|
I've never translated code to another language to help understand it, but I've reformatted it as a way to study it line by line.
|
|
|
|
|
Greg Utas wrote: I've never translated code to another language to help understand it, but I've reformatted it as a way to study it line by line.
This is what I do. If I don't understand the code, I have no idea how I'd translate it.
|
|
|
|
|
BryanFazekas wrote: This is what I do. If I don't understand the code, I have no idea how I'd translate it.
If you don't understand a block of code at all, you can't translate it, but translating a code section that you think you understand into another language can be a very good test of whether you really do, since it forces you to concentrate on details of the implementation that you might otherwise skip over.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
