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.


Messages - SkyCharger001

Pages: [1]
1
QB64 Discussion / Re: Poke to screen 0 for speed
« on: August 03, 2018, 01:50:46 pm »
MEMGET/PUT allow you to bypass some checks performed by the normal graphical functions.

2
QB64 Discussion / Re: Register problem
« on: July 28, 2018, 05:41:54 am »
kind of like personal account vs. business account? (EG: statements from the former are what you think, statements from the latter are what the company you represent think.)

3
QB64 Discussion / Re: Why _MEM.OFFSET?
« on: July 22, 2018, 08:49:56 pm »
I think it's to allow us to control when the lookup is performed, instead of doing it every cycle or whenever the _mem-functions are called. (even the ones that never need the lookup.)

4
QB64 Discussion / Re: Is this fast enough as general circle fill?
« on: June 27, 2018, 05:33:54 pm »
I've been thinking and I think I know why BF is faster.
without BF: multiple line segments that need to be calculated using floating point math. (as line can be of any angle)
with BF: Y horizontal lines of length_X that only require integral math.(for initializing the drawing loop)

5
QB64 Discussion / Re: Is this fast enough as general circle fill?
« on: June 26, 2018, 04:44:11 am »
about the LINE BF,
Code: QB64: [Select]
  1. LINE(cx%-px!,cy%-py!)-(cx%+px!,cy%+py!),63,bf
instead of
Code: QB64: [Select]
  1. LINE(cx%-px!,cy%-py!)-(cx%+px!,cy%-py!),63,bf
should save you half of the LINE calls

Yes, but if you are using alpha coloring, the overlapping boxes might NOT give you an even shade.
Ah, didn't think about that.
one solution (that might ruin the speed-gain) would be to draw the filled circle on a temporary indexed image with color 0 set to RGBA(0,0,0,0) for masking and color 1 set to whatever RGBA color you want, and _PUTIMAGEing it onto the target image.

6
QB64 Discussion / Re: Is this fast enough as general circle fill?
« on: June 25, 2018, 02:55:44 pm »
about the LINE BF,
Code: QB64: [Select]
  1. LINE(cx%-px!,cy%-py!)-(cx%+px!,cy%+py!),63,bf
instead of
Code: QB64: [Select]
  1. LINE(cx%-px!,cy%-py!)-(cx%+px!,cy%-py!),63,bf
should save you half of the LINE calls

7
QB64 Discussion / Re: A Few Crazy Suggestions for QB64's Source Code
« on: March 04, 2018, 11:03:03 am »
Removing the internal help-cache is a bad idea:
how is one supposed to access the help-data when either [abandoned, outdated and now likely malicious qb64 dot net website - don’t go there] or your internet-connection is down if you don't have a cache?

8
QB64 Discussion / Re: QB64 coding challenge
« on: July 27, 2017, 01:45:34 pm »
page 106 (108 according to the PDF-reader) confirms my suspicion: Td precedes all AMOS 3D specific commands.

9
QB64 Discussion / Re: QB64 coding challenge
« on: July 26, 2017, 03:16:57 pm »
I've tried to look it up and all references I found focused on AMOS 3D, an extension to base-AMOS.

this suggests that "Td" means the command is intended for that extension and not base-AMOS.
It also suggest to me the "Td" is a variable-/function-naming-rules friendly rendition of "3D".

10
QB64 Discussion / Re: Is rolling your own really that important?
« on: July 25, 2017, 11:04:55 am »
E.  If it's your own work, it's easier to troubleshoot, edit, and customize.
Guess you can call C a corollary to that. (or vice versa)

11
QB64 Discussion / Re: Is rolling your own really that important?
« on: July 25, 2017, 02:59:21 am »
A. While a library might perform the tasks you desire, sometimes they don't do it with the efficiency you desire.
B. Using a third-party library might require you to violate you own rules of programming.
C. You may wish to understand the low-level aspects of what is being done.
D. There might be licensing issues (if not with the library directly then with how it's sub-libraries are licensed.)

12
QB64 Discussion / Re: Burning ship explorer
« on: July 23, 2017, 11:55:07 am »
you only need to calculate the screen-center once
Code: QB64: [Select]
  1. CONST sw=640
  2. CONST sh=480
  3. CONST zw=sw/2
  4. CONST zh=sh/2
  5.  

13
QB64 Discussion / Re: Compound assignments
« on: July 23, 2017, 05:43:56 am »
all you need for a UDT array is a _MEM-block

14
Programs / Re: Brainfuck Interpreter
« on: July 20, 2017, 09:00:35 am »
make ptr an unsigned integer and underflow/overflow will cause a wrap-around instead of a crash. (you won't need to handle them manually)

Pages: [1]