Site Discussion • Re: Small docs suggestions

Hello, I am currently working on a 2nd PR for the docs fixing and adding some other stuff but I want a suggestion.

I have a question regarding documentation for plugins, I recently tested a Frosted Glass fork and wanted to use Disabled=1 to remove it from applying the window style effect to the window, though it still did.
Upon some researcher (building a test plugin myself), I've discovered that Disabled=1 on plugins acts funny, even if you have that option on, Initialize and Finalize still execute, and Reload with DynamicVariables=1 updates at the Update(=1000) set for the skin.
Reading what Disabled=1 dose, it just stops the measure from updating it's values, so the Update and GetString function in plugins (I couldn't create a pointer in those 2 functions to test though).

So... How should this be communicated on the docs?

• Should it exist only on the guidelines page to explain this behavior?

  What dose the Disabled option do to a plugin? If set to 1, the measure value is never updated, only stopping the execution of the Update and GetString functions. Every other function (Initialize, Reload, Finalize etc.) still executes. You should write your own code to detect if the Disabled value is set to 1 and make the skin act accordingly in order to save resources.

• Or should this be added on both the CPP and C# pages as a Note, along with maybe communicating what UpdateDivider dose too to those functions?
• Or is this a bug?

Statistics: Posted by Jeff — Yesterday, 9:49 pm

---