Samples Gallery

[TerryRitchie]

Update: Nope QBzerk is running around mazes 1980's Arcade game style. Opens with Asimov's 3 Laws for robots. I think I heard a clip from Pink Floyd.

Read those laws again ;-)  The robots rule in this game.

[bplus]

Ah, that makes more sense for this game :) You know I might have missed that the first time too,  deja vu again!

[STxAxTIC]

bplus, saw your recent post.

It was supposed to be two ZIP files, appended to the original post.

Okay, weird how they fit in Programs...

(yall're turning me into clippy)

[bplus]

bplus, saw your recent post.

It was supposed to be two ZIP files, appended to the original post.

Okay, weird how they fit in Programs...

(yall're turning me into clippy)

Sorry, that is what I tried for but https://www.qb64.org/forum/index.php?topic=2273.msg115066#msg115066

[STxAxTIC]

Oh man yeah I'm getting tired, missing some of the updates. Thanks again m8.

[RhoSigma]

@RhoSigma and @SMcNeill, do you guys want to point me at anything of yours?

EDIT:
Just put on hold for a while, just found another quirk in it, let you know when ready...


EDIT2:
So finally here's the correct routine, there was a mistake in the negative value barrier check.
Unfortunately I can't correct it in the mentioned post below, as that thread is already locked...

Code: QB64: [Select]

1. '---------------------------------------------------------------------
2. 'Function:  Convert any given dec/hex/oct number into a binary string.
3. '           Can handle positive and negative values and works in that
4. '           similar to the QB64 built-in HEX$ and OCT$ functions.
5. '
6. 'Synopsis:  binary$ = BIN$ (value&&)
7. '
8. 'Result:    binary$ --> The binary representation string of the given
9. '                       number without leading zeros for positive values
10. '                       and either 8/16/32 or 64 chars for negatives,
11. '                       depending on the input size.
12. '
13. 'Inputs:    value&& --> The pos./neg. number to convert, may also be
14. '                       given as &H or &O prefixed value.
15. '
16. 'Notes:     You may also pass in floating point values, as long as its
17. '           represented value fits into the _INTEGER64 (&&) input, hence
18. '           approx. -9.223372036854776E+18 to 9.223372036854776E+18.
19. '           Different from HEX$ and OCT$, BIN$ won't throw an overflow
20. '           error, if this range is exceeded, but the result is probably
21. '           wrong in such a case.
22. '---------------------------------------------------------------------
23. FUNCTION BIN$ (value&&)
24. '--- option _explicit requirements ---
25. DIM temp~&&, charPos%, highPos%
26. '--- init ---
27. temp~&& = value&&
28. BIN$ = STRING$(64, "0"): charPos% = 64: highPos% = 64
29. '--- convert ---
30. DO
31.     IF (temp~&& AND 1) THEN MID$(BIN$, charPos%, 1) = "1": highPos% = charPos%
32.     charPos% = charPos% - 1: temp~&& = temp~&& \ 2
33. LOOP UNTIL temp~&& = 0
34. '--- adjust negative size ---
35. IF value&& < 0 THEN
36.     IF -value&& < &H0080000000~&& THEN highPos% = 33
37.     IF -value&& < &H0000008000~&& THEN highPos% = 49
38.     IF -value&& < &H0000000080~&& THEN highPos% = 57
39. END IF
40. '--- set result ---
41. BIN$ = MID$(BIN$, highPos%)
42. END FUNCTION
43.  
44.  

NOTE: The function here is obsolete and buggy, use for reference only!!
The only thing I think of, regarding the &B enhancements in v1.4, would be to replace the old, slow, and non-negativ numbers able BIN$ in the ToolBox board with this one: https://www.qb64.org/forum/index.php?topic=1933.msg112096#msg112096

[Ashish]

@Qwerkey
It runs fine on my machine. Sky is looking good. Can you share a screenshot of that? Have anyone else found this issue?
Ok. It is fine to *not* to my "Moving into the matrix rain" program.
Oh! There's a games section too..
@Qwerkey @bplus Please add my game Hunter's Revenge https://www.qb64.org/forum/index.php?topic=345.msg2322#msg2322

[RhoSigma]

bump: https://www.qb64.org/forum/index.php?topic=2233.msg115086#msg115086

[bplus]

The only thing I think of, regarding the &B enhancements in v1.4, would be to replace the old, slow, and non-negativ numbers able BIN$ in the ToolBox board with this one: https://www.qb64.org/forum/index.php?topic=1933.msg112096#msg112096

Hi Rho,

Makes sense to update toolbox BIN$ with complement to &B enhancements in QB64 v1.4 by same author.

I think we want to replace BIN$ in Toolbox with the one found in "A few pushes to Development Build" Reply #35, last Edit Dec 17, 2019"
https://www.qb64.org/forum/index.php?topic=1933.msg112096#msg112096

So that is what I will try.

[RhoSigma]

I think we want to replace BIN$ in Toolbox with the one found in "A few pushes to Development Build" Reply #35, last Edit Dec 17, 2019"
https://www.qb64.org/forum/index.php?topic=1933.msg112096#msg112096

So that is what I will try.

NO - NO - NO
I wrote I still found another bug in it, please take the corrected function from here instead: https://www.qb64.org/forum/index.php?topic=2233.msg115086#msg115086

[bplus]

NO - NO - NO
I wrote I still found another bug in it, please take the corrected function from here instead: https://www.qb64.org/forum/index.php?topic=2233.msg115086#msg115086

Roger that but can you guess why I got confused?

IMO you should have not made that note but I bet you were trying to be careful :)

I have it changed, how is it now?

[bplus]

Roger that but can you guess why I got confused?

IMO you should have not made that note but I bet you were trying to be careful :)

