Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Developing U++ » U++ Developers corner » Is Rainbow/FrameBuffer/XXXXFB broken?
Re: Is Rainbow/FrameBuffer/XXXXFB broken? [message #43984 is a reply to message #43983] Sun, 07 December 2014 11:02 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14260
Registered: November 2005
Ultimate Member
Mindtraveller wrote on Sun, 07 December 2014 01:54
Recently I've made an attempt to look Rainbows-based and WinFB examples, but they failed to compile.
reference/UWord_FB seems to be broken too.
Is it some kind of upgrade going on? Or framebuffer-based stuff is completely broken in latest revisions?

By the way, I consider making framebuffer-like front-end for e-ink displays. It's 4 bits per pixel and needs manual updates of display. How do you think, will it be possible to implement it without changing any of Ctrl or any other U++ internals?
Thanks.


Yes, it might be broken now. There were changes in CtrlCore; so far I have only fixed "canonical" backends. But should be easy to fix (might do it soon).

e-ink: definitely possible. But I would say that due to manual updates, your GUI will have to be changed a bit anyway....

In any case, I would probably start by thinking about some screen buffer (with all pixels) in application and some mechanism how to put that data to e-ink.

4-bits is not a problem at all, just make convert RGBA to monochorome... (maybe you might want some dithering too).
 
Read Message
Read Message
Read Message
Previous Topic: uld with MingW-w64
Next Topic: Udp class (UdpClient/UdpServer)
Goto Forum:
  


Current Time: Mon Jun 02 20:12:48 CEST 2025

Total time taken to generate the page: 0.03010 seconds