Closed klytje closed 11 months ago
Cool! I've been thinking about that this morning!
Screenshots please! :-)
Screencast from 12-06-2023 07:47:17 PM.webm
Now that I look at it, I think the example could use a little bit of polish with some titles and sections maybe
The <size, major_divs, minor_divs> API is better.
Here's a suggestion:
slider_marks
with the updated template params, along with slider_marks_element
.slider_marks_lin
and slider_marks_lin_element
slider_marks
and alias template (or subclass, if alias is not possible) slider_marks_element
, both in terms of slider_marks_lin
and slider_marks_lin_element
.@redtide is there a way to swash the commits posthoc via github?
@redtide is there a way to swash the commits posthoc via github?
Ah seems there is: https://bit.ly/3uU2EPP
@redtide is there a way to swash the commits posthoc via github?
Ah seems there is: https://bit.ly/3uU2EPP
Didn't know it was there all along!
I implemented a new element
slider_marks_log
and showcase it in therange_slider
example.I couldn't figure out how to do this correctly while limiting myself to the original
<size, num_divs, major_divs>
template, so I switched it around (for this element only) to<size, major_divs, minor_divs>
instead. For consistency I think either the normalslider_marks
element should also be updated with this, or alternatively remove theminor_divs
template from this new element and hardcode it to10
. I don't see any reason to use a different number than this anyway.