You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are extremely difficult to debug and maintain as they are undocumented. For example: #2962
As mentioned in that thread, one approach would be to rip out the private APIs and everything that depends on them.
I expect the immediate effects would be a far less pretty Quicksilver, as these seem to be primarily used for animations. However, it should help avoid fiascos like the current (long) list of Sonoma issues.
The text was updated successfully, but these errors were encountered:
This removes `CGSPrivate.h`, `CPSPrivate.h`, as well as
`QSCGSTransition.{h,m}` which only seemed to serve as adapters for them.
It additionally either removes entirely or comments out (to serve as a
quick and dirty reference for reimplementation) code that depended on
these files.
This will break the pretty animations.
See also: #3001
* Remove the private APIs entirely
This removes `CGSPrivate.h`, `CPSPrivate.h`, as well as
`QSCGSTransition.{h,m}` which only seemed to serve as adapters for them.
It additionally either removes entirely or comments out (to serve as a
quick and dirty reference for reimplementation) code that depended on
these files.
This will break the pretty animations.
See also: #3001
* Revert "#FIXME: Force-disable superfluous effects on startup"
This reverts commit a5640c6.
* Cleanup unused
* Remove references to flare
Quicksilver currently relies on private APIs, primarily for its animations.
These are extremely difficult to debug and maintain as they are undocumented. For example: #2962
As mentioned in that thread, one approach would be to rip out the private APIs and everything that depends on them.
I expect the immediate effects would be a far less pretty Quicksilver, as these seem to be primarily used for animations. However, it should help avoid fiascos like the current (long) list of Sonoma issues.
The text was updated successfully, but these errors were encountered: