x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

inl file build issue - on a property name

Hi,

I have a strange issue on one of my properties.

its name: CooldownTime as float. When the build process failed, it say that it can't find a Cool*D*ownTime property.

For any reason the "d" is moved to capital "D". If I set my property to CoolDownTime, I have no issue.

Is there any manipulation done in the Generateheader process or ???

any idea of the root cause?

Product Version: Not Selected
Tags:
more ▼

asked Apr 14 '14 at 12:10 PM in Bug Reports

avatar image

Elvince
464 42 67 152

(comments are locked)
10|2000 characters needed characters left

1 answer: sort voted first

This looks like an FName issue. FNames are case insensitive, but will only store the string for the first version they find, so if they see CoolDownTime first, CooldownTime will be a name match, but will come out as CoolDownTime.

Here's a similar question: https://answers.unrealengine.com/questions/27902/error-when-building-uproperty.html

more ▼

answered Apr 14 '14 at 12:36 PM

avatar image

Jamie Dale STAFF
7.4k 176 66 304

avatar image Elvince Apr 14 '14 at 01:03 PM

Ok I think I understand: So that's means CoolDownTime was already user in another header file and UHT already get it with a capital "D" so it will always put a capital "D" in the generated files.

I can understand the reason now, but is it something that can be fixed in the next version of the engine, or do we have to take this as "by design" and keep this in mind ?

Thanks,

avatar image Jamie Dale STAFF Apr 14 '14 at 01:33 PM

Unfortunately this will likely be an issue for the foreseeable future due to how ingrained FName usage is to UClass. If it is fixed, it certainly won't be in the next version, although the core team are aware of this issue.

avatar image Elvince Apr 14 '14 at 01:39 PM

Thansk for the clarification.

Now I'm aware of it, so it should be manageable :D

avatar image Jamie Dale STAFF Sep 23 '14 at 11:19 AM

We've made a change for 4.5 which will make FName case-preserving for the editor and UHT. This should address the FName case issues you've been seeing.

I've checked that you're able to rename asset, actor, and blueprint components in a way that changes only their case. I've also tested that you're able to have a variables in different UObject/UStruct types that vary only by case, and that the UHT will generate code that actually compiles.

avatar image Elvince Sep 23 '14 at 11:54 AM

Thanks for this update. This will ease the coding and it's clearly more flexible.

(comments are locked)
10|2000 characters needed characters left
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question