Hello, for a few days now I've been working on a program you could use to create GUIs for your BASIC programs. This program is based on defining clickable areas. The only real downside is that the inputs for the commands are stored in a list.
What kinds of elements can it render? Do you have any screenshots demonstrating how it works? What inspired you to create this project?
it can render a mouse, a large window, a small window and a clickable area. And sorry, but no screenies yet. But here's some syntax
Code:
Code:
Large Window:
{1}
prgmGUI
Small Window:
{2}
prgmGUI
Mouse:
{3}
prgmGUI
Make a Clickable Area:
{5, top left X, top left Y, bottom right x, bottom right Y}
prgmGUI
returns: id to ans
Return if a clickable area has been clicked:
to be continued...
Thanks, that helps. How fast is the mouse? It seems like you have a fairly good design so far; keep us posted on progress.
- spud2451
- Power User (Posts: 481)
- 06 Nov 2012 12:37:36 pm
- Last edited by spud2451 on 06 Nov 2012 12:39:43 pm; edited 1 time in total
spud2451 wrote:
it can render a mouse, a large window, a small window and a clickable area. And sorry, but no screenies yet. But here's some syntax
Code:
also to answer your question kerm, the mouse is fast but not exactly smooth.
Code:
//Large Window:
{1}
prgmGUI
//Small Window:
{2}
prgmGUI
//Mouse:
{3}
prgmGUI
//Make a Clickable Area:
{5, top left X, top left Y, bottom right x, bottom right Y}
prgmGUI
//returns: gui item id to ans
//Return if a clickable area has been clicked:
{6, Gui item id}
prgmGUI
//returns: 1 or 0 depending if area was clicked
//Return mouse click Coordinates:
{7}
prgmGUI
//Returns: a list containing the coordinates of the last mouse click
Shouldn't the {7} function be unnecessary? I would expect {3} (the mouse function) to return both the coordinates of the click and the ID (if any) of the item clicked on. That's what the DCSB Libs GUIMouse does, anyway.
Edit: By not smooth, you mean it skips? What's the granularity, 8 pixels per jump? 4?
Edit: By not smooth, you mean it skips? What's the granularity, 8 pixels per jump? 4?
well kerm im trying to keep it simple and fast. thats why i used an axe writen asm program to do the drawing. everything else is in basic though.
one cool thing about the whole id system is that you can store it to a variable to use it again later.
example:
Code:
one cool thing about the whole id system is that you can store it to a variable to use it again later.
example:
Code:
{5,1,1,10,10}
prgmGUI
ans→a
{3}
prgmGUI
{6,a}
If ans
then
Disp "you clicked it"
End
Register to Join the Conversation
Have your own thoughts to add to this or any other topic? Want to ask a question, offer a suggestion, share your own programs and projects, upload a file to the file archives, get help with calculator and computer programming, or simply chat with like-minded coders and tech and calculator enthusiasts via the site-wide AJAX SAX widget? Registration for a free Cemetech account only takes a minute.
» Go to Registration page
» Go to Registration page
Page 1 of 1
» All times are UTC - 5 Hours
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Advertisement