Porting Geonkick to Windows marks a new milestone. The Cairo based graphics backend now draws on the main window, simplifying UI porting with minimal changes to the Geonkick core GUI engine. "#Windows #geonkick #Cairographics
Porting Geonkick to Windows marks a new milestone. The Cairo based graphics backend now draws on the main window, simplifying UI porting with minimal changes to the Geonkick core GUI engine. "#Windows #geonkick #Cairographics
Someone wrote to me that they found my blog posts about #CairoGraphics and #Ruby quite helpful. So, I'm reposting the links to help others find them.
* Converting code from Cairo to RCairo: https://notepad.onghu.com/2021/cairo-rcairo-porting/
* Samples using RCairo: https://notepad.onghu.com/2021/cairo-samples-in-ruby/
I'll be streaming #CodingTogether this evening.
This evening I'm going to resume the hex-grid project, especially now that I have it posted to my open source repository. I'll be figuring out more about how the cropping tools in #CairoGraphics works, and refactoring the relationship between a Terrain and a Tile. Hopefully I'll finish the evening with a full rendering of the example map that I made a few weeks ago!
Join me on my Youtube channel at 9pm EST (-0500 UTC)
The things I want to add to #Mandelbrot #Perturbator #GTK this week are varying in difficulty.
Hard:
Currently you can select an item in the annotation list on the right hand side of the user interface window, and it is highlighted in the fractal explorer window. But when you have a lot of annotations, trying to find a specific annotation gets tedious. So I want to make it so I can click in the explorer window and have it select the annotation in the list.
I think I can do this by drawing the annotations (using the #CairoGraphics library) into an off-screen buffer with anti-aliasing turned off and annotation ID values as colours. I'll probably draw the rays thicker than 1 pixel in this buffer, otherwise selecting will be a nightmare. I already have one off-screen buffer used for text collision/overlap avoidance (aka dynamic level of detail), I might be able to reuse it. Ray sort order should be by (preperiod+period) (lowest drawn last / on top) to be intuitive, text b-boxes on top.
Medium:
Add a button to annotate an embedded Julia set automatically, because marking all those points and rays is a bit boring.
Easy:
Add a number box for hiding rays whose (preperiod+period) is higher than this threshold, as a stop-gap until I figure out how to choose this threshold (or another way to prune rays) automatically.