I'm just starting out in C++, writing my first few programs in CodeLite. I keep getting this red arrow & warning message (shown below). I managed to fix it so that my code runs and works fine (had to open some of my files as an administrator?), but the message won't go away - would like to know if anyone else has had this issue and if you managed to fix it! (and how, please & thankyou)
Select 'Plugins'->'Language Server'->'Settings' and uncheck the box that says 'Display Diagnostics' at the bottom of the page then click OK ( Drag down Setting Dialog to See it ). That should take care of those red arrows.
source:
https://www.udemy.com/course/beginning-c-plus-plus-programming/learn/lecture/18801890#questions/15870611
Related
So I have not changed any settings in my code blocks editor and yet this appears I am new to the code blocks editor and if anyone could explain how this could popup so I can fix it and I have heard people will disable code completion to fix this but I never had the problem with it on so
I have tried disabling code completion this did fix the problem but it normally wouldn't do this with code completion on and I don't want it off
Open Code Blocks settings screen
Click "Editor..."
On the left, choose "Code compliation"
Choose "C/C++ Parser"
Make sure the checkmark on "Use one parser for the whole workspace" is checked
Then after saving the changes restart your Code Blocks IDE and make project save it. After that your issue is resolved.
None of the solutions mentioned above helped me!
I found myself solution, try whether it works for you not!
settings -> Editor -> scroll down (left options) -> Code Completion -> C/C++ parser -> Use one parser per project Check this option -> Maximum allowed parsers keep it less mine worked when i keep it to 2
It seems that rebooting the program has fixed this problem... Also I uninstalled the Library finder which I had opened once by accident then closed the program not saving and changes to anything which then restored library finder and apparently fixed the issue...
This worked for me:
Create two C/C++ files. Build and run them. Go to the C/C++ file you've built first and try to write something. Now, your issue should be fixed.
There's a youtube video explaining this trick. You can watch this if you face any difficulty: https://www.youtube.com/watch?v=sduqmX_VXB8
It's very simple. Save the file declaring which type it is. If C++, save it as whatever.cpp and it's gonna work.
Your file name should start with lower case alphabet.
We have to simply do one thing i.e. stop the code completion.
Goto "Settings" menu --> "Editor" --> "General Settings" (Left Pallet) --> "Editor settings" tab --> uncheck the "Code completion" checkbox..
Save the setting and you are good to go.. now u will never get that pop-up again..
I have an application which worked well so far.
Today I have updated my ubuntu to 18.04 and therefore reinstalled all software components, including Qt.
Now I experience a pretty wired behavior.
When I compile my application in debug build, everything is correct. When I switch to release build some combo boxes become invisible.
What is strange is, that events still work, the comboboxes are still there (but invisible).
I know this because I use an installEventFilter()
with if(event->type() == QEvent::Enter) which changes some other widgets if I hover the combo box with the mouse. Although the combo boxes are invisible the events still work when I hover the area where the combo box would be located.
Unfortunately, I do not know what makes this issue, so I cannot reproduce it in a minimal example.
My question is: Did anybody experience something like this before?
And: Where should I start to look for the error?
(I cannot debug it because everything is correct for debug builds)
By the way: I do not know if this is related but when I first tried to run the application I got an error that gl/gl.h was missing. After asking my friend google for help I found out that OpenGL was missing, so I installed it.
I would go and look for uninitalized variables when setting the properties of the combobox. Usually in debug even unitialized variables are set to some fixed value.
Or maybe you are setting properties in an assert that is not compiled in the release build? E.g. like this
Q_ASSERT(...)
that code in between the () will just be skipped during a release build.
I've been using Postman for a while now. Suddenly though it has stopped working. When trying to open it I get a loading spinner then nothing. No error. Nothing in Event Viewer. Nothing. Although the Icon in the task bar at the foot of the page looks broken or corrupted.
I've tried reinstalling, rebooting, clearing cache - nothing
I'm on Windows 7, 64 bit
Anyone ran into anything like this? :-/
I had a similar issue. The solution that worked for me is to use --disable-gpu flag for postman shortcut C:\Users\<username>\AppData\Local\Postman\<app-version>\Postman.exe --disable-gpu:
More info on Github: https://github.com/postmanlabs/postman-app-support/issues/4594
This issue happened for me when running a remote desktop session, it appears that postman is running but opening off screen. According to this thread
https://github.com/postmanlabs/postman-app-support/issues/2833
This can happen when you add or change a monitor.
There is a solution there - deleting some json files - but I found that I could see the Postman app in Task Manager -> Applications and then bring it up by selecting "Switch To"
I faced a similar issue and found that you need to navigate to AppData\Local\Postman and find the latest installed version folder now change the shortcut path on the desktop in my case it was AppData\Local\Postman\app-7.36.0\Postman.exe I did and it worked :)
postman folder
postman desktop shortcut
I had a similar issue on Windows 10. The application did not show up after opening it. This post helped me:
Hover the Postman icon in the taskbar. Then click the preview window that opens above it.
Press Alt + Space and then M or click "Move".
Move the Postman window with arrow keys, it probably was invisible on the right or left side of your screen.
This problem appeared after working with an external display. When I got Postman back visible, it showed an update dialogue.
I was trying to understand how to fix my watch window but didn't find any good answer(I'm using visual studio 2013).
I used the debugger and suddenly the watch window didn't show the values or the object i'm have in the block - actually it didn't show anything anymore.
Does anyone know how can it be fixed?
Many thanks!!!
Maby this will help you:
To open the QuickWatch dialog box with a variable added While in break
mode, right-click a variable name in the source window name and choose
QuickWatch. This automatically places the variable into the QuickWatch
dialog box.
Source
The Watch windows don't show anything by default, you need to add things to them to see the values. What might have happened in your case, is that either you deleted what you had by mistake, or you ran into a bug, where something got corrupted in your solution and they were lost.
If you want to see everything that is currently in scope, the Locals window is the way to go.
And if you want a superset of that (which has both current and previous statement), use the Autos window.
The QuickWatch dialog box is similar in concept to the Watch window, but QuickWatch can display only one variable or expression at a time
https://msdn.microsoft.com/en-us/library/bhawk8xd.aspx
Problem:
I am using Visual studio 2010 MFC c++..
facing this problem
I need actual menus that i naked, but i am in edit ID mode by mistake how can i leave edit mode.. and when i click on any edit ID mode menu.. i received the message provided in the above link
and when i run the project.. it shows no error but even then MFC is not running and displaying the result.Any one can help me to get rid of from thim problem
Expecting a good response..
Thanks
I have no idea what you're trying to ask but...
maybe edit the resource file as text would help?
Apparently you are in ID edit mode and want to leave it. Right click somewhere on empty space and uncheck 'Edit IDs' in the context menu by clicking on it.