I will be adding to this little corner of forum my QB64 code as I check them in through Linux QB64 v 1.5 (I don't need debug), they already work fine in Windows v2.0 

Sudoku is by far my most used and favorite app I've created with QB64 and version 2020-08-08 has been tested allot! 

The Sudoku app has 2 screens, the first is just an Info/Help screen from which you enter a level of play.
 
Levels are mostly determined by the number of clues you are given, the more the easier.
The lower levels are for practice or flash card like automatic skills builder. 6 gives intermediate puzzle 7 a little harder intermediate 8 would be hardest but takes longer to build for unique solution and may end up a level 7 puzzle.
9 gives you a blank puzzle and puts you in Make Mode and you can click in a puzzle from newspaper or book.
Remember to click back to Puzzle Mode when done making the puzzle.

The Puzzle screen has some menu buttons:
The first on left toggles the solution, ON OFF
The 2nd from left toggles the check cell mode. ON will not allow you to make a simple error of putting a 2nd number in row, column or 3x3 cell block and beep you if you try. Just because you are not beeped, doesn't mean it is correct.
The Load and Save buttons work with one Temp file. Just rename that file or copy and rename if you want to store a special puzzle, perhaps one that was particularly hard. Otherwise every time you save a puzzle the last one in Temp will be overwritten.

Play: Is basically clicking a number from number palette and left click a cell to answer or right click to toggle a note of that number on and off again. To remove a number clicked in, set the number palette to 0, click that in and then reset to number you want to do next.





  Sudoku 2020-08-08.zip (Size: 539.28 KB / Downloads: 84)

You guys may have seen something like this somewhere before, but this is the original, prettier version than the one that exists inside the QB64 IDE. 

If you're signed in as a member of the forums here, you'll see that we have two new subforums there: NSFW (18+) and Freedom to Speak.

Both of these are completely off-topic and password protected forums.  In fact, they're hidden forums to boot, that only registered members can decide if they want to participate in them, or not.  One thing people always objected about with "off topic" discussions in the past was that "they don't look professional for a site" and blah, blah, blah...

To address those concerns, the forums are hidden from the general public by nature.  Folks have to go through the trouble to sign up and become a member of our boards to even know they exist.

Safeguard #2, these forums are each password protected.  If you're going out of your way to join a forum, read up and ask folks about a password to a subforum, and then decide to be offended at the contents of those forums after having to jump through such hoops...   /sigh   I guess I'll just be happy to offend you, as it's obvious you went out of your way in an attempt to get in that state.  

So what are these two forums??  And what features do they offer that others don't?  Why would any sane person bother with jumping through the hoops to get into them?

Both forums are dedicated to the idea of us being built around a community, and for folks to have a freedom to speak with each other.  One thing I always hated about the old forums, before they disappeared, was the Off-Topic forum being taken away.  There should be some place where people who share the same hobby -- in this case QB64 -- can come together and get to know and talk to each other as people and not just as programmers.  Why shouldn't the users be able to talk about politics, or sports, or religion, or their favorite TV shows?  As members of the same community, they already have at least one trait in common -- they like the BASIC language -- so why shouldn't they be allowed to talk and chat and explore if they share other interests as well??

I dunno!!  In my opinion, they should!

And thus, we have the two dreaded sub-forums that people either tend to love, or else they tend to hate.

left click to zoom in
right click to zoom out
mouse wheel to change zoom window
'+' or '-' key to increase or decrease iterations

Waving and shaded 3D US flag.  Drawn according to official specification

Dedicated to all farmers who code with Basic ;-))

I found this cool little program written by the guy from "The Coding Train", so I ported it to QB64. He has a lot of cool stuff on his channel and I've learned a lot from his videos.

Seems like that's the question that everyone has been asking here lately -- "What the heck happened to the old forums?  Why did everything disappear on us?"

I've been a little busy setting up the new forums and migrating the wiki over for us, bot now that those things are more or less complete, I wanted to take time to do into details and try and explain what's happened over the last week or so, so everyone can understand how we got to be where we currently are.

Things first started to change back in QB64 World back sometime in January.  Fellippe suddenly made an announcement to the community that someone new was popping up in the community and taking over as CEO for the project.  An unexpected move -- why the heck did a hobbyist language need a CEO to manage things, anyway?? -- but one which ultimately changed almost nothing at the time.  RC Cola was introduced to the project, he barely spoke to anyone or got involved with anything, and life moved on with him just more or less existing in the background.

***********************

Time flows, as time will, and suddenly we find ourselves at around a week ago.  Fellippe suddenly decides to just pack up and walk away from the project.  He goes from being a member of the forums to just becoming a "guest".  The Inform channels in the Discord are closed.  He makes no real announcement about anything, and just walks.  People who reach out to him via personal messages and such, get told that he's "Left the project for good and won't be back, for his mental health."  Fellippe did a lot of different things, and he put up with a lot, and it seemed like he'd more or less hit his breaking point and just said waltzed off into the sunset like any good Old Western hero would.

This left RC Cola as suddenly holding the reigns to the project.  At that point, much like at the point where we're at now, people became a little nervous about the state of the project.  RC Cola was asked, "What's the future of QB64?  What do you think QB64 is??"   His response to anything like that was more elusive than a politician two days before election day -- "I'm not going to get into that.  I'm not going to say..."

He's not going to answer any questions about the plans for the project?  Not even going to try and say what he thinks the project is about??

And then, someone brought up the rules of conduct which we were all operating under -- and if you guys are like me, you didn't have a single clue about them!!




post image


Now, if you guys notice there's a line in there right above the page break that REALLY bothered me.  "Any media uploaded to QB64 sites, are the property of the QB64 Project."

For me, that meant that if I kept working on my little QB64 Bible, and sharing it for the members of the forums to make use, comment, and help point out things that might need editing, that once it was finished, I wouldn't be able to sell a hard copy of it anywhere!!  After all, the QB64 Team would OWN my work!!  If I did publish it, they could sue me for stealing THEIR property!!

And *this* glaring problem was brought up to RC Cola.  His response was just as lackluster as when asked about his plans for QB64.  His response was, "It's better for us to have too much control over stuff posted, than not having enough."

He didn't think that type of rule was over the top at all!!

So, at this point, people *really* started to complain and act up in the Discord channel.  You could almost taste the displeasure in the air, the feeling was so palpable.  Folks were getting quite upset at everything that was going down and was being said.

Rather than try and diffuse the situation, RC Cola decided to drop the mighty Hammer of Justice on people.  Folks were getting silenced for almost nothing in the Discord channel.  People were being banned from Discord.  At this point, one could almost take bets on who was going to be the next person to get kicked from the Discord channels. 

It was at this point that RC decided he was basically the one true ruler of QB64 World:





It was also around this same time when I found myself in RC Cola's crosshairs.  
 

Quote:RCcola1987 — 04/15/2022

@SMcNeill you have done a lot for the project and this is the only reason i didnt just ban you right now. Neo Nazi content is not allowed ANYWAEAR on this discords nor is it allowed on discord as a whole. I fyou remove the posts and stop this i will not ban. most of my family died fighting againt Hitler in ww2 and i will not stand for that. most things i will let slide in teh off topic but this is just astounding and not expected from someone like you. 

Quote:

1. RC... You know what... I've tried being a nice guy and ignore all the crap that's been going on, but I just can't do it anymore. At no point have I shared any neo-nazi content, nor do I stand for anything Nazi related. I'm certain I can hop in the car and head to the cemetery and point to just as many graves from my family who fought against the war, as you ever could. From our last genealogical study (my father was an amateur genealogist), we can count 106 members who died in WWI and WWI from both my mother's and father's side. All I posted was links to a lyrics.com collection of SONG LYRICS... in a topic which was tagged "off-topic" and flagged NSFW. There's nothing objectionable about what I posted, but what [b]IS[/b] objectionable is you thinking you're some sort of second rate dictator for the project just because Fellippe left.\
   
2. [7:56 PM]
   Here, let me play dictator for a while: [b]I was the [i]only[/i] person who Galleon ever officially welcomed into the QB64 Team, before he stepped down.[/b] My code contributions to the project go all the way to version 0.5 or so, and were in the code well before Fellippe or anyone else branched off Galleon's github account and started pushing their own version of QB64. At no point have I ever given up on my intellectual property rights for the code which I added into the project. Galleon had NO license on QB64 back in the day, and the code anyone committed to the project always retained the property of the coder. Fellippe and them may have pushed to add a MIT license to [i]their[/i] github and QB64 project, but I never gave up the rights to my intellectual property.
   So here's my little asshole dictator demand: Take ALL my work out of the repo. I no longer feel that the project as it exists supports the spirit of BASIC with which I wrote my code and inserted itself into the project, and I refuse to give any rights to keep my code active and inside the source any longer. Failure to remove all my contributions from the language will result in my pursuing legal recourses against copyright infringement.
   

To run QB64 on a Raspberry PI, you need to do a few things to QB64 in order to compile and run programs.

Also, right now, QB64 will only run on a 32-bit running on the RPI. I haven't yet gotten it to work on 64-bit OS's. I am still researching if this is possible. It just might be a PI ARM issue. I am experimenting with settings in the ARM chip itself and GCC/G++ compiler options from the ARM technical documents I've obtained from the IEEE. Very few in my local chapter have had experience in the ARM, and none with QB64.

However, there are a few issues that are part of the PI's ARM processor that cannot be easily fixed in QB64.

Most programs will compile and run fine. Others will get one or both of the following issues:

1) Racing Conditions (can appear as SIG BUS errors)
2) Misaligned Addresses, or misaligned word errors (appears as SIG BUS errors)

For the most part, identifying where the racing condition is occuring (you will need to do a gdb session to find out), a simple _DELAY .3 will fix it. Racing occurs when QB64 creates multiple threads, and since QB64 isn't really a multithreaded programming language (the backend C++ is), there can be issues.

There are two ways to fix the misaligned address/word issue. One way is to use the -fsanatize compiler option. However, the better fix for most of these issues has been added to the common.h file provided. The code that fixes this and other non-x86 issues is: