Samples/Toolbox re-awakening. Call for entries.

[The Librarian]

As the topic says, it's time we expand our Samples Gallery and Toolbox. Please reply to this post with links to existing threads in Programs with code that qualifies.

First things first though - is everyone happy with the filled circle/ellipse code up there?

[bplus]

Here is a link to a number of tools:
https://www.qb64.org/forum/index.php?topic=1511.0

First, I have been very happy with filled circle and ellipse code actually has come in handy for me, thanks!

[SMcNeill]

ConvertOffset: http://qb64.freeforums.net/thread/52/convert-offset-integer64

MEMSort: http://qb64.freeforums.net/thread/28/mem-sort

ExtendedTimer: http://qb64.freeforums.net/thread/20/extended-timer-uet

SaveImage: (needs updated on forums to the latest version and then linked)

POSIX File and Dir Listing to Arrays: http://qb64.freeforums.net/thread/63/file-directory-listing-arrays

Spell Checker: https://www.qb64.org/forum/index.php?topic=1587.0

MemToHex: https://www.qb64.org/forum/index.php?topic=1553.0

All of the above are handy little routines which I keep in my toolbox and have reused in a ton of different ways.

[STxAxTIC]

Thanks boys.

I happen to know the Librarian connects through a mobile hotspot so updates may a bit slow.

The old "saveimage" routine is a gem Steevo! Resurrect that for us, I bet the newbies will be thrilled!

[STxAxTIC]

Not sure where to begin this discussion, but may as well be here.

So MEM is different than all QB64 commands, amirite? It's strange from a QB45 point of view, takes a minute to master from a QB64 point of view, and I've noticed that almost half of Steve's tools involve it.

So the question is, should we cram MEM-related stuff into its own category? Something all-inclusive to MEM, including tutorials. It may be sortof a turnoff to see all the MEM stuff scattered into everything else. --- OR, is this 100% off base? ... because Toolbox entries should be black boxes that shouldnt be looked into... hmmm... opinions?

[Petr]

Hi. I am again last.


Please look to my previous answer  https://www.qb64.org/forum/index.php?topic=1566.msg107875#msg107875

[pforpond]

As the topic says, it's time we expand our Samples Gallery and Toolbox. Please reply to this post with links to existing threads in Programs with code that qualifies.

First things first though - is everyone happy with the filled circle/ellipse code up there?

I'm curious as to what 'code that qualifies' means :) Is there a criteria to me met?

[STxAxTIC]

I'm curious as to what 'code that qualifies' means :) Is there a criteria to me met?

You got it m8.

https://www.qb64.org/forum/index.php?topic=178.0

https://www.qb64.org/forum/index.php?topic=1062.0

[pforpond]

You got it m8.

https://www.qb64.org/forum/index.php?topic=178.0

https://www.qb64.org/forum/index.php?topic=1062.0

Thank you. Looks like I probably don't comment my code enough to qualify. I'd submit this but I didn't post the source code in the thread and it was all spaghetti anyways :)

[SMcNeill]

Not sure where to begin this discussion, but may as well be here.

So MEM is different than all QB64 commands, amirite? It's strange from a QB45 point of view, takes a minute to master from a QB64 point of view, and I've noticed that almost half of Steve's tools involve it.

So the question is, should we cram MEM-related stuff into its own category? Something all-inclusive to MEM, including tutorials. It may be sortof a turnoff to see all the MEM stuff scattered into everything else. --- OR, is this 100% off base? ... because Toolbox entries should be black boxes that shouldnt be looked into... hmmm... opinions?

_MEM really isn’t that strange; it’s QB64’s updated take on PEEK and POKE.  Since “toolboxes” tend to contain those routines which you use over and over again, they tend to be as efficient as possible, so they’ll plug into any program — and you can’t beat the speed and performance of direct memory access I Which MEM gives.  I think a lot of toolbox code will make use of MEM, when it can.  Probably no reason to separate them into their own subfolder. ;)

[bplus]

Not sure where to begin this discussion, but may as well be here.

So MEM is different than all QB64 commands, amirite? It's strange from a QB45 point of view, takes a minute to master from a QB64 point of view, and I've noticed that almost half of Steve's tools involve it.

