Varsuuk
January 2nd, 2021, 01:13
I have so far 99% of the time worked on the "host" as I work on my MoreCore ruleset extension.
I came across an odd thing when investigating a bug where when I add a character to the CT it does not check my "asc/descending" flag until it is flipped (it uses right one but both controls are visible so the Asc, last control, is the visible one) - the issue was obvious, I added handlers but I did not add a check on initializing.
So when I loaded up the ct_host.xml and ct_client.xml, I noticed my scripts had update() and onInit(), respectively, defined in the <script> tag. I thought I typed while writing it but it seems I got this from the same files of the same name in MoreCore.
Is there a reason they vary this way? I noticed in the same file, for some controls onInit() is defined, others update().
I have yet to do anything in client mode and the options they check are meaningless until/when I look up what MCC2/MCC2C/MCC3 etc MEAN... - perhaps onInit() is used when the option should never change again (but... it CAN right? What does that mean then?) and update() for ones where you want to react to?
I may be able to answer this myself once I get to work on the ClientUI - but figured I'd ask in case anyone saw this and knew the answer on why it is supposed to be that way.
I came across an odd thing when investigating a bug where when I add a character to the CT it does not check my "asc/descending" flag until it is flipped (it uses right one but both controls are visible so the Asc, last control, is the visible one) - the issue was obvious, I added handlers but I did not add a check on initializing.
So when I loaded up the ct_host.xml and ct_client.xml, I noticed my scripts had update() and onInit(), respectively, defined in the <script> tag. I thought I typed while writing it but it seems I got this from the same files of the same name in MoreCore.
Is there a reason they vary this way? I noticed in the same file, for some controls onInit() is defined, others update().
I have yet to do anything in client mode and the options they check are meaningless until/when I look up what MCC2/MCC2C/MCC3 etc MEAN... - perhaps onInit() is used when the option should never change again (but... it CAN right? What does that mean then?) and update() for ones where you want to react to?
I may be able to answer this myself once I get to work on the ClientUI - but figured I'd ask in case anyone saw this and knew the answer on why it is supposed to be that way.