Skip to content

lack of was_touched for pin_logo makes it less useful as a 'third button' #149

Closed
@jaustin

Description

@jaustin

For the buttons we can easily write code that's not super time-dependent wrt things happening in the main loop, by using was_pressed. However, with the pin_logo, as far as I can see can only test whether it is_touched.

I wouldn't be against having a was_pressed for all touch pins, either. Does anyone recall the reason for not having was_ methods for pins?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions