Dev-C++ rearanging and deleting my code - c++

As I write code in Dev-C++ and scroll around to write another function and come back to the previous function I was working on Dev-C++ will have had entirely deleted my previous function! It also puts my code in all different places all over the screen randomly, messes up my code when I do edit --> undo and will give me error statements when I don't even have errors. I am running Windows 8. Can anybody help me get this straightened up please? It recently messed up a very large product I was working on with over 500 lines of code so I am rather upset about it. Thank you very much in advance for any help or any suggestions of other simple IDEs.

Related

AmCharts4 Value does not exist

I have got a chart which I have been working quite some time now. Lately, I noticed the following error in the console:
This error spams my console and funny enought, everything works perfectly fine. I still want to get rid of it, however. Things I have noticed:
After building the chart, I have the error roughtly 10 times in the console
It does not matter If my chart has data or not, it will always be there, spamming the console
When I do a mouseover, the error is created many many more times
Everything works perfectly fine: my chart is there, I see the bubbles on mouse over, etc.
Because the error log does not tell me anything, I really do not know what to do or where to start looking.
Providing a snippet is very difficult and time consuming, as the different parts of the code are split up in three files. I will do so however, if I do not manage to solve it any time soon.
Best regards,
Martin
So the problem was that a colleague removed the exportButton and when AmCharts tried to tie the exporting functionality to this button, it threw this error. However, I do not understand why such an obvious error would produce such an ambigous error log.

Printing text in different colours in the Windows CMD

I am planning to make a console game in C++, kind of like Dwarf Fortress (although I don't know if it was coded in C++), but I have encountered a big problem.
I want to display different things in different colours on the screen at once. I also need to change something that has already been printed (so that I don't have to re-print everything and make the screen flash annoyingly, especially that I will want to make changes every second or so) and I found a way to do that with WriteConsoleOutput() and although I don't know yet exactly how to use it, I'll be reading into it soon.
As for the colours, I found a post here about some ANSI Escape things, but it
a) doesn't work, even when copying the linked code from github
b) I don't know if it'll work with attempts to over-write the console in specific places with WriteConsoleOutput()
So my request is: could someone please ELI5 to me what am I supposed to do and why, as well as present with a viable solution to this combination of two problems so that I can replicate something like this, with the possibilty of changing what the characters show.
Thanks in advance!

VS Code C++ Automatic Syntax Error Highlighting?

Currently VS Code will only highlight errors when the file is saved. This can get bothersome, as it isn't immediately apparent sometimes if you've mistyped something or are using something wrong etc.
Is there a way to make VS Code automatically show syntax/logical errors i.e red/green squiggles underneath code?
I am working with python but I have the same problem.
As shown here: "Linting runs automatically when you save a file."
Therefore, what I did to automatically lint, is enable Auto Save. With this configuration you can achieve linting almost in real time.
I guess that for C++ will work similar. Hope it helps.

Does anyone know what this error is related to? I have checked my syntax, my declarations, most of everything, but can't find the solution

I am new to programming, VERY new. I am reading a C++ book and doing beginner level problems on the side to get a practical grasp. But there seems to be a very specific issue here.
With my VERY limited understanding, i have tried to check and recheck things but for some reason, i can't get rid of this error in line 16.
This is no homework or assignment, i am learning C++ just to add to my resume.
Any and all help + tips will be highly appreciated.
Here is the image associated with the problem showing the code and error statement at the bottom
You are not supposed to add ">" before the ";".
Remove the ">" and recompile.

Winform Not Displaying in Designer

I have a Managed C++ WinForm that suddenly stopped showing in the VS 2005 designer. The error it shows is
Could not find type 'int'. Please
make sure that the assembly that
contains this type is referenced. If
this type is a part of your
development project, make sure that
the project has been successfully
built.
I don't even know where to start with this one. Does the designer only access the InitializeComponent(void) method when rendering the form? So my question is: where do you start troubleshooting designer errors?
EDIT: I forgot to mention that this code builds and runs perfectly. It only shows an error in the windows forms designer.
This is troubleshooting for C# but I'd assume a couple of the points mentioned here would help.
What's the state of play with "Visual Inheritance"
This is usually caused by a syntax error somewhere in the code that causes the designer to be unable to run the form to render it. The best method for this is ofent sadly just reading the code looking for the problem extra brace, missing string etc. The good news is that it is most likely easy to find since you know that it preceeds the INT in the error message.
Some possibilities:
* I cause this usually by accidentally hitting the keybaord and putting some extra characters at the top of a file
* Extra braces that make the class uncompilable - missing quotes, semicolons
* Something typed at the top that messes up a common include/using statement
Diagnostics
* Sometimes you can find this by dogin a build and seeing what lione is flagged with an error and then looking around it.
* More often then not I have to just open the source file and scan through it looking for the problem.