12-12-2022, 06:27 PM
..Or end up doing it over and going full re-Pete.
Two schools of thought here, and both have merit.
1) Do it yourself to build confidence in your coding ability. Whatever the style, if it works, it works.
2) Use other people's libraries and routines. Faster, hopefully proven, and you get to spend more time on other part of your project.
The C/C++ community and I hear the Python community are big on telling newbies to just use libraries. I drove those C people nuts when I wanted to make a custom keyboard input routine in C/C++. I did it, but getting help was a bit of a struggle, because hardly anyone there knew anything about a non-library approach.
For me, my custom keyboard routines are fun to build and always allow complete customization and flow-through events. Can't do that, no matter how much better LINE INPUT gets.
Just my 2-cent, and since those pennies are from the Roman Empire Era, they're actually worth something.
Pete
Two schools of thought here, and both have merit.
1) Do it yourself to build confidence in your coding ability. Whatever the style, if it works, it works.
2) Use other people's libraries and routines. Faster, hopefully proven, and you get to spend more time on other part of your project.
The C/C++ community and I hear the Python community are big on telling newbies to just use libraries. I drove those C people nuts when I wanted to make a custom keyboard input routine in C/C++. I did it, but getting help was a bit of a struggle, because hardly anyone there knew anything about a non-library approach.
For me, my custom keyboard routines are fun to build and always allow complete customization and flow-through events. Can't do that, no matter how much better LINE INPUT gets.
Just my 2-cent, and since those pennies are from the Roman Empire Era, they're actually worth something.
Pete