Hello,

As some of you may know, I am writing a GUI dll and editor at the moment.
This brought up some question, or let me say problems.

First of all, a speed vs compatibility problem:
Using panels for the GUI-elements would be better, if you want to have to
have the same layer system as in the native GameStudio system. (If you
have any other elements with a layer, they would work as intended) -
but that would be slow... The other method would be using draw_*
commands, that would be faster than panels, but your elements would
always be below the GUI.

Okay, a quick test changed the situation a bit - it seems that
panels are not really slower (maybe even faster D: ) than draw_ calls.



Next problem: Image source
There are some plans for the image source of the elements. The first is
the simple "use a image for every state of the element" which is very
self explaining. The next method is, that all states (of a button e.g.)
are in one picture, that is tiled. Another method is using .fx (shader)
to create those elements procedurally. This prevents ugly scaling and
the like.




There will be many features, that are not available in the standard
GameStudio GUI, an alternative input (way better than inkey/inchar -
tested!), a nice and usable standard image set, the great editor wink and
easy usage.


Thanks,
Marian

Drawmode
single choice
Votes accepted starting: 10/12/11 08:32
Image source
multiple choice
Votes accepted starting: 10/12/11 08:41
Last edited by Rei_Ayanami; 10/12/11 18:52.