Description

In general, UPROPERTY(VisibleAnywhere) makes a property ineditable. But, if the type of a property is FMovieSceneObjectBindingID, VIsibleAnyhere no longer prohibits it from editing.

[Image Removed]

 

[Image Removed]

Steps to Reproduce

To reproduce this, it requires to define a UMovieSceneSection subclass which has FMovieSceneObjectBindingID propery with UPROPERTY(VisibleAnywhere). Using Customizable Sequencer Tracks plugin makes it less steps. And, the reproduce project is avaiable in attachment. It can skip Step 1 - 10. Open a project and LV_Test level, edit a level sequencer there for step 11.

  1. Create a project based on blank template.
  2. Enable Customizable Sequencer Tracks plugin and restart the editor.
  3. Add a new C++ class inheriting SequencerSectionBP and add a MovieSceneObjectBindingID public member variable with UPROPERTY(VisibleAnywhere). For compile, it may require to add "CustomizableSequencerTracks" into PublicDependencyModuleNames in Build.cs.
  4. Add a new blueprint class inheriting SequencerTrackInstanceBP.
  5. Add a new blueprint class inheriting SequencerTrackBP and open it with blueprint editor.
  6. Specify your class to Default Section Type and Track Instance Type property then compile.
  7. Back to level editor and place an Actor to the map.
  8. Create a new level sequence.
  9. Click +Track > Actor To Sequencer > the Actor, placed at step 7.
  10. Add a new track with your customizable track and a new section on it.
  11. Right click on the section, select Properties and see the "VisibileAnywhere" property is editable.

A sample source code for step 3 is here;

UCLASS()
class UMySequencerSectionBP : public USequencerSectionBP
{
	GENERATED_BODY()
	
public:
	UPROPERTY(VisibleAnywhere)
	FMovieSceneObjectBindingID BindingVar;
};

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-212755 in the post.

0
Login to Vote

Fixed
ComponentUE - Anim - Sequencer
Affects Versions5.4
Target Fix5.5
Fix Commit33232727
CreatedApr 19, 2024
ResolvedApr 25, 2024
UpdatedOct 22, 2024
View Jira Issue