Skip to content

Move MotorController to DisplayApp#1468

Merged
Riksu9000 merged 1 commit intoInfiniTimeOrg:developfrom
Riksu9000:motor-is-ui
Feb 25, 2023
Merged

Move MotorController to DisplayApp#1468
Riksu9000 merged 1 commit intoInfiniTimeOrg:developfrom
Riksu9000:motor-is-ui

Conversation

@Riksu9000
Copy link
Contributor

Vibration is a user interface element and thus belongs in DisplayApp. Vibrations are now screen specific.

@JF002 JF002 added this to the 1.12.0 milestone Dec 26, 2022
@github-actions
Copy link

github-actions bot commented Jan 31, 2023

Build size and comparison to develop:

Section Size Difference
text 415048B -32B
data 940B 0B
bss 53560B 0B

@Riksu9000

This comment was marked as outdated.

@Riksu9000 Riksu9000 marked this pull request as ready for review February 25, 2023 08:22
@Riksu9000
Copy link
Contributor Author

I've reverted creating the MotorController instance inside DisplayApp until we resolve #1583.

Vibrations should be associated with something happening on the UI.
Therefore SystemTask should not be controlling the motor.
@Riksu9000 Riksu9000 merged commit 5ab255b into InfiniTimeOrg:develop Feb 25, 2023
@Riksu9000 Riksu9000 deleted the motor-is-ui branch February 25, 2023 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants