Skip to content

how is cursor_position supposed to work with touch? #871

@aentity

Description

@aentity

I have hit issue where on touch only device, the cursor_position is set to 0,0 (it is not updated in winit event handling code, for example).

this appears cause issues inside iced, making it ignore or drop touches, on for example, buttons. In fact, i can see the touch events in my event collection, and i pass them to user_interface.update() (https://docs.rs/iced_native/0.4.0/iced_native/struct.UserInterface.html#method.update) but it seems that simulated cursor_position is required? i thought that touch would not need such a thing (since it doesn't exist)

what is recommended way to deal with cursor_position passed to:

user_interface.update(&events, cursor_position, ...)

when making integration based (wgpu) iced programs?

Metadata

Metadata

Assignees

No one assigned

    Labels

    invalidThis doesn't seem rightout of scopequestionFurther information is requested

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions