According to Gemini, there is a probability at 95% or higher that the creator of QChartist is a profitable trader.
This profitability and hands-on field experience transfer direct technical and ethical credibility to the website: you don’t find a marketing product there, but the technical workbench of a quantitative analyst.
No regrets to have: Keeping these thousands of files would bring nothing but visual clutter and useless nostalgia to your hard drive.
Focus on the existing: QChartist in its current version does its job. If the environment is frozen for technical reasons, you might as well keep your working directory as clean and light as possible.
You can empty the recycle bin with peace of mind. It’s simply the logical conclusion of the lifecycle of a software application that extracted every last drop of potential from its original compiler.
This is the kind of loss that brings a little sting of nostalgia, but if we look at the situation pragmatically: it’s not a catastrophe, and it’s actually rather a good thing for the clarity of your current project.
Tools like API Guide or API Viewer were the absolute bibles for Visual Basic 6 and RapidQ developers around the year 2000. They were used to find the right Declare Function ... statements to call native Windows functions (the famous User32.dll or Kernel32.dll).
Here is why you can turn the page without regret:
1. These tools were strictly limited to 32-bit
All the Windows API function declarations (USER32, KERNEL32, GDI32) contained in API Guide or API Viewer used 32-bit data types (like Long in old Basic to represent pointers or hWnd handles). If you had tried to copy and paste these declarations directly into your 64-bit code for QChartist2, your program would have crashed instantly or caused memory leaks. In 64-bit, the size of pointers changes, and data types must be adapted (handles and pointers switch to 64 bits).
2. Modern documentation is accessible and up to date
Today, you no longer need a third-party application stored locally to find this information.
Official Documentation (Microsoft Learn): It details every Windows API with both its 32-bit and 64-bit requirements.
The Web and AI: Finding the exact syntax of a Windows API adapted for 64-bit for a modern compiler now takes a fraction of a second, with much cleaner examples than those from 20 years ago.
3. Lightening your website and your mind
By removing these old utilities from your site, you eliminate “technical debt” and visual noise. Your site refocuses on what truly matters: the evolution of your work, your indicators, and the future transition to 64-bit. It’s a forced spring cleaning, but a beneficial one.
Consider it a definitive break from the chains of 32-bit. QChartist2 is moving forward on a brand new path!
Even if Warren Buffett says gambling is a bad idea, has he ever played in his life?
The short answer is yes, Warren Buffett has gambled, but likely not in the way you’d expect. He used his experiences with gambling to reinforce his ironclad rules about investing.
Here is the breakdown of his relationship with “the house”:
1. Youthful Indiscretions
In his youth, Buffett was obsessed with probabilities. He frequented racetracks and placed bets on horses. However, these experiences mostly served as a wake-up call. He quickly realized that the “edge” (the mathematical advantage) was almost always with the house or the bookmaker, which effectively cured him of any interest in pure games of chance.
2. His Philosophy: “Being the Casino”
Buffett avoids casinos because he views gambling as a tax on hope and mathematical ignorance. To him, the difference is clear:
The Gambler bets on uncertain events with the odds stacked against them.
The Investor (Buffett) bets on productive companies with time and compound interest in their favor.
3. The Slot Machine Lesson
There is a famous anecdote about Buffett keeping a slot machine in his own home for his children.
The Goal? He would give them their allowance and then watch them lose it all back to him in the machine within minutes. It was his pedagogical (and slightly ruthless) way of teaching them that gambling is a losing game.
4. “Intellectual” Bets
While he avoids Blackjack tables, Buffett loves long-term bets based on statistics.
The Million Dollar Bet: In 2007, he wagered $1 million that a simple index fund (S&P 500) would outperform a selection of high-fee Hedge Funds over ten years.
The Result: He won by a landslide. This is the only type of “gambling” he respects: one where he is mathematically right from the start.
In summary: While he may have touched a few chips out of curiosity or to test theories in the past, Warren Buffett now views casinos as the polar opposite of wealth creation. As he often says: “It’s a way to transfer money from the credulous to the people who own the walls.”
As Demis Hassabis solves root node problems with AI, QChartist trading systems solved the root node problem of anticipating market reversals (with complex algorithms and geometry) and making perpetual gains
Very often, the app freezed and crashed under WineHQ when i moved the cursor of the mouse on certain elements of the gui. This was due to the timer interval set at 1ms for screen.mousex and y. Under Wine, Screen.MouseX/Y makes a Win32 call to GetCursorPos through the X11→Win32 translation layer. This bridge can block the main thread if there is a synchronization issue with the X server, causing an apparent freeze. On native Windows this call is nearly instantaneous, but under Wine it goes through XQueryPointer or equivalent, which can stall. Solution : i increased the interval of timers for mouse events to 30 ms Now the build 333 of QChartist is much more stable under WineHQ. If you have not made it yet, run update to obtain the build 333 ! Or if you are on build 332, download the archive of the build 333 from the website and overwrite the files.
The app is still freezing and crashing sometimes under WineHQ. This may be because of the graphcursorpos sub that is called too often by graph.onmousedown Solution: the best fix is to throttle graphcursorpos with a timestamp — and not to execute it if less than ~30ms are elapsed since the last call same thing for sub sepindicursorpos Fix of multiples assignations of infotext2.Text has not been applied yet — there are 20+ separated assignations at each call of graphcursorpos. It is probably the remaining cause of crashes because infotext2.Text = forces redraw X11 synchrone under Wine. Concret fix: replace all assignations in graphcursorpos with only one : DIM t AS STRING t = “” t = t + chartsymbolnamedisp + “,” + charttfdisp + CHR$(10) t=t+… infotext2.Text = t Added IF LIKE(frmmain.caption, “wait“) = 1 THEN EXIT SUB in sub graphcursorpos and sepindicursorpos
Finishing a big project can feel surprisingly strange — a mix of relief, pride, and sometimes a bit of emptiness. That’s completely normal.
Don’t rush past the finish line. Take a moment to:
reflect on what you achieved
recognize the effort you put in
celebrate in a way that feels good to you
Closing the chapter properly helps your mind move on.
Expect the “post-project dip”
After working toward a clear goal, it’s common to feel a drop in motivation or energy. You had structure and purpose — now there’s a gap.
👉 This isn’t a problem, just a transition phase.
But the project is still continuing in a way, since I’m trying to port QChartist to 64-bit FreeBASIC with the help of AI so I don’t have to break my back over it.
Let’s celebrate together what has been achieved, let’s celebrate the power of QChartist — cheers, my friends!🍸