Holy balls of shit … I got this to show up in the plugins list >.<
I want to be clear about the existing issues, as well as potential changes that could effect your use of certain controls.
NOTE: I have not added default event consumption as of yet… this is for people to play around with and give feedback on general usability, things they would like to see changed, etc… so, you have been warned =) - This is no longer an issue. Default event consumption should be in place and working correctly.
NOTE: Also wanted to mention that when you are creating controls and placing objects, the Y coord is flipped for you so you don’t have to think upside-down. On the other hand, when manipulating objects remember that the Y coord is flipped on you. A for-instance where you might do this: Showing a menu from a button… if you would like it to show below the button as expected, you would use:
float y = button.getAbsoluteY()-menu.getHeight()
to place it correctly. Cases where you actually need to do this for yourself are rare, but worth the mention!
First, changes that WILL effect usage:
Style are NOT implemented on this control and therefore will be subject to change that could effect usage.
Free-float ranges (i.e. percents for non-stepped dials) are NOT being forwarded to the the onChange event.
I’ve disabled the call back for development purposes which, in essence, makes this control non-functional until the next release (which will be very soon… couple days at most) - I had time to fix this due to build fail.
I just want to reserve the right to update this control as needed. The version that is being released in the simple (all text) version
If you apply your own theme and make a local copy of Common.xml document, there is a chance that new tags will added and will require you to copy/edit any these to your local copy. The two that I am fairly sure are going to happen soon would be the addition of Dropdown Highlight Color and Tab Focus Color. I can see this being updated past this at some point, however… nothing in the foreseeable future past these two.
There are few other controls that are not implementing their own styles yet, but leveraging the super classes instead. This will eventually change.
Now, the changes that will NOT effect usage (outstanding issues):
The visuals for displaying text ranges does not update properly when you select a range that is larger than the display area of the text field.
The Paste function has been disabled for the time being.
Default keyboard usage is not working properly at the moment. The effect varies depending on the type of button (i.e. standard buttons seems to work properly, however toggled buttons including checkboxes do not untoggle properly.
Because the sliders thumb can reside within or overhang the track, the eval of percent for free-floating values are not being set by the correct element making it difficult to quickly select value 0 or value 100 while dragging the thumb if the Slider is set to trackContainsThumb when creating the control.
Controls outside of a form are not losing focus properly when a form element is selected.
Controls with tab focus are not losing focus when you click into the scene (outside the GUI).
Other non-issue related items:
Some new methods have been added to different control and I’ll be updating the documentation here as I can.
You’ll notice a few controls with nothing in the source… these have been held back for dev purposes. They are:
LoadScreen - which I don’t think I have started yet, though, the a placeholder may exist.
Ummm… that’s all I can think of off the top of my head.