> yes i care about it, i want to create a robust, quality
> appliction, and thanks to the support on these pages i have
> come a long way in the past 6 months or so. I need to review
> the docs in depth regarding the show(argc, argv) because i
> cannot understand where all the switch parameters are being
> referenced when my app at the user level will only ever pass
> a file path. so where are these tooltips and bkgd colors? i
> thought they had been supplied in my constructos in fluid?
> and if they are redundant when argc is greater than 1 then i
> need to reiterate them somehow?
I really think you should just use Fl::args() to sort this out.
See the browser.cxx demo for an example of how this works.
Basically, at the head of your program, you call Fl::args(), and it
"eats" all the fltk-specific options and returns a count of how many it
ate.
If the count is less than argc, you know there are still options there
to parse that Fl::args() does not recognise, so you can then handle them
yourself.
An example would go somethng like:
int main(int argc, char **argv) {
int opts_fltk_used;
Fl::args(argc, argv, opts_fltk_used));
// did we use up all the args?
If (opts_fltk_used < argc){
my_arg = argv[opts_fltk_used];
}
else {
// no more options passed
}
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
