JDeveloper 10g error not highlighting - jdeveloper

I have recently shifted to work on Jdeveloper ide version 10.1.3 for one of our project, the ide doesn't assists me when I make any kind of errors in the code like eclipse and other ide's highlights, at the time of complying the project the errors are shown on the console window, I have tried with different ways but no solution.
I have checked in windows menu it don't have an option for rest factory settings, I have searched that option in tools menu too but there is no such option, please help me to resolve this problem.

After looking to the JDeveloper ide options one by one, the reset factory settings available in tools->preferences->audit->profiles. Now JDeveloper highlights me the syntax errors, this may be helpful to someone who is very new to this ide. Once reset factory settings done restart ide.

Related

VSCode Spring Initializr Error : Failed to fetch metadata

When I try to create a new project on Spring Initializr on VSCode, it produces the error on right bottom screen
Fail to create a project. Error: Failed to fetch metadata
Fail screenshot
I have checked Developer : Toggle Developer Tools and checked the error, it's not common JSON tag (html error return) problem.
I have checked the access to https://start.spring.io/ on my browser : no problem.
I have checked the internet access via proxy : There's no proxy.
I have completely removed VSCode (including extensions) and re-installed, still the same problem.
Windows 10, using gradle 6.9, java 11.0.12, vscode 1.59.0
Ok I've resolved the problem.
In case anyone comes up with the same issue, here it is :
open Spring Initializr Java Support extension from VSCode extensions.
click settings icon, then choose Extension Settings.
scroll down, and click "Edit in settings.json"
In my case spring.initializr.serviceUrl was empty. It should be :
"spring.initializr.serviceUrl": "https://start.spring.io/"
Sometimes the issue can be resolved by simply restarting the vs code editor.
Because extensions will get reflected only after restarting the editor
I received the same error message after having installed the extension pack and starting up a new maven project. Yet, for me the solution of #sayginify did not work.
In my case lowering the version to 0.4.8 did help. I was on 0.8.0. Also the versions in between did not work either. Obviously there are some known bugs in some versions. The solution came in here on the VS Code Spring Boot initializr Github page: https://github.com/microsoft/vscode-spring-initializr/issues/162#issuecomment-726832226 .
I had same issue, when I was at work. Removed work network connected to personal network and able to proceed. I got the feeling work network preventing downloading. Or may be have to edit your proxy settings

How to access mnemonics in Intellij 2017+ on Mac?

There is some evidence in the Intellij codebase they support ALT(/Meta)+CTL - (mnemonic) in Mac.
E.g: in platform/platform-api/src/com/intellij/openapi/MnemonicWrapper.java
if (SystemInfo.isMac && Registry.is("ide.mac.alt.mnemonic.without.ctrl")) {
And the corresponding resource value in ./platform/util/resources/misc/registry.properties is set to true :
ide.mac.alt.mnemonic.without.ctrl=true
However pressing those two modifier keys together with .. say .. F (for File in the main menu) does not work for me on Sierra with the latest 2017.1 intellij.
Is this supposed to work? Is there any other way to get mnemonics working on Mac.
Note: please do not comment/respond "mnemonics are not encouraged/supported on mac". I am more than well aware of this terrible shortcoming on OS/X. However in previous versions of Intellij it has been possible to use mnemonics on Mac: and it would be a big boost to have them working again.
Update A YouTrack issue was requested by the Intellij Jetbrains support lead. It is here https://youtrack.jetbrains.com/issue/IDEA-175624
CTRL-ALT-(Mnemonic) DOES work.
The JetBrains lead Serge Baranov also mentioned that ALT-(Mnenomic) is supposed to work. It did not / does not for any of my laptops on 2017.X.
The Jetbrains support team led by Serge Baranov worked diligently on this - but were unable to reproduce. I expressed surprise since a half dozen installations on my side - all do not work. Apparently for their testing team it does work. One of my Mac's was factory new in June 2017 with Sierra and I installed IJ Ultimate 2017.1 without any changes from defaults. It did not work.
It is unclear what conditions were required for the Alt-Mnemonics to work on 2017.X.
* Another update* . Jetbrains has provided a fix for this: see last answer.
Make sure mnemonics are not disabled in IntelliJ IDEA settings:
By default mnemonics should work with Ctrl+Alt and Alt on Mac.
If you prefer only Ctrl+Alt, add -Dide.mac.alt.mnemonic.without.ctrl=false in Help | Edit Custom VM Options (Processes Alt-based shortcuts for mnemonics in addition to Ctrl+Alt-based shortcuts. Affect MacOS only.)
There is also a bug in IntelliJ IDEA 2017.1.x versions which causes mnemonics to work via Alt in dialogs, but not in the menu. Adding -Dide.mnemonic.helper.old=true in Help | Edit Custom VM Options will workaround this issue. The fix will be available in 2017.2.x.
Thanks to Serge Baranov of JetBrains : we now have a solution
Add the following to Custom VM Options
-Dide.mnemonic.helper.old=true
In addition a fix will be added to 2017.2

cannot open visual basic 6.0 project due to component 'msconctl.ocx' not registered error

I have a project in visual basic 6.0 with an error message that,
'msconctl.ocx' or one of its dependencies not correctly registered:
a file is missing or invalid.
Can't figure out what is the problem,
i am also getting an error:- object or with block variable.
please help?
thanks
First, I'm pretty sure that you are talking about mscomctl.ocx (not msconctl.ocx), the Microsoft Common Control library, which is where you get all the common controls (text box, label, etc.) used in VB6. If you don't have this registered properly, VB6 won't run.
You haven't told us if you're using a 64-bit version of Windows or not. This makes a difference. In any case, you should be able to work out a solution by reading This.
MSComCtl.OCX was in 2012 modified in such a way that it became in-compatibable with legacy VB6 applications. MSComCtl.OCX prior to that was working fine. I ran into this and the only alternative left to me was to remove the control from the project ( in my case a Status Bar ) and use a Label field to cover the duties of the Status Bar. Once I was upgraded to a .Net Codebase I re-introduced the .Net Status Bar and things were back to normal. You probably didn't do anything wrong...its just a change to MSCOMCTL.OCX that once applied to your machine will break old VB6 projects that use that control. If you run or attempt to compile the app, VB6 should point you to the line(s) of code encountering the error. That will tell you which control is being victimized. Consider removing the control, and also the reference to MSComCtl, and creating workarounds. Sorry...just another nail in the VB6 coffin. I hate it but can't prevent it. Hope this helps.

Code Definition Window not working in VS2015

Just upgraded to Visual Studio 2015 and the Code Definition Window is not working.It just says "No definition selected" no matter what I select. Project is Windows Forms written in C#.
Go to Definition and Peek Definition are working fine
Went back to VS2013 to try it out and it's still working there
Tried to make a brand new project in VS2015 to see if it was project related, but it was not
Checked with a couple of colleagues and it wasn't working for them either
I have a feeling this is either a bug in VS2015 or some sort of configuration change.
Anyone found a way to configure it, or any sort of work around to get it up and running again?
I got a reply from Microsoft on my Bug report. Turns out it's not implemented and possibly never will be:
Hi,
Based on the fact that Peek Definition was introduced in VS2013,
combined with telemetry data that shows that only a tiny percentage of
users ever display the Code Definition Window, we decided not to
implement support for it as part of Roslyn. I've filed an issue on our
GitHub project to consider resurrecting it.
Thanks for the report!
-- Kevin Pilch-Bisson Visual Studio Managed Languages
HereĀ“s the github issue Kevin created in response to my bug report in July: https://github.com/dotnet/roslyn/issues/4224
Looks like they just merged a fix for this into Roslyn:
https://github.com/dotnet/roslyn/pull/56102

Build failed... No build tools defined. AVR studio 4.19

When I tried to debug a small piece of code using AVR studio 4 I got this error:
Build failed... No build tools defined.
Could someone give me some advices?
In AVRStudio 4.19, Atmel made some serious changes from previous versions. Specially while using the toolchains. After you install WinAVR (the latest version, 2010...), open a new project in Avrstudio and from now on, everytime you make a new project you have to do this steps:
Go to "Project" tab
Go to "Configurations Options"
Then all the way down to "Custom Options".
Once you there, you'll see a checkbox called "Use AVR ToolChain", UNCHECK that option.(For some reason AVRStudio 4.19 does not link automatically the toolchain from WINAVR, so you have to do it manually).
After this, it enables the two options below.
For avr-gcc, you browse to the next direction: C:\ProgramFiles\WINAVR20100110\bin\avr-gcc.exe
For make, you browse to the next direction: C:\ProgramFiles\WINAVR20100110\utils\bin\make.exe
This directions depends on where did you installed WINAVR. I remember that the default location is "C:\" but when I installed WINAVR, I changed it to "ProgramFiles"
Click "OK".
After doing this steps, you should be able to compile and run your code.
Cheers, and hope it helped!
PD: I had that same problem, months ago. Check out, www.avrfreaks.net, very good webpage for newbies and pros at programming AVRs.
You need to install WinAVR or Atmel's "AVR Toolchain." If you already have one of these and still get this message, you may need to tweak the System Variables.
Connect the programmer first and then run avr studio.
I have that error when I try to open a project made in another version of AVR Studio (or upgraded to another version by someone else).

Resources