> - Am I thinking about learning fltk the right way? is there a > fundamentally smarter way to learn how to perform some of > these higher level passing of variable typed actions between > classes that I am missing based on this little story I just told?
I'm not sure you *are* proceeding in the best way, to be frank. You probably want to get a firmer grounding in C++ to understand the relationships between things, and you maybe do not want to start from Fl_File_Chooser, it is a complex and specialised widget. Better to start from something simpler... There are a number of fltk specific tutorials on the web, and Greg's video tutorials too. They would probably be helpful. http://www.seriss.com/people/erco/fltk-videos/ http://www.seriss.com/people/erco/fltk/ http://www3.telus.net/public/robark/ Might help for starters. > - other than what comes with the code, is there a repository > of *.fl programs that have examples of how to pass variables > from class to class, function to function? The above links might help a bit. > - What is the deal with the missing definitions of functions > tied to Fl_File_Chooser like favoritesCB(), newdir(), and > update_preview()? Where are they defined ever? are they > already in some compiled library where the code is unaccessible? No, they are there in the source. Maybe you haven't looked in the right place? They are defined in the file Fl_File_Chooser2.cxx. The file chooser is implemented over several compilation units, making it more complex to understand for a starting point - this is one reason why I suggest you start from a simpler widget... > - i picked 1.1.9 since it seemed it was the most stable well > working release. Are the things I want to do (like creating > classes similiar to Fl_File_Chooser) easier in 1.3 or 2.0? 1.1.9 is probably the best choice, as it is the most stable. What you are trying to do is essentially the same in all 3 anyway. > - Do I really want to try to recreate Fl_File_Chooser in > order to get it's functionality (...at some step a window > pops up for the user to create a selection, like an integer, > then when they say ok, that integer is passed back to the > code that called the instance of the integer selection > window...)? are there better ways to think about it? This is just creating a dialog to query for user input. There are simpler examples you can start from. Also, when thinking about GUI issues, it often helps if you *don't* try and design things to happen serially, in sequence. With GUI stuff, it is often the case that many things can be happening effectively in parallel, so thinking about the implementation in a manner that embraces that often makes things simpler. > - From how I describe my issues, do you think it is a lack of > understanding how to learn fltk or a lack of understanding > c++ that is getting me caught up here? How much C++ do you know? 'fraid, from your questions, that you might be just getting started, so a little time invested in getting a grounding will help long term. Hopefully the links above will show you a few things to get you heading in the right direction. SELEX Sensors and Airborne Systems Limited 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
