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
Is your feature request related to a problem? Please describe.
We need to be able to set some app specific parameter flags (and store them with FxPlug). All the flags going into FxPlug are filtered to just the flags publicly available (hidden, collapsed, ignore_minmax, etc). All our custom flags (outside the apple defined bits) are not stored.
Describe the solution you'd like
I propose upgrading FxParameterFlags to 64 bits, and FxPlug stores and returns the high bits for application purposes. These bits don't do anything with FxPlug except for being saved, returned, and operated on (like add and remove). All the lower 32 bits can be filtered to Apple Specific public flags as it is today. All the lower 32 bits can continue being reserved by Apple, as expected, and the high 32 bits reserved for developers.
Describe alternatives you've considered
I'm adding in an abstraction layer that traps all the Parameter flag methods and routes app specific flags to be saved in and retrieved from a Custom hidden Parameter. Our app specific flags are added back in when being retrieved. I'm currently using the high 10 bits of FxParameterFlags for app specific flags... but in the long long term, it's not ideal.
Additional context
This would make developing FxPlug frameworks easier.
The text was updated successfully, but these errors were encountered:
belisoful
changed the title
FxPlug API FxParameterFlags upgrade to 64 bits - high bits store for application use.
FxPlug API FxParameterFlags upgrade to 64 bits - high bits stored for application use.
Nov 29, 2024
Apple Feedback Assistant ID: MISSING!
Is your feature request related to a problem? Please describe.
We need to be able to set some app specific parameter flags (and store them with FxPlug). All the flags going into FxPlug are filtered to just the flags publicly available (hidden, collapsed, ignore_minmax, etc). All our custom flags (outside the apple defined bits) are not stored.
Describe the solution you'd like
I propose upgrading FxParameterFlags to 64 bits, and FxPlug stores and returns the high bits for application purposes. These bits don't do anything with FxPlug except for being saved, returned, and operated on (like add and remove). All the lower 32 bits can be filtered to Apple Specific public flags as it is today. All the lower 32 bits can continue being reserved by Apple, as expected, and the high 32 bits reserved for developers.
Describe alternatives you've considered
I'm adding in an abstraction layer that traps all the Parameter flag methods and routes app specific flags to be saved in and retrieved from a Custom hidden Parameter. Our app specific flags are added back in when being retrieved. I'm currently using the high 10 bits of FxParameterFlags for app specific flags... but in the long long term, it's not ideal.
Additional context
This would make developing FxPlug frameworks easier.
The text was updated successfully, but these errors were encountered: