Hey guys 'n' gals, I'm someone who started programming back in (gasp) '65, actually writing a mainframe program.
I've done 360 Assembler, Cobol, fortran, C, Pascal, APL, and invented the Xmodem protocol that got many early computer hobbyists "online" in the last 70's, and with superb hardware hacker Randy Suess, invented the Bulletin Board System in '78, giving people something HOBBY based to call in to. .
SO after tens of thousands of lines of assembler, I finally graduated to a bit of Pascal, C, etc, and can "learn under the duress" of needing something small, pick up some Perl, or VBA, or whatever. (I NEVER NEVER could understand PROLOGUE, with its goal seeking, etc).
I'm now a retired IBMer after 44 years, and wanting to program in something other than my beloved KEDIT macros, and being quite ADD and etc have trouble focusing on really comprehending "Object Oriented".
I learned the "fundamentals" of Windows programming thanks to AUTOIT3, i.e. the idea of putting stuff out there and waiting for the OS to tell you someone did something with your GUI interface.
I am struggling terribly with Code::Blocks and wxwidgets, for while a quick install and sample program worked great in console mode, there's always something funky with wx like finding "Oh, you have the wrong library" (unknown unwind something). Right now I'm wondering if I can't have compiled wxwidgets to another DRIVE than C::B and gcc etc are installed on - for copying the directories from E: to C: some things started working.
I'm also confused by the plethora of places you can poke in your path, (haha) i.e. "set environment variables", then "settings" for compiler, linker, etc. So right now I have wxmsw28d_core undefined in the linker, but I compiled with 2.9.4, but I see nothing *_core except wx_core.dsp, so I become lost again.
QUESTION: In searching documentation, some of it is dated, and points to older versions, so I would like to take my struggles and document them, as to the steps to follow, etc. There are too many things in the current documentation that say things like "check your config files" which is aimed at someone who has done this many times before, i.e. KNOWS WHICH CONFIG FILES, etc.
Good to be here! Looking forward to learning more.