Issue with macro GENERATED_BODY()

shadd-anderson commented 7 years ago

I've got the plugin working, however it has an issue with the GENERATED_BODY() macro. A bunch of errors get thrown up as shown below:

It doesn't seem to affect anything other than an unsightly red squiggly, but curious nonetheless

RicardoEPRodrigues commented 7 years ago

I have this issue often.

I fix it by following these steps:

In UE4, press File > Generate CMakeList
In CLion, press File > Reload CMake Project
Wait a bit to reload and it should be fixed.

If that doesn't help, close CLion, repeat the first step and reopen CLion.

It normally fixes the issue.

shadd-anderson commented 7 years ago

@RicardoEPRodrigues I tried both solutions and neither of them worked... :/

RicardoEPRodrigues commented 7 years ago

Have you installed the UE4 plugin for CLion?

https://plugins.jetbrains.com/plugin/7753-unreal-engine-4-sdk-support

I don't know if it helps, but you could try it out.

shadd-anderson commented 7 years ago

Yeah, I've got it installed. Not sure how much it does, tbh. lol

shadd-anderson commented 7 years ago

I've noticed it has issues with a few different macros. Might be all of them. UE_LOG complains a bunch too

RicardoEPRodrigues commented 7 years ago

The code compiles but CLion does not recognize the tags.

Could you tell us your OS and some details. UE4 version for example. Maybe we can find some solution.

reapazor commented 7 years ago

Have you allowed CLion to update symbols?

shadd-anderson commented 7 years ago

Right. It's just red squigglies. Unreal still compiles no problem.

I'm running Windows 10, UE4 version 4.16.1, CLion version 2017.1.2

I've reloaded CLion multiple times. Remade the CMake file as well.

reapazor commented 7 years ago

UE_LOG always seems to complain about inappropriate number of arguments, I've filed a ticket with JetBrains prior about that, but mostly things work out ...

Some things I've noticed:

if you do not have the build targets setup correctly the project that Unreal generates seems to have a hard time finding references.
sometimes CLion takes a bit to load symbols, even after load
latest EAP 2017.2 actually fails on one of our machines to parse anything (bug filed already)

What mine on a good day looks like.

shadd-anderson commented 7 years ago

Cool. Thanks @reapazor ! Like I said, I'm not too worried about it, cause it still works. There's no performance issues, it's just a bit of an OCD thing on my side :) Someday soon Unreal and CLion will get along in perfect harmony ;)

shadd-anderson commented 7 years ago

Alright, so now I'm having issues that do affect usability, this time with different macros.

I've got an FHitResult that causes issues when I try to get the Actor from it:

You can see the AActor* pointer isn't recognized, and ActorHit gives an "undefined" error. So I looked into FHitResult, and here's what I found:

Looks like macros in general just aren't working properly. I've tried the suggestions above and it's still not working.

shadd-anderson commented 7 years ago

Looks like they've fixed the parameter issue

reapazor commented 7 years ago

Indeed !

-- Matthew Davey

On Jul 20, 2017, at 02:49, Shadd Anderson notifications@github.com<mailto:notifications@github.com> wrote:

Looks like they've fixed the parameter issue

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/dotBunny/CLionSourceCodeAccess/issues/56#issuecomment-316612978, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAGD3LtBCjiRmZv4LoEHLUr_jFw1cQgWks5sPvh6gaJpZM4NvTGm.

shadd-anderson commented 7 years ago

ahhh... No errors. Feels good

dotBunny / CLionSourceCodeAccess

Issue with macro GENERATED_BODY() #56