- Joined
- May 15, 2020
- Messages
- 1,342
- Motherboard
- Gigabyte Z390 Designare
- CPU
- i9-9900KF
- Graphics
- RX 5700 XT
- Mac
@CaseySJ @joostiphone
This is how files are handled
As this gif is too fast download it and open with Preview
Now config.plist
We take SampleCustom.plist from latest OC -> Docs folder as our base for our new config.plist
for every entry in SampleCustom.plist we search the same entry in user's config.plist
if we find it then we compare the types
if they are the same then we set user's defined value into SampleCustom.plist
if types are different then OC default failsafe value is used
For array of dictionary entries in SampleCustom.plist we take the first item and create an empty template from that item
example for a kext:
a valid Kernal > Add entry
our generated empty template
Now we have a template for Kernel Add and we can fill the fields by values from users config.plist when the type is the same
So when OC team introduce a new field user will have it automatically
if that field requires a value then (we will see later for this case*) ocvalidate will throw an error about that so the user can make manual changes
After updating all fields we proceed into "additional OC Fixes"
You can find details into the code source just here.
Here we are trying to set failsafe values for empty filed when a value is required by OC
We will also check for some logics to fix issues. Ex: don't use OpenUsbKbDxe.efi when KeySupport is enabled, or Enable ProvideCustomSlide when it is required
If you have any question please let me know
This is how files are handled
As this gif is too fast download it and open with Preview
Now config.plist
We take SampleCustom.plist from latest OC -> Docs folder as our base for our new config.plist
for every entry in SampleCustom.plist we search the same entry in user's config.plist
if we find it then we compare the types
if they are the same then we set user's defined value into SampleCustom.plist
if types are different then OC default failsafe value is used
For array of dictionary entries in SampleCustom.plist we take the first item and create an empty template from that item
example for a kext:
a valid Kernal > Add entry
our generated empty template
Now we have a template for Kernel Add and we can fill the fields by values from users config.plist when the type is the same
So when OC team introduce a new field user will have it automatically
if that field requires a value then (we will see later for this case*) ocvalidate will throw an error about that so the user can make manual changes
After updating all fields we proceed into "additional OC Fixes"
You can find details into the code source just here.
Here we are trying to set failsafe values for empty filed when a value is required by OC
We will also check for some logics to fix issues. Ex: don't use OpenUsbKbDxe.efi when KeySupport is enabled, or Enable ProvideCustomSlide when it is required
If you have any question please let me know