I was just in the mood to create an Axe GUI library and I thought "Why not?".

So it's not really a library since I use subroutines to create frames, buttons and dialogs.

So that you can have an idea of how this works, take a look at the code to draw the ABOUT button you can see in the demo:

sub(DB,40,42,30,10
Text(46,44,"ABOUT
As simple as that!

Let's take a look at its event when pressed:

If getKey(54)
[80C0E0F0F8F0B818->O
If X>40 and (X<70 and (Y>42 and (Y<52
sub(DD,"ABOUT","PROGRAM MADE","BY DAVID","GOMES"
Repeat getKey
End
End
...
End


So you have just learnt the two Drawing subroutines, DD (draw dialog) and DB (draw button).

There is not a DF (draw frame) yet, I am tidying it up to make it all a subroutine, but when finished it'll work like this:

sub(DF,"TITLE",1,0
The 1 (which could be a 0) is for X button or no X button to close the frame.
The 0 (which could be a 1) is for allow [CLEAR] to exit or don't allow [CLEAR] to exit.

This is just a demo, but I hope the library can have some uses I'll be making a few more Drawing Routines for other kinds of buttons, listboxes, etc. Not sure of how to make a textbox though.

Probably they can be in separate files (the routines) instead of being in the same program as the main program.

What do you think?

Looks pretty good!
Looks like DCS7 cursor thingy

Thanks

I finished the Draw Frame subroutine and here's my code for drawing the GUI in the GUI demo now:

sub(DB,30,30,30,10
Text(34,32,"BUTTON
sub(DB,40,42,30,10
Text(46,44,"ABOUT
sub(DF,1,"TITLE

And that's all!!!

Wow great job scout!

That is really impressive. It looks almost exactly like the way you do Windows stuff, just way easier.

Update



I added a status bar, very similar to Windows's, which can be created by writing:

sub(SB,X,"TEXT"

X is the X position of the text, for example, for the image above I wrote sub(SB,62,"GUI DEMO.

I optimized the subroutines and the main code (in the loop) is getting much shorter. The GUI DEMO is only 2000bytes for now (the compiled version).

Attached is the source code of the GUI. It works better if compiled with Axe 0.5.1

Quote from: Qwerty.55 on April 06, 2011, 01:06:46 pm

Looks nice, but you could optimize the location detection routine if you are willing to accept aligned buttons,

What do you mean with that?

Currently you're using M>X and N<X to kind of "trap" the cursor and detect it. However, you can take advantage of the fact that Axe doesn't use decimal math to get the position of the cursor with two lines and half as many comparisons per button. The disadvantage is that you're forced to give up some accuracy and flexibility in where you can put your buttons. Here's a demonstration of what I mean:



As you can see, the buttons are all triggered by clicking on them when the cursor is inside of their "area." It's a simple matter to only define those areas that you want clicked and the size of each click area can be fully modified.

I think what Qwerty means is that because the buttons are all located on a grid instead of randomly placed, you can add some optimizations. So correct me if I'm wrong, but you can find the cursor position on the grid by using x/width and y/height. Then using the 2 grid coordinates you can see if a button exists there.

I used a system that qwerty would like, but also added:

-pic support
-scroll bars (working)
-input boxes
-scripting language

Very nice Ashbad