-
-
Notifications
You must be signed in to change notification settings - Fork 1
Migration Guides
Alina P edited this page Dec 11, 2024
·
10 revisions
Widziałam już koty bez uśmiechu – pomyślała Alicja – ale uśmiech bez kota widzę po raz pierwszy w życiu. To doprawdy nadzwyczajne!
Overall:
- We decided to change the way we work with timers. Each new instance of the timer must be registered.
- The
MijickTimer
now allows you to observe state changes in very different ways. Just choose which one you prefer more.
- There are no more static methods to control the state of the timer. It is necessary to create an object and only then call set-up and state control methods.
- The initialization of the new
MTimer
object has been changed:MTimer.createNewInstance()
->MTimer(MTimerID(rawValue: "Your_Custom_ID"))
- Method
stop()
renamed tocancel()
- Added new control method
skip()
that allows to skip timer to it's final state. - It is no longer necessary to call the
publish()
function to make the timer work. All you need to do is initializeMTimer
and callstart()
. The state will be updated when the timer expires. - The status of the timer is expanded. Available statuses:
notStarted
,running
,finished
,paused
. -
MTimer
has become anObservableObject
. This means that you can observe updates to itsPublished
values:timerTime
,timerStatus
,timerProgress
. - Added visionOS support.