Re-write get config in karaoke skin bindable.

[andy840119]

After #927 has been implemented, it's time to refactor this part.

What's need to be concern(or can be thinking):

• [ ] we can throw the whole lyric class object or note object to get the style.
• [ ] should change the style in drawable object if bindable changed.
• [ ] need to think about how to interact with config.
• [ ] public readonly Bindable<IDictionary<int, string>> BindableLayoutsLookup = new() should be adjusted.
• [ ] should deal with style change in internal.

[andy840119]

https://miro.com/app/board/uXjVOZkakKw=/?invite_link_id=352441695809 Wait until all spec done in miro.

[andy840119]

Damn it looks like a piece of shit.

[andy840119]

Another version. Now looks like a turkey shit I guess. Not that bad as previous version.

[andy840119]

And should notice that:

• if update property in skin editor will also trigger style change in main editor, should make sure that only should contains one instance.

[andy840119]

Guess it might be the final version.

[andy840119]

[NOTE] another question:

• should use lots of bindables?
• or just call EditorSkinProvidingContainer.sourceChange? > because it's how ColoursSection trigger hitobject change color in composer page.

[andy840119]

should use lots of bindables

pros:

• wrap all get skin logic, we just need to throw the hit object then got it's layout and style.

cons:

• should make sure handle all the bindable.unbindall logic(might be unsafe).
• hard to remove from dictionary if hit object has been destroyed.

call skin.sourcechange

pros:

• damn simple to implement.

cons

• should get skin provider.
• change skin in skin page does not affect editor because they use different skin.

conlusion

• maybe we can implement the interface and save the bindable first(not implement the remain step)