So the question is, should we cram MEM-related stuff into its own category? Something all-inclusive to MEM, including tutorials. It may be sortof a turnoff to see all the MEM stuff scattered into everything else. --- OR, is this 100% off base? ... because Toolbox entries should be black boxes that shouldnt be looked into... hmmm... opinions?

Categories would be great!

Who wants to look for a saw in the sandpaper pile or a screwdriver in metric socket sets?

But can this be done on a forum? 0f course it can, if there is a Will to do it!  ;-)

If categories are by function, MEM routines would span many categories for a speedier way to do a numbers crunching task, is my thought.

[bplus]

For my first official submission I would like to present Split1000:

We worked on this a bit here at the forum this is my version from my toolbox.

Code: QB64: [Select]

1. 'notes: REDIM the array(0) to be loaded before calling Split '<<<<<<<<<<<<<<<<<<<<<<< IMPORTANT!!!!
2. SUB Split1000 (mystr AS STRING, delim AS STRING, arr() AS STRING)
3.     ' bplus modifications of Galleon fix of Bulrush Split reply #13
4.     ' http://xmaxw.[abandoned, outdated and now likely malicious qb64 dot net website - don’t go there]/forum/index.php?topic=1612.0
5.     ' this sub further developed and tested here: \test\Strings\Split test.bas
6.     DIM copy AS STRING, p AS LONG, curpos AS LONG, arrpos AS LONG, dpos AS LONG, LD AS INTEGER
7.  
8.     copy = mystr 'make copy since we are messing with mystr when the delimiter is a space
9.  
10.     'special case if delim is space, probably want to remove all excess space
11.     IF delim = " " THEN
12.         copy = RTRIM$(LTRIM$(copy))
13.         p = INSTR(copy, "  ")
14.         WHILE p > 0
15.             copy = MID$(copy, 1, p - 1) + MID$(copy, p + 1)
16.             p = INSTR(copy, "  ")
17.         WEND
18.     END IF
19.     curpos = 1
20.     arrpos = 0
21.     LD = LEN(delim) 'mod
22.     dpos = INSTR(curpos, copy, delim)
23.     DO UNTIL dpos = 0
24.         arr(arrpos) = MID$(copy, curpos, dpos - curpos)
25.         arrpos = arrpos + 1
26.         IF arrpos > UBOUND(arr) THEN REDIM _PRESERVE arr(UBOUND(arr) + 1000) AS STRING
27.         curpos = dpos + LD
28.         dpos = INSTR(curpos, copy, delim)
29.     LOOP
30.     arr(arrpos) = MID$(copy, curpos)
31.     REDIM _PRESERVE arr(arrpos) AS STRING 'need this line? YES to get the ubound correct
32. END SUB
33.  
34.  

Function: it takes a string, say a whole file gulped in one go with a binary get, and parses the string into a string array using: the specified string to split, delimiter and array name to load.

My version handles splits delimited by spaces specially by removing extra spaces first. 1000 was added to name when Steve recommended only using REDIM _PRESERVE every 1000 times or so instead of at every split.

What else do you need? I have the code used to test the routine.

I am partial to handling the space delimiter specially because this was originally used for space only delimited parser for interpreters I played with but that can be removed and special filter applied in separate function.

[STxAxTIC]

Okay, we've heard from both sides on the "mem categories" thing...

I think for now, until the collection proves unruly, that our existing tag system will work. Nay on categories. I'll "tell" the Librarian... :-)

[STxAxTIC]

bplus-

I The Librarian was looking to add BIN$ found at https://www.qb64.org/forum/index.php?topic=1511.0

Code: QB64: [Select]

