Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - Richard

Pages: [1] 2 3 ... 5
1
QB64 Discussion / QB64 Development builds
« on: January 18, 2022, 08:20:26 pm »
Unless I went to the wrong site (or something)...


The development  build comes up as (for example)

qb64_development_win-x64.7z



Previously, the name included Date & Time and Version number.

Although I can get the version number quite easily, it would be nice to know these details BEFORE downloading the file.

2
QB64 Discussion / [v2.1 dev build] $DEBUG - problem with _FREEIMAGE ...
« on: November 30, 2021, 06:50:52 pm »
@FellippeHeitor

9f81ba1 dev build   Windows x64 Pro 21H1 Nov updated


When switching around various sources and using _FREEIMAGE ... eg with the partial code below

t& = _NEWIMAGE(wdth, hght,32)
SCREEN t&

...

IF t& < -1 then _FREEIMAGE t&   'This is line xxx
_SOURCE t&


get   "Error occurred on line xxx" message  and $DEBUG does not reach my breakpoint.


As $DEBUG now stands - it is totally un-useable for me when I have _FREEIMAGE code.

3
QB64 Discussion / Help with QB64 code to resize and reposition apps (e.g.NotePad)
« on: November 16, 2021, 11:34:12 am »
Anyone able to assist with QB64 code (or API or something) to allow the resizing and repositioning of an app (e.g. NotePad)?

Ideally, say NotePad is launched by


SHELL _dontwait "NotePad"

which despite previously having been sized/positioned often appears in a different position and to a lesser extent, a different size.

Assuming I can program calculate how far to move (to the desired location) - my problem is to in a program reposition the app (also maybe re re-size it).

So far I cannot seem to establish the handle via the SHELL _dontwait command - in any case when I can determine the handle (by a few methods, e.g. via PID, TaskManager,etc) and try to "plug-in" the handle into various API's (eg MoveWindow) - NOTHING seems to happen (no resizing/relocating).

Using Windows 10x64 Pro 21H1 (Nov updated)

4
QB64 Discussion / [v2.1 dev build] $DEBUG - when running, breakpoint reached display position
« on: November 08, 2021, 06:17:43 pm »
@FellippeHeitor

dev 9f81ba1   Windows 10 x64 Pro  21H1 (Oct updated)


Feature request - user option to allow running breakpoint to be anywhere else then the current MIDDLE of the IDE.

When working with say minimum  IDE window, and say 8 watch variables - the breakpoint line is hidden behind the Watch List variables box. By allowing to reposition (other than the default IDE MIDDLE), can see both Watch List and breakpoint line. This saves the step of having to navigate via up/down arrow keys to manually reposition breakpoint IDE position.

5
QB64 Discussion / [v2.1 dev build] IDE issue - mouse click button change
« on: November 08, 2021, 01:03:59 pm »
@FellippeHeitor

dev 9f81ba1  Windows 10 x64 Pro 21H1 (OCT updated)


The right mouse (TouchPad) button has to be used to navigate around the Open Files selection in this dev build - whereas the left mouse (TouchPad) button is used in the stable build v2.0 07b2101.

How to restore to left button for dev build??


6
QB64 Discussion / How to remove title Bar from graphics screen?
« on: October 29, 2021, 12:31:59 am »
Fullscreen does not show Title Bar - want the same feature when not in full screen graphics.  The wiki example only seems to work for text screens.

7
QB64 Discussion / [v2.0 build] $DEBUG STRING * and DIM SHARED global suffixes
« on: October 27, 2021, 06:40:09 am »
@FellippeHeitor



Thankyou very much for adding the relevant suffixes into the Watch List Box for e.g.



DIM scan_line as STRING *32             -->  scan_line$32 (in watch list box)

DIM SHARED Result AS _INTEGER64   -->  Result&&       (in watch list box)



this would help minimize confusion with my programming style.

8
QB64 Discussion / [v2.0 dev build] Python file question
« on: October 27, 2021, 03:48:39 am »
On auto start-up of QB64 (via Task Scheduler) where the latest dev build (c48bf67 2021-oct-22 x64) being a zip is unzipped to the RAM drive to folder A:\QB64\   I get the following message.


  [ You are not allowed to view this attachment ]  




