I have already written around 1000 lines of code. I expect the whole project to be under 2500 lines. Have to finish before monday.
Writing in C with the usage of windows.h.
The features left to implement:
Instead of drawing things to screen, use buffer, and update the window as a whole.
Filling in polygons.
Slicing polygons.
Draw curves with different methods.
Redacting curve's derivative after it is drawn.
Optional: compile into a library.
Time rounds down. I am counting only the time when I am literally working on the project, rest periods do not count in.
1,000🏅 Top traders
| # | Name | Total profit |
|---|---|---|
| 1 | Ṁ499 | |
| 2 | Ṁ46 | |
| 3 | Ṁ39 | |
| 4 | Ṁ32 | |
| 5 | Ṁ28 |
687 Diffficult bug.
637, just one big bug is left. Program crashes with exit codes 322.. or 3 when a sliced polygon is filled.
There is a minor bug than one line in filling is skipped.
439 minutes. Slicing done.
Fill in triangles with one merhod and filll in polygons with another method is what is left.
344 minutes. All about curves is done.
Only slicing and filling is left. Slicing is hard, but i expect filling to be moderate.
After 273 minutes total i have completed buffer and one of 3 methods for curves. Also I now do not need to do "redacting derivatives" because I managed to apply the polygon transformations onto curves without any changes.
(From the very beginning I used the same data structure for both, which now payed out).
I will not do the optional part, because I found out that deadline is moved closer to noon Sunday.
Everything about buffer works right, instant images, no flickering. But I somehow broke color system and all colors are substituted by their complements.
110 minutes in.
Buffer initiates successfully, program draws what is needed. But window is redrawn EVERY frame due to recursive call (surprisingly very responsive), and when I avoid recursion and redraw the window only when the contents change, nothing happens. I want to get rid of recursion, might lose points if i draw every frame instead of minimising the load of the app.
Let the battle begin.
I have a whole 3day weekend specifically dedicated for this.
@KongoLandwalker lol
I was joking about switching, and I can't tell if you're joking or if you actually think C is easier than Rust
@Pykess you miss the context. Learning a new syntax BEFORE monday is not as easy as keeping using C, which I am familiar with for 2 years. Any familiar thing in a limited timeframe is easier than a new thing of the same class. I am sure that Rust is does not have the margin in the difficulty big enough to payback.
@KongoLandwalker but going from J to Wolfram, for example, has such a jump in difficulty decrease, that I would switch mid-project.