|
So how about wrapping it in a kind of de-reference handler for the user to use.
The user only creates one Context object, which contains the current draw_target.
Changing modes doesn't create a new object for them, but sets the internal draw_target of the Context.
The draw::line methods accept the Context instead of the draw_target and access the internal draw_target.
There is much I don't understand about what you're doing with the template binding, so this may not be at all feasible. It's also adding an abstraction layer, and I know you're working in resource constrained environments. However, that abstraction layer may be what you need to present a better API to the user.
|
|
|
|
|
That's not possible because there is no common base to use.
Different draw targets are entirely distinct types.
Furthermore, each draw target is typed by the type of its pixel.
So for example, if you have a bitmap<rgb_pixel<16>> and bitmap<rgb_pixel<24>>, the former indicating a bitmap with 16-bit color RGB pixels and the latter indicating 24-bit RGB, each bitmap is a different type. And it must be because the drawing code for a 16-bit pixel is different than that of a 24-bit pixel because the layout in memory of what it's drawing is different.
A bitmap<> is an example of a draw target, but each screen you can draw to is a draw target as well. A draw target is anything you can draw on.
Ergo, each screen mode is also a draw target, and if it has a different type of pixel than the next, it must be a different type.
There can be no common base since 90% of the drawing methods will take a pixel and that has a particular type. So even if i made a base type, that type would have to be a template.
This is generic programming and it's powerful, but it's not polymorphic in the traditional way we think about polymorphism.
It sounds like you might be a C++ dev but I don't want to assume. If you're not a C++ dev I'm not sure if there's an analogy for this style of coding in any other language.
OO principles only loosely apply here though. GP is a different animal.
Real programmers use butterflies
|
|
|
|
|
No, I've never developed anything in C++. Plenty of other languages, including plain C, but not C++. I have a vague theoretical understanding of what you're doing and would love to have time to explore it more (sadly, I don't)
Logically, if I have a screen device configured in a particular mode and I reconfigure it to a new, incompatible mode, then I am essentially removing one device and adding another.
All reference to the original device is now invalid, and any attempt to reference it is invalid.
If, as a programmer using your library, I make an invalid call, I would expect a simple error back.
The trickier question now becomes, if I reconfigure it back, am I adding the original device back? I'd say no, it is a new device with the same configuration as one that was previously removed.
|
|
|
|
|
Thank you! That's actually very helpful. I've been considering your approach but my fear was that it would be difficult or counterintuitive. Since you basically articulated to me that you expect precisely one of the avenues I was considering, it seems I have a clear winner in terms of approaches to this.
Real programmers use butterflies
|
|
|
|
|
I do not know the details of your code, only what I read in this thread, but I was thinking the same as NeverJustHere with one change.
I would probably make the class defining the device/target a singleton so that getting a new target would make the old reference point to the new target and probably no errors would have to be thrown.
If a method is added to check the current drawing mode you have all your bases covered.
Maybe! 
Hope it helps. Good luck.
|
|
|
|
|
Yeah that's not doable because each mode must be a fundamentally different type. You can't represent mode 1 with a class for mode 2.
If you could, I'd just have a "set mode" method on the driver class, and then use the driver class as the draw target like i do with my single screen mode drivers.
Real programmers use butterflies
|
|
|
|
|
The Witch wrote: I bind using templates, not virtual base classes
That's your problem right there. 
|
|
|
|
|
It would be impossible to do what I am doing efficiently and by hand in C++ using any other method than what I'm doing.
Generic programming has no real substitute in terms of C++ functionality. You basically *can't* replace it with virtual base classes unless you were using it where you didn't need it in the first place.
Consider this:
I have a pixel. The pixel is user-defined in terms of the number of color channels it has, their names, and what their binary layout, min and max channel values are, etc. This is too involved to compute at run time. It would kill performance
Now, for every draw method, it deals in pixels like this, but because a pixel must be typed to its functionality, literally the only way I could make it polymorphic is to use a vtbl every time i needed a pixel. That's just not acceptable in terms of performance.
Binding using templates is the solution. That way you can inline, or you can otherwise aggressively optimize away those calls.
Real programmers use butterflies
|
|
|
|
|
Wouldn't polymorphic flyweights work?
You've piqued my interest. If one of your recent articles discusses this code, please point me to it.
|
|
|
|
|
I don't have an article that explicitly talks about how the code works, just how to use it.
But..
gfx_demo/gfx_pixel.hpp at master · codewitch-honey-crisis/gfx_demo · GitHub[^]
Consider the convert<>() routine starting at line 690.
It's massive. It's ugly. It would be slow as heck to do at runtime. This will get called width*height times during a call to draw a bitmap when format conversion needs to be done.
If any of the routine did not result in aggressive compile time operations, to where this routine translates to a few shifts and multiply/divides at worst - the thing would slow to a crawl if I had any JMPs in there. There are none despite what it looks like, except sometimes for clamping, which often gets compiled to ifless code anyway.
Real programmers use butterflies
|
|
|
|
|
|
Not even a little.
Real programmers use butterflies
|
|
|
|
|
Time to look at some creational design pattern?
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
I have no choice but to use the factory pattern for creation.
Real programmers use butterflies
|
|
|
|
|
When you're stuck on a super important issue with significant consequences and you just can't decide which of your options is the best one, use The Grand Query Of Decision Making (TGQODM).
Its MySQL version looks like this:
SELECT IF(RAND() < 0.5, 'Do option 1', 'Do option 2')
|
|
|
|
|
I'm not sure if I even fully understand the problem but it sounds a bit like you could benefit from a design change where you maintain state information for each draw mode. This would allow you to switch between modes without loosing anything since all relevant data would be saved before switching modes.
|
|
|
|
|
I don't have that kind of memory. The e-paper displays essentially require me to keep the frame buffer around in local RAM. So my size in bytes for monochrome black and white displays is width*height/8 and it gets worse when you introduce virtualization of higher bit depths through dithering, such that you can simulate 8-bit grayscale for example, but at that point your frame buffer size becomes simply width*height in bytes. Ouch. That's my state for each mode.
It's not a good idea to hold a frame buffer around when someone is not using it on these devices. The devices I'm targeting with these displays range in RAM anywhere from about 300k to 4.5MB, with the caveat that 4MBs of that is PSRAM over SPI and thus slow.
Real programmers use butterflies
|
|
|
|
|
In the past, I had to solve that kind of problem by using buffer switching. To do that you can save the buffer to the PSRAM and then when you switch back to it you can save the current buffer and then load the next buffer if it was saved.
|
|
|
|
|
I mean yes, but there's a number of problems with that.
For starters, there might not be room in NVS flash to do that.
Second, it's a performance killer
And finally, it doesn't seem that intuitive to hold the screen buffer for multiple simultaneous screen modes around when a screen can only display one at a time. Or at least I should say I can think of as many arguments as to why it's counterintuitive as the opposite.
So given that, it's not a route I'm taking. I've actually finished 80% of this driver now - the last bit being a dithering algorithm i need to work out that takes advantage of 4 color grayscale rather than simply black and white.
Real programmers use butterflies
|
|
|
|
|
US tycoon McAfee found dead in Spanish prison[^]
I suspect he was just trying to uninstall himself ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
And yet he managed to avoid the Virus
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
Another sad story of someone who had it all, did lots of drugs, lost their mind, committed crimes, suicided.
|
|
|
|
|
Indeed - sad though someone killing themselves 
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
|
|
|
|
|
With every spark of genius comes a touch of madness.
The less you need, the more you have.
Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?
JaxCoder.com
|
|
|
|
|
Gosh - I feel like a lightening bolt.
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
