I had a question that came from a recent experience with my IDE (Visual Studio) and it made me think about an aspect of being a programmer that I has been a hurdle for me for a while.
Now I understand that:
- Being a software engineer/programmer/what ever you want to call it, can be difficult and there are so many complex parts to it weather it be the platform you are trying to create within or the tools you are using to create.
- Things don't always work how you want them too.
- Things change quickly (platforms, api's, standards).
I posted up over the weekend about an issue which was driving me crazy, I wanted to add an external library (graphics.h) to my IDE (visual studio 2013) and there where some really helpful people on this forum who tried to help. But it became more and more of a rabbit hole. I became lost and confused while trying to figure out how to do this. And being a learner it became really demoralising. I decided to move on and focus on something else, I just wanted to ask people who are more experienced than me on here...... how do I deal with and avoid programming rabbit hole like trying to add an external library to my IDE ?
Thanks a lot PrivateRyan, I totally agree with what you're saying and its been the biggest learning curve for me.
I also love the feeling of solving problems like bugs and figuring things out about my code, my major frustration that led to this question is with things like the IDE I'm using. It's like MS said to themselves "How difficult can we make it for programmers to add a library to Visual Studio" lol..... of course I know that's not the case...... For me a rabbit hole is spending the whole weekend trying to add a library to my IDE (which I'm sure I'm missing a very simple trick with) which took time away from me actually learning.
I think I need to take a bit more time an learn more about the tools of my craft. What do you think is the best way to do this ???
One thing you can do to avoid frustration is not trying to do something that is not supported.
For example, conio.h is not a standard C++ header. It roots go back to Turbo C which is an outdated, non-standards compliant compiler. Visual Studio has no support for conio.h.
Part of the confusion is that conio.h is just header, not a library. Generally libraries consist of one or more headers with a matching object file. In your case, you had the header with no matching object file.
Woah, instead of just using OpenBGI, a very easy to install and use library, you're going to download and obsolete compiler to produce obsolete code that only runs in an emulation layer?
I may be a bit late here, but I had the same problem with VS 2015. I finally fixed the problem when I changed permissions on the sub-directory that the include files reside in. Now I can add new files or change what I have added.
Hi, AbstrationAnon and Duoas....... You know what...... I know deep down in my gut that you are both right, graphic.h is a bit of a waste of time......I guess its that whole thing with programmer pride which is forcing me to 'persevere' and not 'give in' but I'm just wasting time on an obsolete compiler to produce obsolete code...... I know that there can be value in learning some types of legacy coding principles because it can provide context and history, but graphics.h is maybe tooooo old and its just so energy sapping and frustrating fumbling around with something that's obviously had its day....... I am going to move on and look at using Allegro and SFML.
Thank You both for your advice, and tough love, its been a valuable lesson in not getting to bogged down and following my instincts.