In case you are not familiar with what a drop target is.  It can be a box or window open by a program to accept a list of files.  To be dropped into the drop target box.   The drop location could also be a location inside a program that will process a list of files dropped there.

Using shell and dir to capture a list of files is too much sledgehammer approach to a pin prick need.  This will most certainly require a DLL call.  And I am clueless to know how.  This could be a good routine inclusion, would become a nice touch for QB64 tools.  Stuffing the clipboard would be likely the best way to get them in.

Thanks

you would need someone who knows C++, and a deep understanding of the target OS or platform, and has a lot of free time.

Industrial control guy's love the PI's to death.  They know "C", want to get rid of expensive PC-104 controllers.  Faster, wifi and they have no free time.  They are payed to do it all.  Even if they have to use compute modules to do it.  It's cheaper faster in the end.

Something like print using "###.##" ?

It's not just the single thing.  Double and float do it too.  Only thing that does not do it is integer. But then I lose all .## 's

I know it's 4/1/22 but the math is like 2+2=3.999999
ps.
Tried using the using "###.##".  Looks right for a formatted output. I still want to know why the math got Borked.

The problem with getting QB64 into the Raspberry Debian repositories is that not all the code compiled by QB64 on the PI works.

That on line rather says it all.  (Not ready for prime time.)

QB64 is so much more closer in usage to qb45 that everybody knows from way back when.  All other flavors of basic in the windows environment require esoteric knowledge of how to compile or how basic works.  Not for the beginners.  I knew INFORM did not compile on the PI.  Because right off the bat, a special call to a windows function occurs.  Rendering PI compile very moot.  I was not aware of code alignment problems with PI compiled QB64.  I have experienced segment faults with Linux.  They can be a very painful process to correct sometimes.

I was hoping for a quick way to get a slice of the Raspberry PI crowd.  I know for a fact Industry (especially process and control) are moving away from PC-104 (1k+) costs.  To very cheap PI's.  Even the compute modules which focus on professional crowds are a good solution.

So how do we get 150,000 new QB64 users.  With sales of 30 Million unit's in 2019, who knows where that number is today with covid locking people at home.  And any available unit being scalped at ridiculous prices.  Or any online listing announcing stock all gone within 15 minutes.  The little sought after PC is the Raspberry PI.  If we can get 0.5% of the user base to install it's 150K new users.

So what will it take to get QB64 listed in the Raspberry Debian Repository ?  There are many locations the where repositories are holding code.  I could be wrong but all we need is one developer to compile and post a image of QB64 and support files.  I now the install script exists to compile QB64 but it's not "ALL" new user friendly.  I think we need to "APP" QB64 into a repository package.

So can we make this happen ?  I would love to help but I am too newbie even after a couple of years using Linux to know how to do this.

Thanks
BTW, With all the competition QB64 has under windows.  Nobody has listed there basic in the repository.  We could be a first.
 

Come again?

You missed the joke.... never mind.

I would never list any basic flavor as a programming language on a Resume.  Unless it was under hobbies.

Basic never got good publicity.
In fact "programming snobs" would look at it as.  This idiot does not know that good program structure flow is important.  re: goto's and such.

I like the fact I can just sit down and bang out a decent "QB64" program without a Flow chart or process specification.  If I am going to write some narly code I will comment the shit out of it.  It has happened in the past and will again in the future.  I will sit down to modify old code that was not "greatly" commented.  Look at it and think "What the F' was I on when I wrote that"

So, I will certify anybody who, takes the time to comment his programming.  Poor reason for no comments "Because it was hard to write, it should be hard to fix."  I have seen too much assembly code get tossed because the next programmer did not understand it and rewrote it.  Only to go back in "my self" later and fix the timing problems.  Rewritten code was a time critical routine and was written that way.  It was optimized for clock cycles and bytes.

TLDR: QB64 Certification is not going to happen.  Enjoy the fact, almost anybody can read and use basic.