ThemeListener or the access to create our own

Discussion in 'Client & Site Suggestions' started by SlashnHax, Apr 22, 2015.

  1. This would be pretty awesome and useful for a few UI related things :)

    Arbiter says he's fine with ColorPalette being exposed too.

    Pls :D
    @Cloud, @Arbiter
  2. Arbiter should know how complicated it would be to allow users to "install themes" because he designed the system to begin with. In regards to ThemeListener, if it's really wanted it would be easy to setup.
  3. By "Create our own" I meant create our own ThemeListener, not Themes :p

    It would be appreciated, I'm currently detecting Theme changes a pretty horrible way xD
  4. Your own listener is easy, just check if the string returned by Themes#getCurrentStylesheet() changes.
  5. That's exactly what I'm doing at the moment xD Although I do it far too often
  6. Although that's doable, a proper event driven system would push the event when it changes and not have to worry about constantly checking the current return value.
    Defeat3d likes this.
  7. Not to mention it's probably very easy to locally inject new themes... but I'm gonna crawl back in my corner now :p
  8. It's available in the next release :p
    Defeat3d likes this.

Share This Page