Post by: bplus on July 15, 2019, 11:20:40 am
But without a toolbox, one has to figure it out again and again when the occasion arises.
First the story, I was checking into XOR even before Steve provided the link in the Xbox tunnel of love thread when I discovered that &H has the reverse HEX$ and &O has the reverse OCT$ but poor 'ole &B has squat!
So here is BIN$ for your edification and toolbox:
Code: QB64: [Select]
- 'does QB64 reverse &B numbers conver HEX$ for base 16, OCT$ for base 8, no base 2?
- INPUT "Enter integer to convert to binary (0 to quit) "; test
- n = nDec 'copy this because or nDec gets changed effecting main code
- p = p + 1
- n = n - d * bs ^ pow
- Dec2Base$ = b$
- '2019-12-02 latest eliminates &B prefix
- j = j + 1
Who needs Bill, the toolbox librarian, just start your own thread! ;- +
BTW, wouldn't it be better if HEX$(base10Integer) returned the string as "&H...." and OCT$ as "&O..." ?
You know, label the number base if it is not your standard base 10.
EDIT: For library code, probably should DIM everything, something a librarian might remind us of if one were present. ;-))
EDIT: 2019-12-01 more elegant version of BIN$
EDIT: 2019-12-02 reconsidered again with RhoSigma's input no &B prefix, also get rid of the limit test for integer and the other junk in demo! see reasons in reply #46
UPDATE: This stuff has been incorporated into QB64 since v1.3 I think, 1.4 for sure.
Post by: bplus on July 15, 2019, 12:19:52 pm
Code: QB64: [Select]
Today we have a classic one in our midst. ;-)) which reminded me of this old code exercise for people who need to get comfortable with using SUBs and FUNCTIONs.
EDIT: line 19 too long, too many redundant calls to MID$ for same thing. I bit the bullet and added another variable for clarity.
UPDATE: Hardy an auspicious start for a mighty thread ;-))
Post by: johnno56 on July 15, 2019, 04:38:19 pm
Post by: bplus on July 28, 2019, 05:18:12 pm
Code: QB64: [Select]
- '2019-07-28 All enclosed in a sub, possible feed it score and see how it stacks up.
- '2019-07-28 fix to fill all 10 slots.
- '2019-07-29 2nd fix with an n > 10 check, change to a function and get GoAgain reply.
- ' ref https://www.qb64.org/forum/index.php?topic=1511.msg107586#msg107586
- Dim score, again$
- 'testing function with random scores, would be good to start with
- Print "End of test."
- ' This FUNCTION creates a file in the same folder as your .bas source or .exe
- 'EDIT: 2019-07-29 change to FUNCTION to combine Top Ten update functions with Go Again reply.
- fName$ = "Top 10 Scores.txt" '<<< since this is toolbox code change this as needed for app
- n = n + 1
- Print "You have made the Top Ten!"
- scores(n) = compareScore
- settleScore = -1
- n = n + 1
- Close #1
- Print "There is a slot open for your name and score."
- Close #1
- Print "You are first into file!"
- Close #1
- topTenGoAgain$ = dummy$
Works OK for me. How did name$ get to be NAME$ here in forum post?
Update: Sorry, I did not test the sub enough, only with increasingly good scores. But what happens if score is not better and you have 9 slots left in Top Ten? You fill the next slot, Fixed.
Update: 2019-07-29 found another thing to fix, check if n > 10 Also changed the SUB to a FUNCTION and used it to get Go Again information from the player. It seems the perfect time to ask the player if they want to go again and combining functions saves the player a 2nd question and key press answer to make. This is demo'd in the test code.
2021-10-27 Modified for new Function change in QB64 v 2.0
Post by: SMcNeill on July 31, 2019, 07:39:09 am
Code: [Select]
SUB SubState (toggle)
STATIC DefaultColor, BackGroundColor, Font, Dest, Source
IF toggle THEN
_FONT Font
COLOR DefaultColor, BackGroundColor
_DEST Dest
_SOURCE Source
ELSE
Font = _FONT
DefaultColor = _DEFAULTCOLOR
BackGroundColor = _BACKGROUNDCOLOR
Dest = _DEST
Source = _SOURCE
END IF
END SUBWhen writing a lot of subs, I've found that a majority of them tend to require the same things at the top and bottom of them so that they play nicely with my main routines -- a means to save the main program state and then restore it upon exit.
For example:
Code: QB64: [Select]
Now, the above SUB isn't very library friendly, and it's a PITA to plug into most programs. It changes the default color that we we're printing with when we entered the sub, and it's now something completely different when we exit the sub. It just doesn't play nice with others.
So how to fix that?
Code: QB64: [Select]
Note: This version of SubState isn't for use with recursive routines, or for routines which call others which alter default values on us. If you guys are interested in it, I'll share it as well for you. Use this for quick save/exit routines for single call SUB/FUNCTION as illustrated above. ;)
Post by: bplus on July 31, 2019, 08:22:35 am
Here is the tail end (currently, it keeps needing more things) to my mBox (messageBox) sub and inputBox sub:
Code: QB64: [Select]
- 'put things back
- _PUTIMAGE , backScrn
- COLOR fg, bg
- _FREEIMAGE backScrn
- _FREEIMAGE mbx
- 'clear key presses
- LOCATE curRow, curCol
- 'clear mouse clicks
- _LIMIT 100
I was wondering if I was missing more items. I did not do _FONT nor _SOURCE but I do put back row and col, and _AUTODISPLAY / _DISPLAY setting and found the need to clear both mouse click and key press (esc or enter mainly need to be cleared so main program isn't short circuited).
Collecting all these settings and then putting them back really distracts from the code for the procedure, so this could be very useful to use with tool box procedures. Thanks again, I will put a version of this in my toolbox.
Post by: bplus on July 31, 2019, 08:57:28 am
(Employs a scnState sub discussed earlier in this thread suggested by SMcNeill.)
Speaking of message Box here is my current version which I updated recently with better mouse button clear (I think) and adding of _DISPLAY / _AUTODISPLAY resets.
The advantage is you don't need Windows and since it is Tool Box code and not Library code, you can copy / paste into your program and are free to modify to needs of program eg, you won't like my colors for message box (I don't like my colors) but you are free to change to fit program you are using message box in. Trying to anticipate every mod change that might be needed for message box turns it into a complex Swiss Army Knife too awkward to be of practical use IMO. So this has the simple parameters of Title$ and message$:
Code: QB64: [Select]
- '
- ' 2019-05-18 new version of mBox developed from scrollWindow test code (Array Window.bas)
- ' hmm... old version saved curRow and curCol ? put back in
- ' new version clears mouse clicks
- ' 2019-07-25 save _autodisplay setting and set it back before leaving, rework clearing mb
- 'test #1 does message box work in screen 0
- 'mBox "Well?", "Test mBox in Screen 0" NO! for graphic screens ONLY!!!
- '2019-07-31 attempt to assimulate Steve's idea for saving and restoring the screen state
- ' before a sub messes with all the settings, so in future mBox and inputBox$ will need this
- ' helper sub. Damn the fan is back! Also fix this to make it easier to change colors.
- ' OK tests here now try scrollWindow and Geometry Circle Intersects...
- PRINT "REMINDER: press escape, enter or spacebar to exit the message box. Escape (again?) to exit this test."
- PRINT "Here is some stuff on screen."
- m$ = "This is the message for mBox in 800x 600 _NEWIMAGE setup, "
- m$ = m$ + "how does it handle a long line? Yeah! grab title bar and move this box around!" 'great
- mBox "This is Demo Title", m$
- INPUT "For next test [h | m] for mBox, [esc | space | enter] to quit it and then [esc] again to quit, enter for next test...", enter$
- 'draw stuff, until h or m press, then show message box
- WHILE 1
- k$ = INKEY$
- kh = 0
- kh = _KEYHIT
- ' _DISPLAY '<<<< comment out to see if _AUTODISPLAY mode, yep! good
- _LIMIT 60
- PRINT "OK where is this print line going to end up, hopefully under the last '# message done'." 'yes! Excellent!
- SUB doMessage
- DIM title$, mess$
- mess$ = mess$ + "Here is a long line that hopefully won't all fit across the screen, so I just keep going on and on ..."
- mess$ = mess$ + "until the screen is half full of this single long, long line so I can test the wrapping my code does "
- mess$ = mess$ + CHR$(9) + "This line started with a tab which should be replaced by spaces so now this line should be running too long. The End."
- title$ = "123456789012345678901234567890123456789012345678901234567890"
- mBox title$, mess$
- 'title$ limit is 57 chars, all lines are 58 chars max, version 2019-07-31
- 'THIS SUB NOW NEEDS SUB scnState(restoreTF) for saving and restoring screen settings
- bg = &H33404040
- fg = &HFF33AAFF
- 'first screen dimensions and items to restore at exit
- 'screen and current settings to restore at end ofsub
- scnState 0
- _KEYCLEAR '<<<<<<<<<<<<<<<<<<<< do i still need this? Yes 2019-08-06
- 'screen snapshot
- curScrn = _DEST
- 'setup t() to store strings with ti as index, linit 58 chars per line max, b is for build
- 'are there any new line signals, CR, LF or both? take CRLF or LFCR as one break but dbl LF or CR means blank line
- tail = "": ff = 0
- ff = 1 'found space flag
- tail = d + tail 'the tail grows!
- b = b + c 'just keep building the line
- t(ti) = b
- bxH = ti + 3: bxW = limit + 2
- 'draw message box
- _DEST mbx
- COLOR fg, bg
- 'now for the action
- _DEST curScrn
- 'convert to pixels the top left corner of box at moment
- bxW = bxW * 8: bxH = bxH * 16
- tlx = (sw - bxW) / 2: tly = (sh - bxH) / 2
- lastx = tlx: lasty = tly
- 'now allow user to move it around or just read it
- WHILE 1
- _PUTIMAGE , backScrn
- grabx = mx - tlx: graby = my - tly
- 'attempt to speed up with less updates
- tlx = mx - grabx: tly = my - graby
- _PUTIMAGE , backScrn
- lastx = tlx: lasty = tly
- _LIMIT 400
- kh = _KEYHIT
- _LIMIT 400
- 'put things back
- _PUTIMAGE , backScrn
- _FREEIMAGE backScrn
- _FREEIMAGE mbx
- scnState 1 'Thanks Steve McNeill
- ' for saving and restoring screen settins
- _FONT Font
- COLOR DefaultColor, BackGroundColor
- _DEST Dest
- _SOURCE Source
- LOCATE row, col
- _LIMIT 100
This will be soon be modified with my version of Steve's new subState (toggle) along with InputBox$
Update: 2019-07-31 11AM: OK modified with more complete srnState(restoreTF) SUB as promised but I see now Steve has improved his further into two SUBs, sheez hard to keep up! I also made it easier to modify colors in mBox sub, see fg, bg settings at top of sub for foreground and background.
Anyway mBox works well and tested in a couple of programs from which I caught bugs earlier:
Here I try semi-transparent background in mBox SUB.
2019-08-06 Update: _KEYCLEAR was needed when starting mBox, I found the test code that proved it.
comment removed from this line:
_KEYCLEAR '<<<<<<<<<<<<<<<<<<<< do i still need this?
Post by: SMcNeill on July 31, 2019, 09:52:59 am
Code: [Select]
SCREEN _NEWIMAGE(120, 25, 0)
PRINT "Currently my print cursor is here =>";
SLEEP
QPrint 10, 10, 4, "Then I jump to 10,10"
SLEEP
PRINT "But I'm still here! =>";
SLEEP
RQPrint 3, 3, 1, "Hello World"
SLEEP
PRINT "And, even after all the recursive work, I'm still here!!"
SUB QPrint (y, x, kolor, text$)
s = SaveState
LOCATE x, y
COLOR kolor
PRINT text$
RestoreState s
END SUB
SUB RQPrint (y, x, kolor, text$)
s = SaveState
IF kolor < 15 THEN RQPrint x + 1, y + 1, kolor + 1, text$ + "."
LOCATE x, y
COLOR kolor
PRINT text$
RestoreState s
END SUB
FUNCTION SaveState
TYPE SaveStateType
InUse AS INTEGER
DC AS INTEGER
BG AS INTEGER
F AS INTEGER
D AS INTEGER
S AS INTEGER
Disp AS INTEGER
CurX AS INTEGER
CurY AS INTEGER
END TYPE
DIM SS AS SaveStateType, Temp AS SaveStateType
SHARED NSS AS LONG 'Number of Saved States
SHARED SaveMem AS _MEM
IF _MEMEXISTS(SaveMem) THEN
'do nothing
ELSE
SaveMem = _MEMNEW(LEN(SS) * 255) 'Save up to 255 save states; More than 255 and we toss an error
$CHECKING:OFF
_MEMFILL SaveMem, SaveMem.OFFSET, SaveMem.SIZE, 0 AS _UNSIGNED _BYTE
$CHECKING:ON
END IF
'Data to Save
SS.InUse = -1
SS.F = _FONT
SS.DC = _DEFAULTCOLOR
SS.BG = _BACKGROUNDCOLOR
SS.D = _DEST
SS.S = _SOURCE
SS.Disp = _AUTODISPLAY
SS.CurX = POS(0)
SS.CurY = CSRLIN
$CHECKING:OFF
FOR i = 1 TO NSS
o = (i - 1) * LEN(SS)
_MEMGET SaveMem, SaveMem.OFFSET + o, Temp
IF Temp.InUse = 0 THEN
_MEMPUT SaveMem, SaveMem.OFFSET + o, SS
SaveState = i
EXIT FUNCTION
END IF
NEXT
_MEMPUT SaveMem, SaveMem.OFFSET + NSS * LEN(SS), SS
$CHECKING:ON
NSS = NSS + 1
SaveState = NSS
END SUB
SUB RestoreState (WhichOne)
DIM SS AS SaveStateType
SHARED NSS AS LONG 'Number of Saved States
SHARED SaveMem AS _MEM
$CHECKING:ON
_MEMGET SaveMem, SaveMem.OFFSET + (WhichOne - 1) * LEN(SS), SS
IF SS.InUse THEN
SS.InUse = 0 'Let the routine know that we're no longer in use for this handle
_MEMPUT SaveMem, SaveMem.OFFSET + (WhichOne - 1) * LEN(SS), SS
_FONT SS.F
COLOR SS.DC, SS.BG
_DEST SS.D
_SOURCE SS.S
IF SS.Disp THEN _AUTODISPLAY ELSE _DISPLAY
LOCATE SS.CurY, SS.CurX
END IF
$CHECKING:ON
END SUB
Notice here that we get a handle for a saved state, and then when we exit the sub we restore that handle. This allows us to have one sub call another sub, or recursively call itself, and yet preserves the original information without any problem for us.
One thing to note with this method: Just like GOSUB can run out of stack space if you call them and exit without using RETURN, this also has a limit of 255 states being saved at a time. IMHO, that's more than enough for any program I write, unless I've got a glitch somewhere where I'm exiting the sub/function without restoring values. (In which case, I've created a memory leak, and I'd want to find it and fix it anyway...)
Post by: bplus on July 31, 2019, 11:32:45 am
You know I just started wondering about multiple mBox windows going... how the setting for different windows up might be saved. You anticipated that.
But what happens if you close the windows / screens out of the order they were opened? You would be restoring the wrong settings. Or what happens should any of the other screens start messing with the their settings in between.
Might be a can or worms here, unless keep everything modal.
Post by: SMcNeill on July 31, 2019, 12:00:10 pm
Let’s say I have a red screen and print stuff on it.
Now, open a green box in the center of it, and preserve the background so you can restore it later.
Now, open a blue box in the center of that one, and preserve the background so you can restore it later.
If you close the blue box, then the green box, your background will go back to looking as it originally did.
If you close the green box first, then the blue box, your background is now red, with a green box where the blue one used to be. (You restored the original background when you closed the green box, but closing the blue box put the background behind it — the part of the green box it covered up — back onto the screen.)
As long as you call the routines and exit the routines in order, all is good. If they’re going to be truly “independent boxes” and not “pop-up boxes” which require closing them in order, then sequentially stacking settings won’t be possible. You’re looking at Z-order style handling at that point, which is a bit more than the routines above handle.
Post by: Petr on July 31, 2019, 12:16:24 pm
Example for four windows.
Code: QB64: [Select]
- g = 1
- x(g) = f
- g = g + 1
- g = 1
- y(g) = f
- g = g + 1
- position(N) = N
- NEXT N
- old = position(d)
- position(d) = 1
- position(R) = position(R) + 1
Previous code show you windows positions.
For correct view on screen then use Window nr.1 as UBOUND next array, Window nr.2 as second, Window nr.3 as third and Window with nr.4 as last - LBOUND.
For correct view on screen then just use
FOR ViewIt = Lbound(WindowArray) Ubound(WindowArray)
....
....
graphic operations
NEXT
As you see, UBOUND is last, so window nr.1 as UBOUND in array is always on top.
And you get the answer to the question - what if I close the window in a different order? Window numbers are reduced by one, minimized, or closed is deleted from the field FOR VIEW (so I suggest using an extra field only for window rendering and another field with window position, text, and so on) (so there will only be three), the same loop render it. There will be another graphic loop below the windows that will not be overwritten by the window array at this location if the window is closed before calling _DISPLAY. Pseudocode:
Loop for background drawing on screen
Loop for rendering windows
_DISPLAY
This way you can make transparent windows, behind which will run - spiders :).
Post by: bplus on July 31, 2019, 01:52:54 pm
You guys and your giant screens! Your demo does not fit my screen but OK because I am totally unprepared to take on a Windows management discussion in this thread. For this thread I have other fish to fry... ;-))
Good to know, you have worked on this problem though and are ready with help. Also I am so proud that spiders made such on impression on you! :)
Post by: Petr on July 31, 2019, 02:00:26 pm
Post by: bplus on July 31, 2019, 07:33:11 pm
Yes BPlus, Spiders are perfect. I hope I understood the topic correctly and did not respond quite badly? If so, just say it and I delete the post, I don't want to spam your tools thread.
Hi Petr, you are fine coder, no way a spammer!
To all,
Here is the a complementary tool to mBox that I wanted to get posted with mBox, inputBox$.
This lets you get some information from user without any disturbance of the screen. Like mBox you can grab the title bar and move it around the screen.
I combined that with cText, a way to print any size text around the midpoint x, y and overhauled the Top Ten screen used in Invaders bplus style.
inputBox$ and demo:
Code: QB64: [Select]
- _TITLE "inputBox$ tester.bas started 2018-10-26 need an input box for WS Editor"
- ' 2019-07-32 assimulate scnState(restoreTF) used to save and restore screen settings
- ' so sub can do it's thing and restore settings, Thanks Steve McNeill for starter code and idea.
- PRINT "Here is some stuff on screen."
- well$ = inputBox$("Well?", "Test inputBox$", 20)
- PRINT "inputBox$ returned: "; well$; ". Is this line printing exactly below last stuff sentence?" ' OK now with center fix too!
- 'draw stuff, until h or m press, then show message box
- WHILE 1
- k$ = INKEY$
- well$ = inputBox$("Well?", "Test call inputBox", 36)
- 'kh = 0 'should not need this to stop esc keypress in input box
- kh = _KEYHIT
- '_DISPLAY '<< should not need this
- _LIMIT 5
- PRINT "OK where is this print line going to end up, hopefully under the last inputBox returned." 'yes! Excellent!
- ' You can grab this box by title and drag it around screen for full viewing while answering prompt.
- ' Only one line allowed for prompt$
- ' boxWidth is 4 more than the allowed length of input, it needs to be longer than title$ and prompt$ also
- ' Utilities > Input Box > Input Box 1 tester v 2019-07-31
- 'colors
- ForeColor = &HFF000055 '< change as desired prompt text color, back color or type in area
- BackColor = &HFF6080CC '< change as desired used fore color in type in area
- White = &HFFFFFFFF
- 'items to restore at exit
- scnState 0
- 'screen snapshot
- 'moving box around on screen
- 'draw message box
- bxW = boxWidth * 8: bxH = 7 * 16
- _DEST ibx
- COLOR ForeColor, BackColor
- GOSUB finishBox
- 'convert to pixels the top left corner of box at moment
- bxW = boxWidth * 8: bxH = 5 * 16
- tlx = (sw - bxW) / 2: tly = (sh - bxH) / 2
- lastx = tlx: lasty = tly
- 'now allow user to move it around or just read it
- WHILE 1
- _PUTIMAGE , backScrn
- grabx = mx - tlx: graby = my - tly
- 'attempt to speed up with less updates
- tlx = mx - grabx: tly = my - graby
- _PUTIMAGE , backScrn
- lastx = tlx: lasty = tly
- _LIMIT 400
- kh& = _KEYHIT
- _LIMIT 60
- 'put things back
- scnState 1 'need fg and bg colors set to cls
- CLS '? is this needed YES!!
- _PUTIMAGE , backScrn
- _FREEIMAGE backScrn
- _FREEIMAGE ibx
- scnState 1 'because we have to call _display, we have to call this again
- inputBox$ = inp$
- finishBox:
- _DEST ibx
- COLOR BackColor, ForeColor
- _DEST curScrn
- 'from mBox v 2019-07-31 update
- ' for saving and restoring screen settins
- _FONT Font
- COLOR DefaultColor, BackGroundColor
- _DEST Dest
- _SOURCE Source
- LOCATE row, col
- _LIMIT 100
Here is cText, text and demo:
Code: QB64: [Select]
- DIM y, i
- PRINT "Hello World"
- 'test& = _NEWIMAGE(xmax, ymax, 32)
- 'DEST test&
- y = ymax
- y = y - 60 / i
- _LIMIT 5
- '_DEST 0
- '_PUTIMAGE , test&, 0
- PRINT "OK, blue?"
- fg = _DEFAULTCOLOR
- 'screen snapshot
- cur& = _DEST
- _DEST I&
- mult = textHeight / 16
- COLOR fg
- _FREEIMAGE I&
- 'center the text
- fg = _DEFAULTCOLOR
- 'screen snapshot
- cur& = _DEST
- _DEST I&
- mult = textHeight / 16
- COLOR fg
- _FREEIMAGE I&
Here is topTenGoAgain$ code and tester reworked with cText and inputBox$:
Code: QB64: [Select]
- '2019-07-28 All enclosed in a sub, possible feed it score and see how it stacks up.
- '2019-07-28 fix to fill all 10 slots.
- '2019-07-29 2nd fix with an n > 10 check, change to a function and get GoAgain reply.
- '2019-07-31 modify Top Ten Screen with cText and inputBox$
- ' 1. to make it look better, 2
- ' 2. for demo in thread "another one for the tool box"
- ' 3. improve Invaders look
- ' 4. test new revsions to inputBox$
- DIM score, again$
- 'for testing
- 'IF _FILEEXISTS("Top 10 Scores.txt") THEN KILL "Top 10 Scores.txt"
- 'testing function with random scores, would be good to start with
- ' This FUNCTION creates a file in the same folder as your .bas source or .exe
- 'EDIT: 2019-07-31 this function needs:
- ' SUB cText(x, y, pixelTextHeight, Colr)
- ' SUB inputBox$(prompt$, title$, maxBoxWidth)
- ' which needs scnState(restoreTF)
- fName$ = "Top 10 Scores.txt" '<<< since this is toolbox code change this as needed for app
- n = n + 1
- names$(n) = inputBox$("Please enter your name here:", "You have made the Top Ten!", 40)
- scores(n) = compareScore
- settleScore = -1
- n = n + 1
- CLOSE #1
- _DELAY 3.5
- CLOSE #1
- CLOSE #1
- topTenGoAgain$ = inputBox$("Press <Enter> to play again, enter q (or any) to quit... ", "Play Again?", 66)
- 'center the text around (x, y) point, needs a graphics screen!
- fg = _DEFAULTCOLOR
- 'screen snapshot
- cur& = _DEST
- _DEST I&
- mult = textHeight / 16
- COLOR fg
- _FREEIMAGE I&
- ' You can grab this box by title and drag it around screen for full viewing while answering prompt.
- ' Only one line allowed for prompt$
- ' boxWidth is 4 more than the allowed length of input, it needs to be longer than title$ and prompt$ also
- ' Utilities > Input Box > Input Box 1 tester v 2019-07-31
- ' This FUNCTION needs scnState(restroreTF)
- 'colors
- ForeColor = &HFF000055 '< change as desired prompt text color, back color or type in area
- BackColor = &HFF6080CC '< change as desired used fore color in type in area
- White = &HFFFFFFFF
- 'items to restore at exit
- scnState 0
- 'screen snapshot
- 'moving box around on screen
- 'draw message box
- bxW = boxWidth * 8: bxH = 7 * 16
- _DEST ibx
- COLOR ForeColor, BackColor
- GOSUB finishBox
- 'convert to pixels the top left corner of box at moment
- bxW = boxWidth * 8: bxH = 5 * 16
- tlx = (sw - bxW) / 2: tly = (sh - bxH) / 2
- lastx = tlx: lasty = tly
- 'now allow user to move it around or just read it
- WHILE 1
- _PUTIMAGE , backScrn
- grabx = mx - tlx: graby = my - tly
- 'attempt to speed up with less updates
- tlx = mx - grabx: tly = my - graby
- _PUTIMAGE , backScrn
- lastx = tlx: lasty = tly
- _LIMIT 400
- kh& = _KEYHIT
- _LIMIT 60
- 'put things back
- scnState 1 'need fg and bg colors set to cls
- CLS '? is this needed YES!!
- _PUTIMAGE , backScrn
- _FREEIMAGE backScrn
- _FREEIMAGE ibx
- scnState 1 'because we have to call _display, we have to call this again
- inputBox$ = inp$
- finishBox:
- _DEST ibx
- COLOR BackColor, ForeColor
- _DEST curScrn
- 'from mBox v 2019-07-31 update
- ' for saving and restoring screen settins
- _FONT Font
- COLOR DefaultColor, BackGroundColor
- _DEST Dest
- _SOURCE Source
- LOCATE row, col
- _LIMIT 100
and a screen shot of the revised screen after installed in Invaders b0_4:
Post by: SMcNeill on August 06, 2019, 01:41:10 am
Code: QB64: [Select]
- held$ = ""
- PRINT "Left pressed: "; left
- PRINT "Right pressed: "; right
- PRINT "Middle pressed: "; middle
- PRINT held$
- _LIMIT 10
- FUNCTION MBS 'Mouse Button Status
- CONST ClickLimit## = 0.2 '2/10th of a second to down, up a key to count as a CLICK. Down longer counts as a HOLD event.
- WHILE _MOUSEINPUT: WEND 'Remark out this line, if mouse main input/clear is going to be handled manually in main program.
- IF _MOUSEBUTTON(1) THEN 'If a button is pressed, start the timer to see what it does (click or hold)
- MouseHandler = 0: ButtonDown = 0: StartTimer = 0
- ELSE 'We've now started the hold event
- MouseHandler = ButtonDown + 3
One quick command to tell you if a button was clicked or held, for any of the 3 mouse buttons.
Post by: bplus on August 06, 2019, 09:11:46 am
And another rather simple routine for your toolbox collection -- a quick mouse handler.Code: QB64: [Select]
One quick command to tell you if a button was clicked or held, for any of the 3 mouse buttons.
Hi Steve,
Shall we assume you intended to set the Function MBS with the ButtonDown value before exiting function?
Code: QB64: [Select]
- held$ = ""
- PRINT "Left pressed: "; left
- PRINT "Right pressed: "; right
- PRINT "Middle pressed: "; middle
- PRINT held$
- _LIMIT 10
- FUNCTION MBS 'Mouse Button Status
- CONST ClickLimit## = 0.2 '2/10th of a second to down, up a key to count as a CLICK. Down longer counts as a HOLD event.
- WHILE _MOUSEINPUT: WEND 'Remark out this line, if mouse main input/clear is going to be handled manually in main program.
- IF _MOUSEBUTTON(1) THEN 'If a button is pressed, start the timer to see what it does (click or hold)
- MouseHandler = 0: ButtonDown = 0: StartTimer = 0
- ELSE 'We've now started the hold event
- MouseHandler = ButtonDown + 3
- MBS = ButtonDown '<<< fix set function with ButtonDown ???
hmm... second time in couple days you post a fine function but don't set the value, makes me wonder how much you test code before posting... maybe it's the meds or the summer heat?
wait... just making bplus feel useful ;-))
Actually I found this mouse code and tester interesting that Steve had posted a while back:
Code: QB64: [Select]
- ClickThreshold = 0.2 'down and up in threshold of a second to count as a click. If down for more then threshold, we just have a hold event.
- _LIMIT 60
- UpdateMouseInfo
- PRINT MouseX, MouseY
- PRINT MouseWheel
- SUB UpdateMouseInfo
- LeftMouse = 2 'clicked
- ELSE 'if it's still down
- LeftMouse = 0 'the mouse was just released
- leftdown = 0 'timer is cleared either way
- LeftMouse = 1 'the left mouse is down , timer should have already been set
- LeftMouse = 1 'the left mouse is down
- LeftMouse = 0
- MiddleMouse = 2 'clicked
- ELSE 'if it's still down
- MiddleMouse = 0 'the mouse was just released
- middledown = 0 'timer is cleared either way
- MiddleMouse = 1 'the middle mouse is down , timer should have already been set
- MiddleMouse = 1 'the middle mouse is down
- MiddleMouse = 0
- RightMouse = 2 'clicked
- ELSE 'if it's still down
- RightMouse = 0 'the mouse was just released
- rightdown = 0 'timer is cleared either way
- RightMouse = 1 'the right mouse is down , timer should have already been set
- RightMouse = 1 'the right mouse is down
- RightMouse = 0
I thought this useful because it handles the mouse wheel (my mouse has a wheel not a middle button) and left and right buttons.
Post by: SMcNeill on August 06, 2019, 10:15:20 am
Hi Steve,
Shall we assume you intended to set the Function MBS with the ButtonDown value before exiting function?
hmm... second time in couple days you post a fine function but don't set the value, makes me wonder how much you test code before posting... maybe it's the meds or the summer heat?
wait... just making bplus feel useful ;-))
Actually I found this mouse code and tester interesting that Steve had posted a while back:
I blame it on the stupid medication. :P
Tested, it works -- as long as I don't go in and halfway rename things to make them "simpler" when I finish them. (MouseHandler was the original name for the routine, but I renamed it to a simple "MBS" and didn't change everything like I should have, like a big idiot...)
Here's the version once again -- even enhanced this time to handle the middle scroll button for you! :P
Code: QB64: [Select]
- held$ = ""
- PRINT "Left pressed: "; left
- PRINT "Right pressed: "; right
- PRINT "Middle pressed: "; middle
- PRINT "Mouse Wheel Scrolled: "; scroll
- PRINT held$
- _LIMIT 10
- FUNCTION MBS 'Mouse Button Status
- CONST ClickLimit## = 0.2 '2/10th of a second to down, up a key to count as a CLICK. Down longer counts as a HOLD event.
- WHILE _MOUSEINPUT 'Remark out this block, if mouse main input/clear is going to be handled manually in main program.
- IF _MOUSEBUTTON(1) THEN 'If a button is pressed, start the timer to see what it does (click or hold)
- MBS = 0: ButtonDown = 0: StartTimer = 0
- ELSE 'We've now started the hold event
- MBS = ButtonDown + 3
Post by: bplus on August 06, 2019, 12:37:58 pm
This was needed when running complex dialog code like mBox or inputBox, it is important then to get the mouse and key press from dialog to NOT interfere with other mouse and key press events in caller code and vice versa...
It has been an ever evolving process to get everything to work together, here is getClick tested with latest version of mBox and inputBox from which I discovered that a _KEYCLEAR line I had commented out in last mBOX update was still needed (fixed in code above)!
Code: QB64: [Select]
- '2019-01-02 added _KEYCLEAR to clear keys hit waiting for enter press at INPUT
- '2019-03-02 discovered this does not work with mBox, can it be tested and fixed?
- ' Nope, impossible.
- 'can I get mBox to use getClick? No because I want to allow mouse to move mBox by grabbing title bar
- 'OK added stuff to clear old mb and they are now working together
- '2019-08-06 More tests with mBox and now inputBox$()
- ' OK test if getClick plays nice with last update of mBox (2019-07-31) and vice versa
- ' and also inputBox. Discovered 2019-08-06 mBox did need a _KEYCLEAR! inputBox already had it.
- m$ = "To exit this mBox click X box, press enter, spacebar or escape, to exit this tester press escape (again?) after mBox is off screen."
- m$ = m$ + CHR$(10) + "Once screen is clicked or enter is pressed you should see an inputBox$ come up."
- WHILE 1
- 'CLS
- mBox "Test mBox with getClick", m$
- PRINT "mBox (Message Box) is a sub that returns nothing, it only provides info. "
- PRINT "If you pressed esacpe from mBox, press again if want to quit."
- 'test inputBox
- r$ = inputBox$("Enter a string for inputBox to return to main program.", "Testing getClick with inputBox function.", 76)
- PRINT " To test getClick (now), click (and drag if want) screen or make a single keypress."
- PRINT "What you did should be detected by getClick and reported back to you here on main screen."
- 'x = -1: y = -1: k = 0 'need this?
- getClick x, y, k
- PRINT "All additional mouse clicks or keypresses will be ignored until:"
- INPUT "PRESS ENTER TO CONTINUE with another mBox or inputBox$() test... "; wate$
- _LIMIT 30
- 'getClick returns the mouse x, y position WHEN THE MOUSE WAS RELEASED! or keypress ASC 27 or 32 to 125
- '2019-08-06 Test now with new mBox and inputBox procedures
- 'found mBox needed a _KEYCLEAR, how about inputBox? OK had _KEYCLEAR already
- WHILE mb
- _KEYCLEAR 'clear previous key presses
- mx = -1: my = -1: q = 0
- q = _KEYHIT
- 'IF mb THEN
- q = _KEYHIT
- _LIMIT 1000
- _LIMIT 1000
- 'title$ limit is 57 chars, all lines are 58 chars max, version 2019-08-06
- 'THIS SUB NOW NEEDS SUB scnState(restoreTF) for saving and restoring screen settings
- bg = &HBB000033
- fg = &HFF33AAFF
- 'first screen dimensions and items to restore at exit
- 'screen and current settings to restore at end ofsub
- scnState 0
- _KEYCLEAR '<<<<<<<<<<<<<<<<<<<< do i still need this? YES! 2019-08-06 update!
- 'screen snapshot
- curScrn = _DEST
- 'setup t() to store strings with ti as index, linit 58 chars per line max, b is for build
- 'are there any new line signals, CR, LF or both? take CRLF or LFCR as one break but dbl LF or CR means blank line
- tail = "": ff = 0
- ff = 1 'found space flag
- tail = d + tail 'the tail grows!
- b = b + c 'just keep building the line
- t(ti) = b
- bxH = ti + 3: bxW = limit + 2
- 'draw message box
- _DEST mbx
- COLOR fg, bg
- 'now for the action
- _DEST curScrn
- 'convert to pixels the top left corner of box at moment
- bxW = bxW * 8: bxH = bxH * 16
- tlx = (sw - bxW) / 2: tly = (sh - bxH) / 2
- lastx = tlx: lasty = tly
- 'now allow user to move it around or just read it
- WHILE 1
- _PUTIMAGE , backScrn
- grabx = mx - tlx: graby = my - tly
- 'attempt to speed up with less updates
- tlx = mx - grabx: tly = my - graby
- _PUTIMAGE , backScrn
- lastx = tlx: lasty = tly
- _LIMIT 400
- kh = _KEYHIT
- _LIMIT 400
- 'put things back
- _PUTIMAGE , backScrn
- _FREEIMAGE backScrn
- _FREEIMAGE mbx
- scnState 1 'Thanks Steve McNeill
- ' for saving and restoring screen settins
- _FONT Font
- COLOR DefaultColor, BackGroundColor
- _DEST Dest
- _SOURCE Source
- LOCATE row, col
- _LIMIT 100
- ' You can grab this box by title and drag it around screen for full viewing while answering prompt.
- ' Only one line allowed for prompt$
- ' boxWidth is 4 more than the allowed length of input, it needs to be longer than title$ and prompt$ also
- ' Utilities > Input Box > Input Box 1 tester v 2019-07-31
- 'colors
- ForeColor = &HFF000055 '< change as desired prompt text color, back color or type in area
- BackColor = &HFF6080CC '< change as desired used fore color in type in area
- White = &HFFFFFFFF
- 'items to restore at exit
- scnState 0
- 'screen snapshot
- 'moving box around on screen
- 'draw message box
- bxW = boxWidth * 8: bxH = 7 * 16
- _DEST ibx
- COLOR ForeColor, BackColor
- GOSUB finishBox
- 'convert to pixels the top left corner of box at moment
- bxW = boxWidth * 8: bxH = 5 * 16
- tlx = (sw - bxW) / 2: tly = (sh - bxH) / 2
- lastx = tlx: lasty = tly
- 'now allow user to move it around or just read it
- WHILE 1
- _PUTIMAGE , backScrn
- grabx = mx - tlx: graby = my - tly
- 'attempt to speed up with less updates
- tlx = mx - grabx: tly = my - graby
- _PUTIMAGE , backScrn
- lastx = tlx: lasty = tly
- _LIMIT 400
- kh& = _KEYHIT
- _LIMIT 60
- 'put things back
- scnState 1 'need fg and bg colors set to cls
- CLS '? is this needed YES!!
- _PUTIMAGE , backScrn
- _FREEIMAGE backScrn
- _FREEIMAGE ibx
- scnState 1 'because we have to call _display, we have to call this again
- inputBox$ = inp$
- finishBox:
- _DEST ibx
- COLOR BackColor, ForeColor
- _DEST curScrn
Post by: johnno56 on August 06, 2019, 05:57:00 pm
Excellent menu. Very cool.
J
Post by: bplus on August 06, 2019, 07:18:23 pm
Menu? but thanks :D
I just got a new one today (palindrome):
Never odd or even.
Post by: SMcNeill on August 08, 2019, 09:51:23 pm
Code: QB64: [Select]
Post by: bplus on October 23, 2019, 08:02:28 pm
Code: QB64: [Select]
- _TITLE "Alternate Calc of nCr, the number of Combinations of n things taken r at a time."
- ' Though this method is still quite limited at least it does not depend upon the full calculation
- ' of a factorial to return a result.
- ' You can do n up to at least 50 with r's at 1/2 n, and smaller r's for higher n's.
- ' Be very careful accepting returns as correct.
- PRINT "The number of hands of 13 in a deck is ";
- PRINT " compare to 635,013,559,600"
- 'Note: I am using notes from a successful calc to generalize this method.
- ' How many hands of 13 from a deck?
- ' Formula for Combination of N items taken R at a time = N!/(R! * (N-R)!) so we need
- ' 52! / (39! * 13!) = 52 * 51 * 50 * 49 * ... * 40 / 13 * 12 * 11 * ... * 1
- a = n - r
- a = n - r
- ' DIM a52_39(1 TO 13) AS INTEGER, a13(1 TO 13) AS INTEGER
- numer(i) = a + i ' = 40, 41, 42, 43, ... 52 numerator multipliers
- denom(i) = i ' = 1, 2, 3, 4, ... 13 denominator multipliers
- ' To keep the numerator from getting too big reduce by demoinator terms that divide evenly
- found = 0
- ' multiply whats left in numerator and denomiator
- numerator = 1: denomenator = 1
- numerator = numerator * numer(i) 'multiple numerators left
- denomenator = denomenator * denom(i) 'multiply denominators left
- nCr~&& = numerator \ denomenator
Here is a demo: https://www.qb64.org/forum/index.php?topic=1792.msg110362#msg110362
Update: 2019-10-28 You are safe using this function to get you past 20! with straight calculation nCR to n=52 after 52 you might want to check calculations against a ball park estimate. If nCr gets the amount of digits right then it is likely precise down to last digit. If the number of digits are off then obviously the precision doesn't matter, it wont be of use.
UPDATE: String Math$ has solved problem of extended factorials check this thread out starting about here:
https://www.qb64.org/forum/index.php?topic=2921.msg121797#msg121797
Post by: STxAxTIC on October 26, 2019, 05:25:40 am
Post by: bplus on October 27, 2019, 03:00:40 pm
Code: QB64: [Select]
Update: FY Shuffle now 3 liner thanks to Steve's suggestion, removed the variable assignment.
Post by: bplus on October 27, 2019, 03:05:55 pm
https://www.qb64.org/forum/index.php?topic=1785.0
With less keystrokes than STR$(number), you can string it and trim it!
Code: QB64: [Select]
Post by: bplus on October 27, 2019, 03:15:04 pm
Just as the _TITLE says: Load and Sort an array at the same time, handy to automatically sort an array while you are loading it. Not intended for giant arrays that need number crunching routines to save time.
Code: QB64: [Select]
Edited with Steve's suggestion, thanks Steve!
x2 Edit thanks again Steve!
x3 Edit found another huge line savings, cut 4 lines, demo using Type Definition for array: https://www.qb64.org/forum/index.php?topic=1833.msg110748#msg110748
2020-06-07 Edit #4 now? While working on Gin Rummy, I needed to load card arrays according to highest points first. This new version is a sub routine, does not need oversized array already DIM and SHARED.
It is better than sAppend! if you need a sorted array while loading it.
Post by: SMcNeill on October 27, 2019, 03:35:19 pm
Instead of IF stored = 0 THEN, change that statement to IF j = i THEN..
When you store a value, you exit J early, so it’s always less than I, but if it searches the whole loop, it terminates at (I - 1) + 1, which is I.
It saves setting and resetting the variable each pass of I. ;)
Post by: bplus on October 27, 2019, 04:05:22 pm
Post by: SMcNeill on October 27, 2019, 05:01:00 pm
In the loop, you set n(j) then exit the loop.
Outside the loop, if I = J then you set n(I)... but since I = J, you could set n(J) instead...
And, if you set n(j) inside the loop, as well as outside the loop, you can simplify down to just *always* setting it once at the end of the loop. No IF needed, and no need to set it inside the loop either. ;)
Post by: bplus on October 27, 2019, 07:02:22 pm
Code edited again.
Post by: bplus on November 01, 2019, 01:03:29 pm
https://www.qb64.org/forum/index.php?topic=1822.0
inputG SUB
A quick way to get an INPUT variable on a graphics screen.
Code: QB64: [Select]
- '2019-11-01 TempodiBasic makes a fine point, 2 little changes
- y = 200: x = 100
- P$ = "Enter something like *testing 1, 2, 3... * about 20 chars max > "
- expectedEnterLen% = 20
- inputG x, y, P$, inpt$, expectedEnterLen%
- PRINT "You entered: "; inpt$
- y = y + 25
- x = x + 30
- PRINT "Test is done when empty string returned by inputG."
- 'INPUT for Graphics screen
- SUB inputG (x, y, prmpt$, var$, expectedLenVar%) 'input for a graphics screen x, y is where the prompt will start , returns through var$
- saveAD = _AUTODISPLAY
- k$ = INKEY$
- _PRINTSTRING (x, y), prmpt$ + " {" + tmp$ + "}" + SPACE$(expectedLenVar% - LEN(tmp$)) 'spaces needed at end to clear backspace chars
I expect this will be edited as refinements are brought up.
Steve recommended Terry Ritchie's library but the learning curve for that! Plus he's not here any more to answer questions... this kind of formality is for computer scientists IMHO.
Anyway, another good one or at least a good start for a handy tool.
EDIT #1: TempodiBasic makes a fine point and now 2 little changes have been made.
EDIT #2: Sorry Terry, I can't remember to spell your name correctly.
EDIT #3: 2019-12-05 Discovered a much needed _DISPLAY line when _DISPLAY has been activated.
Post by: TempodiBasic on November 01, 2019, 05:14:29 pm
The bag of tool has another function!
PS: one little feedback INKEY$ brings also the keys with two bytes into the input taken, for example arrow keys are added to the string returned by the SUB inputG.
Post by: bplus on November 01, 2019, 11:40:32 pm
Fine !
The bag of tool has another function!
PS: one little feedback INKEY$ brings also the keys with two bytes into the input taken, for example arrow keys are added to the string returned by the SUB inputG.
You make fine point, I make 2 changes 1=2 ;-))
Post by: TempodiBasic on November 02, 2019, 01:40:19 pm
your improvement is clear and makes the SUB inputG more powerful and useful!
Post by: bplus on November 02, 2019, 02:12:55 pm
Post by: bplus on November 03, 2019, 09:38:25 pm
https://www.qb64.org/forum/index.php?topic=1833.msg110748#msg110748
so this Load and Sort tool is on it's 3rd improvement!
https://www.qb64.org/forum/index.php?topic=1511.msg110459#msg110459
hmm... wonder how Steve missed that? ;-) busy on the farm I bet!
Post by: bplus on November 20, 2019, 12:55:41 am
Here is demo using fquad (which uses ftri twice) to make a cube:
Code: QB64: [Select]
- _TITLE "Cube It"
- PRINT " bplus was here "
- _LIMIT 30
- sd2 = side / 2
- fquad x, y + side, x + sd2, y + sd2, x + side, y + sd2, x + sd2, y + side, _RGB32(.75 * r, .3 * g, .3 * b)
- ' EDIT 2019-11-20 Improvement by Steve, add a little more speed
- STATIC a&
- D = _DEST
- _DEST a&
- _DEST D
- 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is opposite of x4, y4
- ftri x1, y1, x2, y2, x4, y4, K
- ftri x3, y3, x2, y2, x4, y4, K
EDIT: Update 2019-11-20 Steve strikes again, with Static no longer need to _FREEIMAGE, saves some time plus we preserve old DEST and restore after drawing ftri.
Post by: SMcNeill on November 21, 2019, 12:04:56 pm
Code: [Select]
FUNCTION VerifyNumber (text$)
t$ = LTRIM$(RTRIM$(text$))
v = VAL(t$)
t1$ = LTRIM$(STR$(v))
IF t$ = t1$ THEN VerifyNumber = -1
END FUNCTIONWorks in most cases, unless you overload it and it changes formats on you, such as from 100000000000000000000000000000000 to 1.0E+20 (or whatever that number of 1s and 0s actually is).
We can push it to the point where this little function fails, but in most ordinary cases, it works like a charm. :)
Post by: SMcNeill on November 29, 2019, 01:31:28 pm
Code: QB64: [Select]
I suggest using it with ExtendedTimer instead, so you don't have any pesky little "it acts goofy at midnight" glitches, but this works just like SLEEP for us, except it also supports a mouse click as a valid button press to break it.
Post by: TempodiBasic on November 30, 2019, 06:08:09 am
thanks to share.
Post by: bplus on November 30, 2019, 05:15:13 pm
Code: QB64: [Select]
Post by: bplus on December 01, 2019, 11:00:12 am
The &B is my main contribution for a base ID, compare with &H and &O that QB64 uses.
Code: QB64: [Select]
- j = j + 1
- BIN$ = "&B" + B$
The Librarian may pickup on this and update code in official Toolbox?
Oh we've gone full circle, I will update OP!
Post by: RhoSigma on December 02, 2019, 08:13:46 am
Code: QB64: [Select]
- DIM v&&, vi&&
- BIN$ = "": v&& = value&&
- v&& = vi&&
BTW - It doesn't add the &B prefix, just as HEX$ and OCT$ doesn't add &H and &O respectivly.
Post by: bplus on December 02, 2019, 10:34:01 am
Quote
BTW - It doesn't add the &B prefix, just as HEX$ and OCT$ doesn't add &H and &O respectivly.
Seems a shame too. Look at 10000 that has 4 different possible values.
Post by: RhoSigma on December 02, 2019, 10:55:55 am
Seems a shame too. Look at 10000 that has 4 different possible values.
For sure, I'd like it too, if each function would add its respective prefix, but it would break compatiblity with legacy code. But on the other side HEX$, OCT$ and now BIN$ belong to the same type of function and should behave the same way, that's why I didn't add the &B prefix.
From a different point of view, &B is a new addition added in or after v1.0, that's basically the reason why QB64 misses the built-in BIN$ function. So if BIN$ is QB64 specific, shouldn't it be _BIN$ intead? And what do we do with the binary prefix then, _&B ??
Post by: bplus on December 02, 2019, 11:03:49 am
For sure, I'd like it too, if each function would add its respective prefix, but it would break compatiblity with legacy code. But on the other side HEX$, OCT$ and now BIN$ belong to the same type of function and should behave the same way, that's why I didn't add the &B prefix.
From a different point of view, &B is a new addition added in or after v1.0, that's basically the reason why QB64 misses the built-in BIN$ function. So if BIN$ is QB64 specific, shouldn't it be _BIN$ intead? And what do we do with the binary prefix then, _&B ??
Of course _&B is silly but hmm... _HEX$, _OCT$, _BIN$ that use prefixes all! not terrible ;)
Post by: bplus on December 02, 2019, 01:30:12 pm
Code: QB64: [Select]
- j = j + 1
The function just needs 1 variable, so I use something of Rho's
Post by: RhoSigma on December 02, 2019, 03:47:23 pm
Code: QB64: [Select]
- _TITLE "BIN$ speed test..."
- PRINT "TB = current version from Toolbox board"
- PRINT "BP = latest version from B+"
- PRINT "RS = version from RhoSigma"
- '--- for a fair test we need the same numbers for all
- '--- functions, so we first fill an array with numbers
- NEXT i&
- '--- Toolbox ---
- PRINT "TB-Start:"; st#
- b$ = BIN_TB$(num&(i&))
- NEXT i&
- PRINT "TB-End..:"; et#
- '--- bplus ---
- PRINT "BP-Start:"; st#
- b$ = BIN_BP$(num&(i&))
- NEXT i&
- PRINT "BP-End..:"; et#
- '--- RhoSigma ---
- PRINT "RS-Start:"; st#
- b$ = BIN_RS$(num&(i&))
- NEXT i&
- PRINT "RS-End..:"; et#
- '--- cleanup & wait ---
- PRINT "...done, press any key"
- ERASE num&
- '================================
- '=== AND HERE COMES THE MAGIC ===
- '================================
- i = integerBase10 'copy
- pow = 0
- b$ = "1" + b$
- i = i - 2 ^ pow
- b$ = "0" + b$
- pow = pow + 1
- BIN_TB$ = "&B" + b$
- j = j + 1
- DIM v&&, vi&&
- BIN_RS$ = "": v&& = value&&
- v&& = vi&&
Post by: RhoSigma on December 02, 2019, 04:39:25 pm
it's even twice as fast as my first one (which is in the speed test) by simply avoiding the temporary string operations done under the QB64 hood when adding the "0" or "1" into an existing string. It cuts the times to approx. 3.05 sec. with the x86 build and 2.54 sec. with x64.
Code: QB64: [Select]
- 'chp% = char position, msp% = most significant position
- 'tlv&& = temporary loop value, ivq&& = integer value quotient
- tlv&& = value&&
- chp% = chp% - 1: tlv&& = ivq&&
Post by: bplus on December 02, 2019, 07:25:43 pm
Here is my new version (and NOT final version) against RhoSigma's, had to add another 0 to the test and dump the time consuming array:
Code: QB64: [Select]
- PRINT "BP = latest version from B+"
- PRINT "RS = latest from RhoSigma"
- '--- for a fair test we need the same numbers for all
- '--- functions, so we first fill an array with numbers
- PRINT "First test print BIN$ of 0:"
- PRINT "Press key to continue... "
- PRINT "For random number r = "; r
- PRINT "Press key to continue... "
- '--- bplus ---
- PRINT "BP-Start:"; st#
- b$ = bpBIN$(i&&)
- PRINT "BP-End..:"; et#
- '--- RhoSigma ---
- PRINT "RS-Start:"; st#
- b$ = rsBIN$(i&&)
- PRINT "RS-End..:"; et#
- '--- cleanup & wait ---
- PRINT "...done, press any key"
- '================================
- '=== AND HERE COMES THE MAGIC ===
- '================================
- 'chp% = char position, msp% = most significant position
- 'tlv&& = temporary loop value, ivq&& = integer value quotient
- tlv&& = value&&
- chp% = chp% - 1: tlv&& = ivq&&
- WHILE j <= integerBase10
- j = j * 2: place = place - 1
Post by: RhoSigma on December 03, 2019, 04:56:24 am
used bitshift instead of division, and unrolled the loop for the smallest integer type (_BYTE). Have also tweaked yours a bit B+, j=j+j (instead j*2) and removed the "0" (ELSE) branch from your condition. Your string consists of zeros, no need to write them for each tested bit.
Make sure your QB64 version is recent enough to have the _SHR instruction...
Code: QB64: [Select]
- PRINT "BP = latest version from B+"
- PRINT "RS = latest from RhoSigma"
- '--- for a fair test we need the same numbers for all
- '--- functions, so we first fill an array with numbers
- PRINT "First test print BIN$ of 0:"
- PRINT "Press key to continue... "
- PRINT "For random number r = "; r
- PRINT "Press key to continue... "
- '--- bplus ---
- PRINT "BP-Start:"; st#
- b$ = bpBIN$(i&&)
- PRINT "BP-End..:"; et#
- '--- RhoSigma ---
- PRINT "RS-Start:"; st#
- b$ = rsBIN$(i&&)
- PRINT "RS-End..:"; et#
- '--- cleanup & wait ---
- PRINT "...done, press any key"
- '================================
- '=== AND HERE COMES THE MAGIC ===
- '================================
- 'tlv&& = temporary loop value
- 'chp% = char position, msp% = most significant position
- tlv&& = value&&
- chp% = chp% - 8
- WHILE j <= integerBase10
- j = j + j: place = place - 1
Post by: RhoSigma on December 03, 2019, 08:20:56 am
improved using _MEM and CHECKING:OFF
Once again, make sure your QB64 version is recent enough to have the _SHR instruction...
Code: QB64: [Select]
- PRINT "BP = latest version from B+"
- PRINT "RS = latest from RhoSigma"
- '--- for a fair test we need the same numbers for all
- '--- functions, so we first fill an array with numbers
- PRINT "First test print BIN$ of 0:"
- PRINT "Press key to continue... "
- PRINT "For random number r = "; r
- PRINT "Press key to continue... "
- '--- bplus ---
- PRINT "BP-Start:"; st#
- b$ = bpBIN$(i&&)
- PRINT "BP-End..:"; et#
- '--- RhoSigma ---
- PRINT "RS-Start:"; st#
- b$ = rsBIN$(i&&)
- PRINT "RS-End..:"; et#
- '--- cleanup & wait ---
- PRINT "...done, press any key"
- '================================
- '=== AND HERE COMES THE MAGIC ===
- '================================
- 'tlv&& = temporary loop value, b$64 = fixed length temporary string
- 'chp% = char position mem offset, msp% = most significant string position
- 'one% = ascii code of "1", mp = memory pointer to b$64
- tlv&& = value&&
- chp% = chp% - 8
- _MEMFREE mp
- WHILE j <= integerBase10
- j = j + j: place = place - 1
Post by: SMcNeill on December 03, 2019, 09:20:39 am
Code: QB64: [Select]
- n$ = bin$(12, 1)
- n$ = bin$(-2, 1) 'byte
- n$ = bin$(-2, 2) 'integer
- NEXT j, i1
Unlike all the rest, this is isn't built with speed being it's deciding factor -- flexibility is. It returns BIN$ for both positive and negative values, and for various variable types. I don't usually find myself needing to be concerned with "how fast can I turn a number into a binary string", so this is designed more for "how useful can it be, when turning a number into a binary string".
n$ = bin$(-2, 1) <--- This would return the binary value of -2, if I was dealing with bytes.
n$ = bin$(-2, 4) <--- This would return the binary value of -2, if I was dealing with longs.
Not only does it work for positive numbers, but it also works with negative ones, and returns them back to us for whatever variable type which we might want it to.
Post by: bplus on December 03, 2019, 10:57:33 am
And agree it's getting kind of crazy to be completely focused on speed. (Specially since I don't think I am going to get a faster one than RhoSigma. LOL)
@Steve, you really have an actual use for binary strings for different variable types or are you going to make one up now? ;) Even for MEM stuff I would think you need number values not strings?
Post by: SMcNeill on December 03, 2019, 11:07:36 am
Yeah I suspected this was going to get into bit shifting and MEM but did not expect for Type variables, ha ;-))
And agree it's getting kind of crazy to be completely focused on speed.
@Steve, you really have an actual use for binary strings for different variable types or are you going to make one up now? Even for MEM stuff I would think you need number values not strings?
Mainly for teaching purposes, to help explain to people why COLOR -1 in 32-bit is the same as color &HFFFFFFFF. (A shortcut I use all the time!)
As you say, normally you use AND bit_value, rather than AND VAL(MID$(BIN$(number), position,1)). ;)
Post by: bplus on December 03, 2019, 12:21:04 pm
Update: oh heck I missed the ELSE replace with "0" thing, nice catch.
RhoSigma, really, really nice work! you make my version better and then cut that time in half or so... :)
Post by: RhoSigma on December 04, 2019, 03:50:20 am
I saw it already in your edit. And yes, in general I do also prefer readability end elegance over speed (GuiTools is the best prove), but nevertheless it was a nice brain training to see what's possible and what you can do to take out as many as possible of the time consuming "under the hood" operations, which regulary nobody even think of.
Post by: bplus on December 05, 2019, 11:06:49 pm
https://www.qb64.org/forum/index.php?topic=1511.msg110651#msg110651
Post by: bplus on December 16, 2019, 10:39:30 pm
8 routines added or improved to my toolbox today 2019-12-16, what a day!
Code: QB64: [Select]
- ' 2019-12-16 updates to my Toolbox Listing
- '2019-12-16 fix by Steve saves some time with STATIC and saves and restores last dest
- STATIC a&
- D = _DEST
- _DEST a&
- _DONTBLEND a& ' '<<<< new 2019-12-16 fix
- _BLEND a& '<<<< new 2019-12-16 fix
- _DEST D
- 'update 2019-12-16 needs updated fTri 2019-12-16 I like this ordering of points better
- 'need 4 non linear points (not all on 1 line) list them clockwise so x2, y2 is opposite of x4, y4
- ftri x1, y1, x2, y2, x3, y3, K
- ftri x3, y3, x4, y4, x1, y1, K
- ' 2019-12-16 this should have been in here earlier
- ' CX = center x coordinate
- ' CY = center y coordinate
- ' a = semimajor axis
- ' b = semiminor axis
- ' C = fill color
- w2 = a * a
- h2 = b * b
- h2w2 = h2 * w2
- y = y + 1
- 'thanks STxAxTIC from Toolbox
- ' CX = center x coordinate
- ' CY = center y coordinate
- ' a = semimajor axis major radius
- ' b = semiminor axis minor radius
- ' ang = clockwise orientation of semimajor axis in radians (0 default)
- ' C = fill color
- i = i + CX
- j = -j + CY
- 'relace toolbox code 2019-12-16
- 'this needs RotoZoom3 to rotate image and EllipseFill to make the image BUT it can now scale it also!
- 'setup isolated area, draw fFlatEllipse and then RotoZoom the image into destination
- 'ox, oy is center of ellipse
- 'majorRadius is 1/2 the lonest axis
- 'minorRadius is 1/2 the short axis
- 'radianAngle is the Radian Angle of Tilt
- 'c is of course color
- DIM sd&, temp&
- sd& = _DEST
- _DEST temp&
- _DONTBLEND temp& '<< test 12-16
- 'fEllipse majorRadius, minorRadius, majorRadius, minorRadius, c
- EllipseFill majorRadius, minorRadius, majorRadius, minorRadius, c
- _BLEND temp& '<< test 12-16
- _DEST destH
- RotoZoom3 ox, oy, temp&, 1, 1, radianAngle
- _FREEIMAGE temp&
- _DEST sd&
- ' this assumes you have set your drawing location with _dest or default to screen
- ' X, Y is where you want to put the middle of the image
- ' Image is the handle assigned with _LOADIMAGE
- ' xScale, yScale are shrinkage < 1 or magnification > 1 on the given axis
- ' radianRotation is the Angle in Radian units to rotate the image
- px(0) = -W& / 2: py(0) = -H& / 2 'left top corner
- px(1) = -W& / 2: py(1) = H& / 2 ' left bottom corner
- px(2) = W& / 2: py(2) = H& / 2 ' right bottom
- px(3) = W& / 2: py(3) = -H& / 2 ' right top
- x2& = xScale * (px(i&) * cosr! + sinr! * py(i&)) + X: y2& = yScale * (py(i&) * cosr! - px(i&) * sinr!) + Y
- px(i&) = x2&: py(i&) = y2&
- _MAPTRIANGLE _SEAMLESS(0, 0)-(0, H& - 1)-(W& - 1, H& - 1), Image TO(px(0), py(0))-(px(1), py(1))-(px(2), py(2))
- _MAPTRIANGLE _SEAMLESS(0, 0)-(W& - 1, 0)-(W& - 1, H& - 1), Image TO(px(0), py(0))-(px(3), py(3))-(px(2), py(2))
- '=================================================================================================================== String stuff
- '---------------------------------------------------------------------
- 'RhoSigma keeps saying final version but then...
- 'here is reference: https://www.qb64.org/forum/index.php?topic=1933.msg112096#msg112096
- 'Function: Convert any given dec/hex/oct number into a binary string.
- ' Can handle positive and negative values and works in that
- ' similar to the QB64 built-in HEX$ and OCT$ functions.
- '
- 'Synopsis: binary$ = BIN$ (value&&)
- '
- 'Result: binary$ --> the binary representation string of the given
- ' number without leading zeros for positive values
- ' and either 8/16/32 or 64 chars for negatives,
- ' depending on the input size
- '
- 'Inputs: value&& --> the pos./neg. number to convert, may also be
- ' given as &H or &O prefixed value
- '
- 'Notes: You may also pass in floating point values, as long as its
- ' represented value fits into the _INTEGER64 (&&) input, hence
- ' approx. -9.223372036854776E+18 to 9.223372036854776E+18.
- ' Different from HEX$ and OCT$, BIN$ won't throw an overflow
- ' error, if this range is exceeded, but the result is probably
- ' wrong in such a case.
- '---------------------------------------------------------------------
- '--- option _explicit requirements ---
- '--- init ---
- temp~&& = value&&
- '--- convert ---
- charPos% = charPos% - 1: temp~&& = temp~&& \ 2
- '--- adjust negative size ---
- '--- set result ---
- 'update 2019-12-16 in ...test\graphics\fTri tests.bas SLEEP with a click
- oldMouse = -1 '2019-12-16 2nd fix today assume an old mouse click is still active
- startTime = TIMER
- wayt = 1
- WHILE wayt
- _LIMIT 30
EDIT: 2019-12-17 RhoSigma changed final version of BIN$ again
EDIT: 2020-03-03 Discovered big error in revised RotoZoom3 now fixed
Post by: FellippeHeitor on December 16, 2019, 10:41:16 pm
Quote
8 routines added or improved to my toolbox today 2019-12-16, what a day!
It is wholesome to see this community so active and going so strong. Moment of appreciation here.
Post by: SMcNeill on December 16, 2019, 10:45:55 pm
The more tools in a toolset, the more powerful and versatile that toolset becomes. (As long as you can find the proper tool you need for the job at hand.)
Post by: bplus on December 16, 2019, 10:57:36 pm
What's happening with your other forum?
Post by: SMcNeill on December 16, 2019, 11:10:35 pm
Thanks Steve, your expertise is invaluable! Well I guess I have to sign up to see your Christmas thing ;-))
What's happening with your other forum?
It’s still up and going, but it has nasty upload limits and such which I don’t care for (as well as pop ups and advertisements). I’m too cheap to pay a monthly fee to remove those adds and increase upload limits, so I figured a personal forum hosted on my own server will eliminate all those annoyances for me. ;)
Post by: SMcNeill on December 17, 2019, 05:05:12 pm
Code: [Select]
DIM Array(10) AS STRING
DATA Apple,Banana,Cherry,Date,Fig,Grape,Huckleberry,Iced Fruit,Jambolan,Kiwi,Lemon
FOR i = 0 TO 10
READ Array(i)
NEXT
choice = 0
DO
CLS
DisplayList 10, 10, 20, 5, choice, Array(), -1
k = _KEYHIT
SELECT CASE k
CASE 18432
choice = choice - 1
IF choice < 0 THEN choice = 0
CASE 20480
choice = choice + 1
IF choice > 10 THEN choice = 10
END SELECT
_DISPLAY
_LIMIT 30
LOOP
SUB DisplayList (x AS INTEGER, y AS INTEGER, w AS INTEGER, l AS INTEGER, s AS INTEGER, choices() AS STRING, numbered AS _BYTE)
'x/y location to place the start of our list
'w is the width of our list on the screen
'l is the length of the list items we want to display at a time
's is the starting element that we want to display on the screen
'choices() is the array that holds the actual list for us
'numbered is the toggle for if we want to autonumber our list or not.
' 0 says we don't want to number the list; just display it.
' A value less than 0 says we want to display the number index of the visible list
' A value greater than 0 says we want to display the number of visible elements from the list on the screen.
'Some basic error checking is in need here
IF s < LBOUND(choices) THEN s = LBOUND(choices)
IF s + l - 1 > UBOUND(choices) THEN l = UBOUND(choices) - s + 1
LOCATE x
start = s: finish = s + l - 1
FOR i = start TO finish
counter = counter + 1
IF numbered > 0 THEN counter$ = LTRIM$(STR$(counter)) + ") "
IF numbered < 0 THEN counter$ = LTRIM$(STR$(counter + start - 1)) + ") "
LOCATE , y: PRINT counter$ + LEFT$(choices(i), w - LEN(counter$))
NEXT
END SUB
This is about as simple as it gets, with the actual code here in the sub being smaller than the comments to explain the sub... Works in all screen modes, with use of simple LOCATE coordinates for placement. ;)
Post by: Qbee on December 17, 2019, 06:42:12 pm
nice tool and works fine!
What I found is that you use x for rows (vertical position, top -> down) and y for columns (horizontal position, left -> right).
Post by: bplus on December 17, 2019, 07:16:20 pm
Quote
Another tool which all toolboxes should have, in some form or another -- an easy to use routine to display a large list on the screen.
Yeah mine looks like this which was pretty much copied from Wiki for mouse wheel demo:
Code: QB64: [Select]
- show a() 'from toolbox
- 'this uses 20 lines on screen to display an array
- prevrow = row 'store previous row value
Post by: bplus on January 15, 2020, 12:11:54 pm
Developed in Deal or No Deal, https://www.qb64.org/forum/index.php?topic=2092.0
A comma money format or comma fixed decimal places for type Double#:
Code: QB64: [Select]
Post by: bplus on January 25, 2020, 02:51:11 pm
Code: QB64: [Select]
- '======================= Feature SUB =======================================================================
- ' This code takes a dynamic points array and adds and modifies points to smooth out the data,
- ' to be used as Toolbox SUB. b+ 2020-01-24 adapted and modified from:
- ' Curve smoother by STxAxTIC https://www.qb64.org/forum/index.php?topic=184.msg963#msg963
- 'TYPE XY
- ' x AS SINGLE
- ' y AS SINGLE
- 'END TYPE
- ' targetPoints is the number of points to be in finished smoothed out array
- ' smoothIterations is number of times to try and round out corners
- '
- ' Determine the pair of neighboring points that have the greatest separation of all pairs.
- '
- rad2Max = -1
- kmax = -1
- xfac = arr(k).x - arr(k + 1).x
- yfac = arr(k).y - arr(k + 1).y
- rad2 = xfac ^ 2 + yfac ^ 2
- kmax = k
- rad2Max = rad2
- '
- ' Starting next to kmax, create a `gap' by shifting all other points by one index.
- '
- arr(j + 1).x = arr(j).x
- arr(j + 1).y = arr(j).y
- '
- ' Fill the gap with a new point whose position is determined by the average of its neighbors.
- '
- arr(kmax + 1).x = .5 * (arr(kmax).x + arr(kmax + 2).x)
- arr(kmax + 1).y = .5 * (arr(kmax).y + arr(kmax + 2).y)
- numPoints = numPoints + 1
- '
- ' At this stage, the curve still has all of its sharp edges. Use a `relaxation method' to smooth.
- ' The new position of a point is equal to the average position of its neighboring points.
- '
- temp(k).x = .5 * (arr(k - 1).x + arr(k + 1).x)
- temp(k).y = .5 * (arr(k - 1).y + arr(k + 1).y)
- arr(k).x = temp(k).x
- arr(k).y = temp(k).y
A really nice update to yCP:
Code: QB64: [Select]
- 'update 2020-01-24 now with _printwidth so can use any FONT
Post by: bplus on February 15, 2020, 11:42:00 am
Code: QB64: [Select]
- '===================================================================================
- ' Lets blink between colors white and blue, expanding and shrinking text for 10 secs
- '===================================================================================
- s$ = "Blink colors white and blue, expanding and shrinking centered text for 10 secs"
- th = 16 'Text Height - start normal
- dh = 1 'change height
- flashTimes = 100 'with limit 10 this will take 10 times a second and be done in 100/10 secs
- start$ = TIME$
- PRINT start$; ", ";
- toggle = 1 - toggle
- th = th + dh
- flashTimes = flashTimes - 1
- lastFlash$ = TIME$
- PRINT lastFlash$; " <<<< notice these numbers are not flashing even though we CLS every frame"
- _DISPLAY '>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> eliminates blinking screens when use CLS
- _LIMIT 10 '>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> allows maximum number of loops of 10 per sec
- 'center the text at x, y with given height and color
- fg = _DEFAULTCOLOR
- 'screen snapshot
- cur& = _DEST
- _DEST I&
- mult = textHeight / 16
- COLOR fg
- _FREEIMAGE I&
Post by: bplus on March 03, 2020, 02:46:43 pm
I found my own latest version of Rotozoom posted in this thread needed a little fix (8 updates in one day https://www.qb64.org/forum/index.php?topic=1511.msg112211#msg112211) and I want this demo posted to be sure I don't have such an obvious mistake go into Toolbox. So last chance to break this guys.
I have researched forum starting with STxAxTIC and Fellippe's code in above link, found nice stuff from Steve (working with text 3 subs and at least 100 lines...) and William33's (has more paramenters than needed IMHO but short and sweet too), found [banned user] and Old Moses citing my Rotozoom2, so I think I meet STxAxTIC's stringent criteria.
Code: QB64: [Select]
- ' Starting from an image I pulled from Internet, I used Paint 3D to give it a transparent background.
- ' Standard Rotation about the image center on a given X, Y location. Rotating image in middle of screen,
- ' I used something like this to find ideal angle for level point on left head on right.
- RotoZoom3 xc, yc, s&, 1, 1, a
- ao = _PI(.27) ' I have to offset the image angle by this amount so that the spike point is on the left
- ' and the head is on the right at 0 degrees or radians.
- 'Demo of the independent x and y scale for axis rotations
- maxScale = 4: dxs = .01: ddxs = 1: xs = maxScale:
- PRINT "Press any for rotation on x axis..."
- RotoZoom3 xc, yc, s&, xs, maxScale, ao
- xs = xs + dxs * ddxs
- _LIMIT 60
- ys = maxScale: dys = .01: ddys = 1
- PRINT "Press any to see layout of image over whole screen and end demo..."
- RotoZoom3 xc, yc, s&, maxScale, ys, ao
- ys = ys + dys * ddys
- _LIMIT 60
- ' Demo of an applied layout on screen
- RotoZoom3 x1, y1, s&, 2, 2, a + ao
- _DELAY 4
- 'And finally a little show. What is better than a knife thrower throwing bananas?
- drawKite xc, .9 * ymax, 600, a + ao
- _LIMIT 30
- ' Description:
- ' Started from a mod of Galleon's in Wiki that both scales and rotates an image.
- ' This version scales the x-axis and y-axis independently allowing rotations of image just by changing X or Y Scales
- ' making this tightly coded routine a very powerful and versatile image tool.
- ' This assumes you have set your drawing location with _DEST or default to screen.
- ' X, Y - is where you want to put the middle of the image
- ' Image - is the handle assigned with _LOADIMAGE
- ' xScale, yScale - are shrinkage < 1 or magnification > 1 on the given axis, 1 just uses image size.
- ' These are multipliers so .5 will create image .5 size on given axis and 2 for twice image size.
- ' radianRotation is the Angle in Radian units to rotate the image
- ' note: Radian units for rotation because it matches angle units of other Basic Trig functions
- ' and saves a little time converting from degree.
- ' Use the _D2R() function if you prefer to work in degree units for angles.
- px(0) = -W& / 2: py(0) = -H& / 2 'left top corner
- px(1) = -W& / 2: py(1) = H& / 2 ' left bottom corner
- px(2) = W& / 2: py(2) = H& / 2 ' right bottom
- px(3) = W& / 2: py(3) = -H& / 2 ' right top
- x2& = xScale * (px(i&) * cosr! + sinr! * py(i&)) + X: y2& = yScale * (py(i&) * cosr! - px(i&) * sinr!) + Y
- px(i&) = x2&: py(i&) = y2&
- _MAPTRIANGLE _SEAMLESS(0, 0)-(0, H& - 1)-(W& - 1, H& - 1), Image TO(px(0), py(0))-(px(1), py(1))-(px(2), py(2))
- _MAPTRIANGLE _SEAMLESS(0, 0)-(W& - 1, 0)-(W& - 1, H& - 1), Image TO(px(0), py(0))-(px(3), py(3))-(px(2), py(2))
EDIT: 2020-03-04 added a little show at end of demo after fixing some minor details, the zip bas file has been updated as shown above.
Here is demo in zip for the test image:
Post by: STxAxTIC on March 03, 2020, 05:25:56 pm
So by all means, feel free to add that to where ever you see fit. I'm so vocal about the filtration process so eventually I dont have to do it. There will be a prevailing style which will, if broken, stand out on it's own as irregular. Since it's still early I'm bull-dogging this but soon that can be over.
Anyway, post away. Make things minimal and explain parameters nicely like we did in the ellipse work.... actually nvm, I see you've covered that
Post by: bplus on March 03, 2020, 06:30:05 pm
I am still finding little bugs, fortunately it's in the demo. I am going to check this again with fresh eyes a couple more times, try applying in more situations wait if someone catches something. Oh, I am curious how this might work as a _PUTIMAGE substitute.
Post by: TempodiBasic on March 04, 2020, 09:14:28 am
Is it a nail that goes around?
Post by: bplus on March 04, 2020, 10:48:48 am
Great Bplus!
Is it a nail that goes around?
Just what I was thinking this morning, what a great demo that would be, like a knife thrower only with bananas.
Post by: TempodiBasic on March 04, 2020, 04:18:03 pm
about
Quote
Just what I was thinking this morning, what a great demo that would be, like a knife thrower only with bananas.I think that in a female prison it would be a great success! :-) As for the nail in your demo it changes continuosly point of view! ;-)
Post by: OldMoses on March 04, 2020, 07:44:27 pm
Post by: STxAxTIC on March 04, 2020, 07:55:25 pm
Post by: bplus on March 04, 2020, 09:32:53 pm
I just cooked up a little show in the demo to show RotoZoom3 in action loop, see Best Answer. I also wanted to show how _WIDTH(imageHandle&) and _HEIGHT(imageHandle&) can be used with the x and y Scale parameters.
Post by: bplus on March 07, 2020, 10:58:18 pm
Funny story, I was looking all through samples for it after STxAxTIC assimilated the Toolbox into the Child-boards of Samples. Where is it? Oh, you haven't posted it yet, you ninny!
So I guess it's time to post it.
https://www.qb64.org/forum/index.php?topic=2313.msg115354#msg115354
Post by: bplus on April 09, 2020, 02:49:35 pm
This looks useful and in my opinion didn't need fixing, you just have to keep track of all the new images you are making with _COPYIMAGE. Maybe I am missing something?
Anyway the latest addition to my Toolbox, swapColor Function with demo:
Code: QB64: [Select]
- _TITLE "SwapColor test"
- g = 10
- WHILE 1
- PRINT "Press any to swap color..."
- _PUTIMAGE , newT&
- _FREEIMAGE newT&
- g = g + 10
- ' create new Image Handle for an image copy with a color changed from original image, returns new Handle&
- 'https://www.qb64.org/forum/index.php?topic=2451.0
- ' from Petr to Craz1000
- a& = a& + 4
- _MEMFREE m
Image for demo:
Post by: bplus on June 08, 2020, 12:11:45 am
https://www.qb64.org/forum/index.php?topic=1511.msg110459#msg110459
Post by: bplus on August 18, 2020, 03:47:07 pm
https://www.qb64.org/forum/index.php?topic=2921.msg121886#msg121886
Post by: bplus on September 03, 2020, 07:51:55 pm
Code: QB64: [Select]
- ' 2019-08-22 orig post at https://www.qb64.org/forum/index.php?topic=1646.msg108682#msg108682
- ' direntry.h needs to be in QB64 folder
- GetLists ".", DIRs(), FILs()
- CHDIR ".."
- GetLists ".", DIRs(), FILs()
- DIM nam$
- DirCount = 0: FileCount = 0
- length = has_next_entry
- get_next_entry nam$, flags, file_size
- DirCount = DirCount + 1
- DirList(DirCount) = nam$
- FileCount = FileCount + 1
- FileList(FileCount) = nam$
- 'close_dir 'move to after end if might correct the multi calls problem
- close_dir 'this might correct the multi calls problem
Post by: FilipeEstima on September 11, 2020, 12:36:16 am
Post by: bplus on September 11, 2020, 12:42:29 am
Very interesting, I never knew this _PRESERVE was available. If I only knew it before... Every time I need to DIM an array that may have a different number of files, I have to SHELL _HIDE a DIR command, read the output file and count the number of lines, for only then make a DIM. With REDIM _PRESERVE it's so much more practical.
yes, _PRESERVE is nice option but remember to start the array with REDIM not DIM or use DYNAMIC keyword somewhere in beginning which I don't do. STATIC is default.
Post by: bplus on September 12, 2020, 12:47:39 pm
You may not need it today or tomorrow but someday you might wish you had a listing of combinations you can make with n things:
https://www.qb64.org/forum/index.php?topic=2999.msg122579#msg122579
It is easy to code any word into a letter and then decode letter back as an element of combination.
In the same vein, here is a copy of way to get listings of permutations:
https://www.qb64.org/forum/index.php?topic=2961.msg122575#msg122575
Thanks to Danilin for getting me to share these goodies with you. :)
Post by: bplus on September 12, 2020, 12:52:48 pm
Exponential Notation Remover
I don't know how many hours wasted dealing with exponential notation popping up and ruining my display of numbers:
https://www.qb64.org/forum/index.php?topic=2985.msg122404#msg122404
The final return format I settled on is here N2S$ but you might like Steve's in reply above (just don't use his "fix" there because he had it right from the start):
https://www.qb64.org/forum/index.php?topic=2985.msg122585#msg122585
Another lesson from there: be careful which Type variable you use for exponents! you might get unexpected results using default SINGLE type.
Post by: bplus on September 12, 2020, 01:01:53 pm
Turning a Loaded Image Into a Sprite When _CLEARCOLOR Is Not Enough
by removing dark background; can be done just as easy with light background.
https://www.qb64.org/forum/index.php?topic=3007.msg122645#msg122645
and better 3D effect with same image:
https://www.qb64.org/forum/index.php?topic=3009.msg122648#msg122648
Removing light background for dark object in foreground, this case a shark fin:
https://www.qb64.org/forum/index.php?topic=3307.msg125977#msg125977
Post by: SMcNeill on December 03, 2020, 10:07:40 am
Code: QB64: [Select]
Send it a code, get a name of what key it represents. Good for formatting and display purposes, if you ever need to allow the user to choose their own keys for whatever reason.
For example:
Press <ANY KEY> to Jump:
(user presses a key)
Jump key is now: 100319
Now that doesn't make any dang sense to an user! But, with the above, you get, instead:
Press <ANY KEY> to Jump:
(user presses a key)
Jump key is now: MENU
Oooooohhhhh! The MENU keys makes my little dude jump now! YAAAYYY! That makes sense! :D
Post by: bplus on December 03, 2020, 10:19:39 am
What is the Menu or Jump Key?
Is it MS Windows Logo pictured key?
Update: Nope, it's not the airplane either dang it! Lost my Internet connection :P Ha! There are keys I never mess with on my keyboard ;-))
Post by: SMcNeill on December 03, 2020, 10:27:57 am
CTRL - WIN - ALT - SPACEBAR - ALT - WIN - MENU - CTRL
https://www.howtogeek.com/425623/what-is-the-menu-key-for-and-how-to-remap-it/#:~:text=On%20full-size%20keyboards%2C%20the%20menu%20key%20is%20located,laptop%20keyboards—omit%20the%20menu%20key%20to%20save%20space. (https://www.howtogeek.com/425623/what-is-the-menu-key-for-and-how-to-remap-it/#:~:text=On%20full-size%20keyboards%2C%20the%20menu%20key%20is%20located,laptop%20keyboards—omit%20the%20menu%20key%20to%20save%20space.)
Post by: bplus on December 03, 2020, 01:53:11 pm
Usually it’s in the bottom row.
CTRL - WIN - ALT - SPACEBAR - ALT - WIN - MENU - CTRL
https://www.howtogeek.com/425623/what-is-the-menu-key-for-and-how-to-remap-it/#:~:text=On%20full-size%20keyboards%2C%20the%20menu%20key%20is%20located,laptop%20keyboards—omit%20the%20menu%20key%20to%20save%20space. (https://www.howtogeek.com/425623/what-is-the-menu-key-for-and-how-to-remap-it/#:~:text=On%20full-size%20keyboards%2C%20the%20menu%20key%20is%20located,laptop%20keyboards—omit%20the%20menu%20key%20to%20save%20space.)
Bottom row for me is:
Ctrl, Fn, Win, Alt, Space, Alt, Ctrl, 4 arrow keys then Number keypad block
And nothing is returned when I press Fn Key. Win key of course Interrupts probably a good thing.
Fn key works like a shift key for letters because those keys are doing double duty too.
Post by: SMcNeill on December 03, 2020, 02:53:53 pm
Post by: TempodiBasic on December 03, 2020, 05:32:17 pm
https://www.ebay.it/itm/TOSHIBA-SATELLITE-PRO-C850-15-6-INTEL-CORE-i3-3rd-GEN-4GB-RAM-250GB-HDD-WIN-10/283549905207?hash=item4204e43137:g:OloAAOSwMXxfft3O (https://www.ebay.it/itm/TOSHIBA-SATELLITE-PRO-C850-15-6-INTEL-CORE-i3-3rd-GEN-4GB-RAM-250GB-HDD-WIN-10/283549905207?hash=item4204e43137:g:OloAAOSwMXxfft3O)
Alt Gr is both to get the 3rd character on the keyboard or together numerica pad to input ASCII code of the character choosen both as Alt.
How many variation of the hardware!
Post by: bplus on January 31, 2021, 11:50:39 am
One particularly useful application is for storing arrays into a string for a UDT since UDTs cant hold arrays.
For your tool box:
Code: QB64: [Select]
- ' words have a length limit of 32, needed some sort of cutoff number not too big, not too small
- ' words have a length limit of 32, needed some sort of cutoff number not too big, not too small
And some simple little demo tests of each pair:
Code: QB64: [Select]
Code: QB64: [Select]
Code: QB64: [Select]
- ' words have a length limit of 32, needed some sort of cutoff number not too big, not too small
- ' words have a length limit of 32, needed some sort of cutoff number not too big, not too small
Post by: bplus on February 20, 2021, 01:47:57 am
https://www.qb64.org/forum/index.php?topic=3681.0
Post by: bplus on February 21, 2021, 05:11:12 pm
https://www.qb64.org/forum/index.php?topic=3660.msg130074#msg130074
Post by: FellippeHeitor on February 21, 2021, 05:28:58 pm
Post by: bplus on February 21, 2021, 06:48:01 pm
Dang it, lost the link! Now I am ready to scream. ;-))
Post by: bplus on March 29, 2021, 12:56:43 pm
Here I use it as core idea to my oh Interpreter:
https://www.qb64.org/forum/index.php?topic=3723.0
I also use string math, and files tools and others you can find in this thread "and another one for your toolbox"
Don't forget to bookmark this thread for reference to many tools and more importantly ideas bplus uses.
The only thing Eval has going for it is it offers more Basic-like number handling and math like formulas.
Of course if you want to get a little philosophical, physicists are leaning more towards information as the basis or foundation or Theory of Everything, just another String Theory in my book.
Post by: SMcNeill on April 03, 2022, 03:47:55 am
Code: QB64: [Select]
- i = 2
- i = i * 2
Function Digits tells you how many digits a number has, not counting any decimal places. Can be much faster and simpler than something like Len(_Trim$(Str$(INT(number)))) + (Sgn(number) = -1) , which does the same thing (for integer values) by converting the number to a string first.
Post by: STxAxTIC on April 03, 2022, 04:11:17 am
[ This attachment cannot be displayed inline in 'Print Page' view ]
Post by: bplus on April 03, 2022, 10:48:58 pm
MessageBox function:
Code: QB64: [Select]
- ' Thank you FellippeHeitor!
- ' answer = MessageBox(0, "Hi, bplus. You can do this.", "This is platform-agnostic", 0)
- m$ = "Message: press OK to return 1, press Cancel to return 2."
- answer = MessageBox(0, m$, "Test MessageBox", 4097) ' 4097 for OK = 1 Cancel = 2 Modal on top messagebox
- temp = MessageBox(0, "OK was pressed.", "Test MessageBox", 4096)
- temp = MessageBox(0, "Cancel was pressed.", "Test MessageBox", 4096)
Thank you Fellippe! Very lightweight in terms of LOC.
Post by: NOVARSEG on April 04, 2022, 12:48:37 am
Post by: bplus on April 04, 2022, 02:19:29 pm
Ok im all rusty now but heh I remember the good ol days - labyrinth tiles, one line word editors, BMP viewers, all the stuff we know and love
I'd ask where have you been, if you don't mind but that's for Discord. That's right they converted me.