1. OPTION _EXPLICIT
2. PRINT 2 XOR 3 ' 2 is 10 in binary, 3 is 11 in binary where there is a bit in one but not the other for 2 and 3 in one's position
3. PRINT 2 XOR 4 '= 6?  yes
4. PRINT 2 XOR 10 ' = 8,  10 XOR 1010 = 1000 = 8
5. PRINT &B0
6. PRINT &B1
7. PRINT &B10
8. PRINT &B11
9. PRINT &B100
10.  
11. 'does QB64 reverse &B numbers conver HEX$ for base 16, OCT$ for base 8, no base 2?
12. DIM test AS _INTEGER64
13. DO
14.     INPUT "Enter integer to convert to binary "; test
15.     PRINT "Dec2Base$(test, 2) = "; Dec2Base$(test, 2), "BIN$(test) = "; BIN$(test)
16.     PRINT "and  VAL(BIN$(test)) ="; VAL(BIN$(test))
17.     PRINT
18. LOOP UNTIL test = 0
19.  
20. 'what is limit _integer64 can take
21. DIM i AS _INTEGER64
22. i = 1000000000
23. DO
24.     i = i + 1000000000
25.     PRINT i
26. LOOP UNTIL i >= i + 1
27. PRINT i
28.  
29. 'maybe _BIN$
30. FUNCTION Dec2Base$ (nDec AS INTEGER, bs AS INTEGER)
31.     DIM n AS INTEGER, p AS INTEGER, pow AS INTEGER, d AS INTEGER, b$
32.     n = nDec 'copy this because or nDec gets changed effecting main code
33.     WHILE bs ^ p <= n
34.         p = p + 1
35.     WEND
36.     FOR pow = p TO 0 STEP -1
37.         IF n >= bs ^ pow THEN
38.             d = INT(n / bs ^ pow)
39.             IF d < 10 THEN
40.                 b$ = b$ + _TRIM$(STR$(d))
41.             ELSE
42.                 b$ = b$ + CHR$(65 + d - 10)
43.             END IF
44.             n = n - d * bs ^ pow
45.         ELSE
46.             IF b$ <> "" THEN b$ = b$ + "0"
47.         END IF
48.     NEXT
49.     IF b$ = "" THEN b$ = "0"
50.     Dec2Base$ = b$
51. END FUNCTION
52.  
53. FUNCTION BIN$ (integerBase10 AS _INTEGER64)
54.     DIM i AS _INTEGER64, pow AS INTEGER, b$
55.     IF integerBase10 = 0 THEN BIN$ = "&B0": EXIT FUNCTION
56.     i = integerBase10 'copy
57.     pow = 0
58.     WHILE i > 0
59.         IF i AND 2 ^ pow THEN
60.             b$ = "1" + b$
61.             i = i - 2 ^ pow
62.         ELSE
63.             b$ = "0" + b$
64.         END IF
65.         pow = pow + 1
66.     WEND
67.     BIN$ = "&B" + b$
68. END FUNCTION
69.  

Just want to make sure that:
(i) This is the proper link
(ii) Code in top post is the code you want to show
(iii) You know entering "0" for input causes the program to loop infinitely

Thanks!

------------------------------------------------------------------------------------------

EDIT:

Regarding Split1000: Yes, we need some dead-simple test code for that, 'specially given the huge warning at the top.

[bplus]

Hi STxAxTIC,

Here is just the BIN$ function with just the tester code for it.
(BTW that wasn't an infinite loop that was a test of _INTEGER64, I was testing a number of things with main code.)

Code: QB64: [Select]

1. OPTION _EXPLICIT
2.  
3. ' QB64 can reverse &H numbers with HEX$ and &O numbers with OCT$
4. ' but what about &B numbers?
5.  
6. ' Here is BIN$
7.  
8. DIM test AS _INTEGER64
9. DO
10.     INPUT "(0 ends test) Enter a positive integer to convert to binary "; test
11.     PRINT "BIN$(test) = "; BIN$(test)
12.     PRINT "and  VAL(BIN$(test)) ="; VAL(BIN$(test))
13.     PRINT
14. LOOP UNTIL test = 0
15.  
16. 'BIN$ creates a string = the base 2 equivalent of the Base 10 positive integer
17. 'and is prefixed with &B to work with VAL
18. FUNCTION BIN$ (integerBase10 AS _INTEGER64)
19.     DIM i AS _INTEGER64, pow AS INTEGER, b$
20.     IF integerBase10 = 0 THEN BIN$ = "&B0": EXIT FUNCTION
21.     i = integerBase10 'copy
22.     pow = 0
23.     WHILE i > 0
24.         IF i AND 2 ^ pow THEN
25.             b$ = "1" + b$
26.             i = i - 2 ^ pow
27.         ELSE
28.             b$ = "0" + b$
29.         END IF
30.         pow = pow + 1
31.     WEND
32.     BIN$ = "&B" + b$
33. END FUNCTION
34.  

I will get going on split1000 next.