I have it changed, how is it now?

Oops, needed to update the URL too, OK now what?

@STxAxTIC had to use the whole length in URL to point exactly to RhoSigma's reply, I got a demo and screenshot myself.

@RhoSigma does the output from demo look OK? (neg numbers are a bit of surprise for me.)

[bplus]

@Qwerkey @bplus Please add my game Hunter's Revenge https://www.qb64.org/forum/index.php?topic=345.msg2322#msg2322

@Qwerkey @STxAxTIC  what do you say to every member (over a certain level of contribution to this forum) getting 1 game of their choosing, be it theirs or someone else? This sort of falls in with _vince idea too. The game can be replaced as they progress and mature.

[RhoSigma]

Roger that but can you guess why I got confused?

IMO you should have not made that note but I bet you were trying to be careful :)

I have it changed, how is it now?

Well sorry b+,
yes it looks correct now, so other people can use it without issues.

Just noticed the mistake a few minutes after my first post. Wish there would be a delay before a post is actually shown in the forum, and that one could completly revoke the post within the delay time, or at least tick it to be postponed until the author finally releases it.

Also the locking of threads comes contra productive here, as I can't change the codebox in the "Development" thread to contain the corrected version. Hence everybody who's searching the forum for BIN$ and stumbles over the buggy version first instead of the now correct version in the ToolBox, will probably use the buggy function, at least until it bites his ass.

In the future I'll restrict myself to only posting codeboxes/attachements in the "Programs" board, where no locking is active and I'm able to correct things when needed.

Oh, just see another reply, so here is the answer for that one.

The output looks as intended by me, here an example to show pos./neg. number behavior at the _BYTE barrier:

Code: QB64: [Select]

1. '  128 =         10000000 (8 unsigned data bits)
2. '  127 =          1111111 (7 unsigned data bits)
3. ' -127 =         10000001 (  normal sign + 7 data bits)
4. ' -128 = 1111111110000000 (extended sign + 7 data bits)

note the sign extension for -128, so it can be distinguished from +128, it's similar at the INTEGER/LONG barriers.

However, if you have better sugestions it should be easy enough to adapt the function.

[Qwerkey]

@bplus: When doing the Samples Gallery I am aiming to include at least 1 superior program from all high contributors.  It seems only fair.