you guys were all over that like dobermans on a tossed sausage link

@albert

I like your premise. I too have fascination with attraction / repulstion, and am inclined to believe that light travels through a type of 'liquid'

As Richard pointed out, typically our most prevalent "map" is analogy.

I read more of your zine #1 than what I usually read from anything (unless it's technical information)

@dodi - that's pretty cool

Looking forward to seeing your sorts demo.

Update: properly formatted to eliminate aforementioned errors :)

[2014 March 17] - cartesian tree merge [2012 May 27] - new qsort [2011 Aug 27] - minor optimizations to the QSorts ' ============================= ' visual sorts by c_rex ' ' Ver. 0.96 - 2014 Mar 27 ' ' (0.95 will be next version) ' ' ============================= /' ------- Notes ------- lerp, casc...

Researching CombSort (which I am in love with) I discovered that some sorts perform better starting at the edges, working inward.

So the bubble will go like so:

That's interesting. I see one optimization:

For x= Ubound(a) To Lbound(a)+index+1 Step -1
a(x)=a(x-1)
Next x
a(x)=insert

It's just a selection sort. QSort shines with bigger lists. What I'm thinking would be cool is a "Linked List" sort which could sort chunks of say, 256 elements.

Keep in mind that selection sort will do well here because it intentionally keeps swaps to a minimum.

UPDATE: lol. I see my edit hadn't occurred in time. The J as Long can simply be integer. I had overlooked it converting from VB.

Here's my bi-di selection sort Dim as Integer Position_of_Hi, Position_of_Lo, S_, J ' Pass lowerbound and upperbound as Start_ and End_ Sub BiDiSelectSort(Ary() As Single, Start_ As Integer, End_ As Integer) Do While Start_ < End_ Position_of_Hi = Start_ Position_of_Lo = Start_ S_ = ...

vdecampo's post on qsort got me hyped. I intended to speed up the bubble sort by storing location of lowest and highest values, and researched thereafter, finding that I had coded a bi-directional selection sort. It's about twice as fast as bubble

I had a quick look, and might have a better idea of what's happening from comments, than code (where I feel mostly clueless).

Recently I developed a sprite sheet tile dims estimator that messes up when there's only 1 tile!

I'll need to get back to it.

Howdy folks. Here are 2 low level gfx routines I've been sitting on. DrawLine() is unique in that x and y become meaningless after I've passed control to nested subs. AreaFill() is my second attempt at a flood fill algorithm. My first, while running perfectly (after many wrinkles), crashed from stac...

ah, without really understanding the code, I posted this.

I assumed sample size to be applied in a manner affecting 'line segments'