For all the dev builds I was just only running from the RAM drive directly (not via Task Scheduler) so I do not know when this message first occurs (via Start-up).

Can someone advise me on this particular file please?


9
QB64 Discussion / [dev v2.1 build] $DEBUG - Path resolution / watch window history
« on: October 17, 2021, 08:34:39 pm »
@FellippeHeitor

dev 45fed46 WIN 10 x64 Pro build 21H1 (Aug update)


I may have omitted the obvious but...



When I have the dev build in the folder "A:\QB64_dev\" and my also with my stable build (v2.0) on    "C:\_QB64\"  - (note that v1.5 stable is on   "C:\QB64\") then when working with the exact same file to debug (i.e. no changing ever of filename or path) - debug does not "remember" the selected watch list WHEN I RESTART QB64.exe.

It only seems to "remember", for me, the selected list when just re-running the program (F5).

10
QB64 Discussion / [dev v2.1 build] $DEBUG apply last Watch List window Location/Size
« on: October 16, 2021, 08:43:51 pm »
@FellippeHeitor

Would you be able to arrange that the F4 Watch List window position and width settings are also saved and applied (just as with the variables)?

Currently with a program I am debugging (many reloads involved) the 21 characters for the string variables are just not enough (I have to ideally go to about 40) - at present I have to insert an extra string variable to allow viewing of the next 20 characters of the viewed string


11
QB64 Discussion / *** FIXED *** [dev build] $DEBUG _MEM problem *** string variable too large***
« on: October 09, 2021, 09:23:52 pm »
@FellippeHeitor


Is this a "feature" or a "bug"?

When F4 adding to watch list for _MEM stuff - can only add

+OFFSET
+SIZE
+TYPE
+ELEMENTSIZE
+IMAGE
+SOUND

cannot add

$_LOCK_ID
$_LOCK_OFFSET

as this results in

Error
Cannot add full UDT to Watch List






12
QB64 Discussion / _SCREENPRINT text$ Question
« on: October 04, 2021, 07:00:06 pm »
I have referred to the Wiki regarding _SCREENPRINT text$ and wanted to know if there was any way to allow _SCREENPRINT to accept the equivalent of     [Ctrl] + {+}     to enlarge the focused window (when this action is allowed).

As an example, when from QB64 I open NotePad it comes up with the default tiny text size (I do not wish to use say 200% windows scaling for my High DPI Display) and as always with NotePad I need to do    [Ctrl] + {+}    to enlarge the text to a more pleasant size.

Further to this can _SCREENPRINT in general be able to work with any key-combinations eg    [Alt] + [3] 
  and for that matter key scan codes and the such in general?

13
QB64 Discussion / [dev build] (general) error pop-up binary file reference
« on: October 03, 2021, 01:31:49 am »
@FellippeHeitor

v2.0 48e8f38  win 10x64 Pro  21H1 (Aug updated)


Many thanks for displaying first part of binary file in the error pop-ups - makes it very much easier to sort out  when having multiple instances of QB64

14
QB64 Discussion / [dev build] IDE (general) preserve user inserted spaces
« on: October 02, 2021, 10:59:10 pm »
@FellippeHeitor


I thought that a long time ago that with the IDE one could choose between using the auto-tabbed indents and not at all auto tab. If I recall correctly it was not practical for me since if I created code without the auto tabs and accidently loaded the program without disabling the IDE auto-tab feature then all my "manual custom spaced out code" would be auto-tabbed and would not maintain the "column line ups" I previously set up beforehand for the code layout.

Partly along the lines of above - feature request as a IDE flag - still having auto-tab (as is as present), if IDE flag is set, force the IDE NOT TO reformat the current line to the standard tab/spacing processing rules (as is now present) and allow the file to be saved with the (hybrid) auto-tab (as standard with the IDE) together with my "custom spacing "over-ride"".

Although I could write my entire program (with my custom added spaces where I really want them) using say NotePad - it is a pity not to be able to use your fantastic IDE in the manner (custom spacing override) for this purpose.

Of course, if I ever accidently change the IDE flag then I will lose the custom program formatting. (In my case it would be likely that "forever" I would leave the flag set - as any existing auto-tabbed/spaced formatted program ever written would still display as originally intended.)


15
QB64 Discussion / [dev build] $DEBUG Scientific notation *** ultra low priority ***
« on: September 29, 2021, 01:27:42 am »
@FellippeHeitor

v2.0  049499c   Win 10x64 Pro  21H1 (Aug update)


Some issues regarding scientific notation - notes as part of output


Note that precision is not an issue (depends on the number of bits per variable type).



Code: QB64: [Select]
  1. $DEBUG
  3. dev$ = "v2.0  049499c Win10 x64 Pro 21H1 build (Aug updated)"
  4. DIM AS FLOAT ff, fff, ffff
  5. s! = s!
  6. DIM AS SINGLE s000, s001, s010, s011, s100
  7. d# = d#
  8. DIM AS DOUBLE d000, d001, d010, d011, d100, d101
  9. f## = f##
  10. DIM AS FLOAT f000, f001, f010, f011, f100, f101, f110, f111
  11. a$ = "": darta$ = ""
  12. DIM llllllllll
  13.  
  14. ff = 1.0E30::: COLOR 12: PRINT "ff    ";: COLOR 15: PRINT ff##;::: PRINT USING "###,###,###,###,###,###,###,###,###,###,###"; ff##;::: COLOR 28: PRINT " precision  ";: COLOR 30: PRINT "$DEBUG 1D+30"
  15. fff = 1.0D30:: COLOR 12: PRINT "fff   ";: COLOR 15: PRINT fff##;:: PRINT USING "###,###,###,###,###,###,###,###,###,###,###"; fff##;:: COLOR 28: PRINT " precision  ";: COLOR 30: PRINT "$DEBUG 1D+30"
  16. ffff = 1.0F30: COLOR 10: PRINT "ffff  ";: COLOR 15: PRINT ffff##;: PRINT USING "###,###,###,###,###,###,###,###,###,###,###"; ffff##;: COLOR 26: PRINT " OK  $DEBUG = OK"
  17. s! = s!: COLOR 11: PRINT "_SINGLE    ";: PRINT "wiki !   -2.802597e-45   to   +3.402823e+38 ":
  18. s000 = 1E7:::::::::: COLOR 10: PRINT "s000  ";: COLOR 15: PRINT s000;: PRINT USING "###,###,###"; s000;: COLOR 26: PRINT " OK  $DEBUG = OK":
  19. s001 = 10E6::::::::: COLOR 10: PRINT "s001  ";: COLOR 15: PRINT s001;: PRINT USING "###,###,###"; s001;: COLOR 26: PRINT " OK  $DEBUG = OK":
  20. s010 = 3.402823E+38: COLOR 10: PRINT "s010  ";: COLOR 15: PRINT s010;: COLOR 26: PRINT " OK  $DEBUG = OK":
  21. s011 = 3.402824E+38: COLOR 12: PRINT "s011  ";: COLOR 15: PRINT s011;: COLOR 26: PRINT " INF = OK   ";: COLOR 28: PRINT "+ garbage  ";: COLOR 30: PRINT "$DEBUG = INF + garbage"
  22. s100 = 1000000E1000: COLOR 12: PRINT "s100  ";: COLOR 15: PRINT s100;: COLOR 26: PRINT " INF = OK   ";: COLOR 28: PRINT "+ garbage  ";: COLOR 30: PRINT "$DEBUG = INF + garbage"
  23. d# = d#: COLOR 11: PRINT "_DOUBLE    ";: PRINT "wiki # -4.490656458412465e-324   to   +1.797693134862310e+308": COLOR 15
  24. d000 = 1.797693134862310E+308: COLOR 10: PRINT "d000  ";: COLOR 15: PRINT d000;: COLOR 26: PRINT "  OK  $DEBUG = OK":
  25. d001 = 1.797693134862311E+308: COLOR 12: PRINT "d001  ";: COLOR 15: PRINT d001;: COLOR 30: PRINT " The value > than wiki limit - so INFINITE"
  26. d010 = 1.7976931348624E+308::: COLOR 12: PRINT "d010  ";: COLOR 15: PRINT d010;: COLOR 26: PRINT " INF = OK   ";: COLOR 28: PRINT "+ garbage";: COLOR 30: PRINT "  $DEBUG = INF + garbage":
  27. d011 = 1.797693134862310D+308: COLOR 10: PRINT "d011  ";: COLOR 15: PRINT d011;: COLOR 26: PRINT "  OK  $DEBUG = OK":
  28. d100 = 1.797693134862311D+308: COLOR 12: PRINT "d100  ";: COLOR 15: PRINT d100;: COLOR 30: PRINT " The value > than wiki limit - so INFINITE"
  29. d101 = 1.7976931348624D+308::: COLOR 12: PRINT "d101  ";: COLOR 15: PRINT d101;: COLOR 26: PRINT " INF = OK   ";: COLOR 28: PRINT "+ garbage";: COLOR 30: PRINT "  $DEBUG = INF + garbage":
  30. f## = f##: COLOR 11: PRINT "_FLOAT    ";: PRINT "wiki ##  -1.18e-4932   to   +1.18e+4932"::
  31. f000 = 1.18E+4932: COLOR 12: PRINT "f000  ";: COLOR 15: PRINT f000;: COLOR 30: PRINT " The value = wiki limit - so NOT infinite"
  32. f001 = 1.18E+4933: COLOR 12: PRINT "f001  ";: COLOR 15: PRINT f001;: COLOR 26: PRINT " INF = OK   ";: COLOR 28: PRINT "+ garbage";: COLOR 26: PRINT "  $DEBUG = OK ":
  33. f010 = 1.18E+4930: COLOR 12: PRINT "f010  ";: COLOR 15: PRINT f010;: COLOR 30: PRINT " The value < wiki limit - so NOT infinite ":
  34. f011 = 1.18D+4932: COLOR 12: PRINT "f011  ";: COLOR 15: PRINT f011;: COLOR 30: PRINT " The value = wiki limit - so NOT infinite"
  35. f100 = 1.18D+4933: COLOR 12: PRINT "f100  ";: COLOR 15: PRINT f100;: COLOR 26: PRINT " INF = OK   ";: COLOR 28: PRINT "+ garbage";: COLOR 26: PRINT "  $DEBUG = OK ":
  36. f101 = 1.18D+4930: COLOR 12: PRINT "f101  ";: COLOR 15: PRINT f101;: COLOR 30: PRINT " The value < wiki limit - so NOT infinite ";: LOCATE 24, 1
  37. f110 = 1.18F+4932: COLOR 12: PRINT "f110  ";: COLOR 15: PRINT f110;: COLOR 30: PRINT " The value = wiki limit - so NOT infinite";: LOCATE 25, 1
  38. f111 = 1.18F+4933: COLOR 12: PRINT "f111  ";: COLOR 15: PRINT f111;: COLOR 26: PRINT " INF = OK   ";: COLOR 28: PRINT "+ garbage";: COLOR 26: PRINT "  $DEBUG = OK ";:
  39. a$ = " ": darta$ = "DATA"
  40. DATA 123,e7,0e7,1e7,10e6,10e39,100000e1000,+3.402823e+38,+3.402824e+4932,+3.402823e+100000
  41. DATA 456,1d7,10d7,+1.797693134862310e+308,+1.797693134862310e+309
  42. DATA 789,1f7,10f7,100f7,1234f77,0,+1.18e+4932,+1.18d+4932,+1.18f+4932,+1.18f+100000
  43. DATA NotScientific,10000ee12345,12345e6789e123,123e45f00
  44. llllllllll = llllllllll: SYSTEM
  45.  
  46.  
  47.  






 [ You are not allowed to view this attachment ]
 [ You are not allowed to view this attachment ]  
 [ You are not allowed to view this attachment ]  
 [ You are not allowed to view this attachment ]  
 [ You are not allowed to view this attachment ]  

Pages: [1] 2 3 ... 5