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"

Unable to add OnClicked events in Level blueprint post 4.1

After updating to 4.1, I am no longer able to create OnClicked events in the Level blueprint, but can inside an actor blueprint. Existing instances of OnClicked events in a project work fine, but if I delete one, I cannot re-place it.

Was this functionality deprecated?

Product Version: Not Selected
Tags:
more ▼

asked Apr 24 '14 at 09:58 PM in Blueprint Scripting

avatar image

Stuckbug
158 15 14 28

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

1 answer: sort voted first

Try selecting the actor you wish to add the on-clicked event to, then in your level Blueprint, right-click and at the top of the drop-down you'll see "add events for [your object name]" In there, you'll see the input events, etc. (At-least I am). You can also start typing "Click" and find it too. alt text

more ▼

answered Apr 24 '14 at 10:34 PM

avatar image

Tom Shannon
99 8 10 17

avatar image Stuckbug Apr 24 '14 at 11:40 PM

Yep... that's what's missing. It's there within an actor blueprint, but the Input options are completely absent from the level blueprint.

alt text

onclickmissing.png (31.0 kB)
avatar image Marc Audy STAFF Apr 25 '14 at 01:18 AM

I've reproduced the issue and have a fairly good sense of what has happened. It is going to be inconsistent, some Actors will have the events available and others will not. Unfortunately I don't have a workaround at this time but I will try and get a solution in place as soon as possible.

EDIT: I should note, that if you are compiling your own source and there is a particular Actor class that is causing you immediate issues, you can go to the UCLASS definition of it and remove the hidecategories=(input) (or input portion of the hidecategories). This will have the effect of showing those events, though also showing some other things that probably don't want to be shown. The problem is a couple of different changes related to property/function categorizations coming together in an undesireable way.

avatar image Stuckbug Apr 28 '14 at 01:06 PM

Thanks Marc, I'll keep on eye on this question for more info.

(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