07-26-2022, 09:15 PM
(07-26-2022, 07:51 PM)mnrvovrfc Wrote: If I were a programmer and not working for a multinational I wouldn't be very eager to fix things for other people, only modify it for my needs.
Honestly speaking, that's about how QB64 has always been developed. Somebody will speak up and say, "I wish we could do X with QB64." If it's simple enough, one of the nice folks who push stuff into the repo will say, "Hey, no problem! I know where and how to do that -- give me a moment!" Usually, in those cases, the change/addition/fix can be ready for testing by the next day.
IF there's more to it than that, the answer is, "Ummm... *You* might want to check in XYZ area in the source. You might figure out how to change/add what you want there. If you have questions, ask, and we'll help **all we can**."
NONE of us are the original designers of this source/project. I doubt *anyone* working on it knows 100% how/why/where everything works exactly as it does. We like to help folks do what they want, but we're not the original code creators of the project. We have to dig, research, and decipher how and why things interact as they do, and that's often a very time consuming task. Since, as you mentioned, nobody earns a single cent working on this project, each developer has their own list of personal needs -- and their priority is to work on those things first.
User suggestions do get worked on, as free time and interest allows, but the main "push foward" for development has always been, "What features do the devs need *themselves*, the most?"
