[futurebasic] Re: [FB] Still grinding away lol

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : January 2008 : Group Archive : Group : All Groups

From: Brian Stevens <bstevens33@...>
Date: Sun, 27 Jan 2008 17:24:17 -0700
On Jan 27, 2008, at 4:45 PM, Robert S wrote:

> Hello again,
> I am reading the manual and studying the samples diligently. I find  
> the examples for making radio buttons, for instance very  
> complicated. These examples are not one liners like the opening a  
> file examples is.
Welcome to modern programming.

> If there are empty place holders in the code (two commas) I have no  
> idea what might have gone there if anything.
Successive commas are place holders for parameters that are not  
provided in that particular instance. When not provided, those  
parameters have default values. You would need to check the syntax in  
the reference manual for the specific statement to see what is being  

> Is there a reference I can buy somewhere that explains all of this?
No. Everything that is available comes with FB. The only extra books  
were written by  Frank Turovich years ago but they apply to an older  
version of FB. The books are available on Steve Stratford's web page  
at this link:

The "LFB" means Learning FB - just download all the files in this  
directory. Keep in mind this is OLD FB 2 and not FB4 but it still  
might give you some help.

> Is there some way to code a radio button, for instance, by just  
> simply specifying the x,y coordinates of the button’s location on the
> opened window and the get a return value to indicate if it has been  
> pushed or not?
Yes, but it isn't all one step. Do you understand the EVENT DRIVEN  
MODEL for GUI programming Robert? Your statement indicates you are  
expecting the interactive console approach of days of yore.

> a = radioButton 1 , (x,y) , ”Button 1 title text”
> b = radioButton 2 , (x,y) , ”Button 2 title text”
> I know I am a bit naive to expect it that simple, but does it  
> really have to be so complicated?
There are two steps:
1) creating the button on the window
2) responding to when the button is clicked

These steps happen in different places at different times. If you  
don't understand the event-driven model, this will be greek and  
you'll be forever trying to fit a square peg in a round hole. I'll  
see if there is some write up on this topic. Anyone else with a good  
description please chime in.

Brian S.