OS: ArchLinux
IDE: CLion
I tried to get the view of method signature by typing Ctrl + P, also by View -> Parameter Info. But it doesn't work.
My settings:
Yes -> Show the parameter info popup 1000 ms
Yes -> Show full method signature
How can I fix it? May be there are some plugins to get view signature?
Looks like a known issue. Please check https://youtrack.jetbrains.com/issue/IDEA-277166 as well as https://youtrack.jetbrains.com/issue/IDEA-277041.
There are suggestions about checking the value of ide.browser.jcef.enabled option... but a few comments from Linux users say they have it enabled already anyway (which is the default)...
Follow those tickets (star/vote/comment) to get notified on any progress.
You may download custom JDK build or some other tricks there: check this comment for example.
Related
I have an issue in MS Access.
I have a report that calls a query where the results are filtered with a value taken from the form that calls the report.
The condition on the field looks like this: [FORMS]![Main Menu]![Combo42]
When I open the project with the macros DISABLED the report works okay.
But when I enable macros (either from the enable content pop-up yellow line that appears on top or enabling all macros in the trust setting ) and I try to open the report the "enter parameter value" pop up appears.
It looks like when the I enable macros "Combo42" field becomes unaccessible from the query.
I have tried all the possible combinations from "trust center" settings menu even though only the "enable macros" seems to have any affect.
Is has to be setting related because the issue appears only on "freshly installed" office that I installed by my self (i tried many versions) but when I use pre-configured office (i.e. company laptop) the issue doesn't appear.
Does anyone has any idea why this is happening?
Thanks
UPDATE!
after some time investigation tying to answer some questions i found the solution here
MS Access VBA code editor character encoding and copy/paste
different outcome same root cause.
Have you tried renaming the reference to a valid field name after enabling Macros? This can help:
Enter Parameter Value
I need a solution for this error
Before using UFT 14.x , I wrote my code on UFT 12 (on windows 7) for copy/paste function. (It worked 100%)
When I upgraded UFT to 14.x , that function respond with an error . The code and the image are the following :
Function WritingFast(strDataTable)
set objCB=createobject("Mercury.Clipboard")
objCD.Clear()
objCD.SetText (strDataTable)
Window("Internet Explorer").WinObject("Internet Explorer_Server").Type micCtrlDwn + "v" +micCtrlUp
objCB.GetText
End Function
The error says that WinObject("Internet Explorer_Server") is not unique, what are you trying to refer to by this object?
Please examine the description of the object in the object repository in order to see why the description there isn't enough to make it unique.
Alternatively you could take a step back and think about what you're trying to do, perhaps UFT's web support allows you to do it directly and not by trying to access the underlying Win32 objects.
Can't add a comment, rules, sorry. Gonna put has an answer but its more a tip.
If you don't have a duplicate, try capture the object again. See if UFT recognize that object exists or not at your repository.
At least you can see what he is capturing whit the upgrade and compare (if different).
FYI, I am using a MCVS 2013 to build and run my program. However, I kept getting the error as shown in the picture, I have try to google the solution out, but there are no much information available. Besides that, I also getting 127 warnings. Some one from here please tell me how to prevent this error happen. Thanks!
In the properties page for your project, under the Linker -> Debugging tab, you need to use true or false instead of Debug as shown in the figure I attached.
How to avoid the window "No source available" while stepping into debug mode on VS2010 SL5
In Tools, Options, Debug, General Page. Check if you have 'Enable .NET Framework source stepping' enabled, if it is enabled, disable.
I tried all the suggested fixes; Nothing worked for me.
I finally figured out the solution after several hours of trial & error iterations.
It turns out that the 'No Source Available' error is due to a stack-overflow within the VS debugger env.
The C/C++ code function that was supposed to be stepped-into (by VS debugger), was using a variable that was initialized to a stack array of a few MB in size. When I replaced this with a heap allocation, VS was successfully able to step into the code.
This worked for me.
Please note that in my case, the actual code (with the stack allocation) ran without a stack-overflow error within the debugger (if I skip the No source available error). It was just that VS's debugger's was not able to step-into a particular function sitting inside another C/CPP file, because of the internal stack overflow.
Hope this helps.
You can hit Shift+F11 to step out and it will complete whatever unavailable function it is in and stop at the next line (it may be unavailable as well, but continue to use Step Out until you get to code you want to examine.)
Regarding VS2019, a description for the issue is provided at MSDocs.
For the requisite vcruntime and ucrt source files, the problem can occur after importing from a previous VS version which has since been uninstalled.
To prevent VS from using the old directories, find the solution property pages and navigate to the Debug Source Files Dialog Box.
Click the tick button to check the entries where any invalid ones can be removed.
The vcruntime and ucrt source should always exist in the directories, and the path at the top of the Browse to find source code dialog should always show the correct path.
In my case, because of a venerable drive bug, it is given to prompt for the "D" drive instead of the "C" drive. Further, the provided path cannot be pasted over to refresh the view, so, if none the wiser, one has to use the dialog to navigate all the way up to the required location from the desktop or equivalent.
Here there is an extension for this issue:
http://erwinmayer.com/labs/visual-studio-2010-extension-disable-no-source-available-tab/
But in my own experience before finding this article (I was in page but I was trying to fix it myself without reading article) I have fixed this problem just by accepting a confirmation message saying something like "Selected source file is different from compiled assembly. Are you sure you want to use this file for debug?". But I can't remember exactly what I did to get this message. I think there was a linklabel which I clicked on "No source available" window and then confirmation message appeared and after confirm the problem ran away.
i have some problem in memory management, and then i try to fix it using intrument tool.
Base on mark j video on you tube
about using NSZombieEnabled in intrument, i try to do like that. The problem is i never find a checkbox to set NSZombieEnabled active in my instrument. In this case i use xcode 3.2.5 and still on IOS 4.2.
This is the screenshot from the instrument that show no one check box for NSZombieEnabled activated :
am i doing something wrong??
help me please
thank you
Try running your application on simulator and see if you get the option in instruments. You may refer this tutorial to see how it is done in XCode 3.2 or you may refer the accepted answer in this thread for XCode 4.
Why not installing the new xCode 4? There you can easily set the EnvironmentVariables in the Scheme under the tab Arguments for Debug.
To check if it is actually set I use this code...
if(
getenv("NSZombieEnabled") || getenv("NSAutoreleaseFreedObjectCheckEnabled")
) {
NSLog(#"--------------------------------------->NSZombieEnabled/NSAutoreleaseFreedObjectCheckEnabled enabled!");
}
There is a simple way to enable NSZombie if you are dealing with XCode version 4 through implementation of the following simple step:
Please click on the scheme drop down bar named Product choose -> edit scheme -> arguments tab and then add NSZombieEnabled in the Environment Variables column and YES in the value column...Now you are done with enabling NSZombie to find bugs in program.
When you run your app,you get an error message where the app crashes setting NSZombie state to enabled,but originally before enabling NSZombie,you might find it difficult to find out what's exactly wrong,like crash at autorelease pool,gdb break currently using objective-c,BAD_ACCESS errors etc... By enabling NSZombie you can find what is exactly the problem such as improper deallocation and trying to re-access,or improper release of memory etc..The errors may be of the following kind:
-[ExampleProgramViewController alertView:didDismissWithButtonIndex:]: message sent to deallocated instance 0x7068f70