FGroomEditorMode::InputKey

Input Button/Axis Events & Mouse Capture

Windows
MacOS
Linux

Override Hierarchy

FEdMode::InputKey()

FGroomEditorMode::InputKey()

References

Module

HairStrandsEditor

Header

/Engine/Plugins/Runtime/HairStrands/Source/HairStrandsEditor/Public/GroomEditorMode.h

Include

#include "GroomEditorMode.h"

Source

/Engine/Plugins/Runtime/HairStrands/Source/HairStrandsEditor/Private/GroomEditorMode.cpp

Syntax

virtual bool InputKey
(
    FEditorViewportClient * ViewportClient,
    FViewport * Viewport,
    FKey Key,
    EInputEvent Event
)

Remarks

Input Button/Axis Events & Mouse Capture

event sequence for left mouse down/capture/up is:

for doubleclick, we get one of the above sequence, then a second where instead of the first IE_PRESSED we get a IE_DoubleClick

for mouse wheel, we get following sequence

  • InputKey ( EKeys::MouseScrollUp / Down, IE_PRESSED )

  • InputAxis() for wheel move

  • InputKey ( EKeys::MouseScrollUp / Down, IE_RELEASED ) it appears that there will only ever be oneInputAxis() between the pressed/released sequenece

that this wheel event sequence can happen during a middle-mouse tracking sequence on a wheel-button (nice!)This is not just called for keyboard keys, it is also called for mouse down/up events! Eg for left-press we get Key = EKeys::LeftMouseButton and Event = IE_Pressed Return value indicates "handled'. If we return true for mouse press events then the StartTracking/CapturedMouseMove/EndTracking sequence is not called (but we also don't get MouseMove(), so the mouse-movement events appear to be lost?)

Help shape the future of Unreal Engine documentation! Tell us how we're doing so we can serve you better.
Take our survey
Dismiss