On Fri, May 6, 2011 at 11:28 AM, Otavio Salvador wrote:
> On Fri, May 6, 2011 at 11:14, Marc-André Moreau
> wrote:
> ...
> > You must re-implement all the callbacks registered by libgdi within
> > dfb_win.c and provide a full GDI implementation using DirectFB. This is
> > unfortunately the only w
On Fri, May 6, 2011 at 11:14, Marc-André Moreau
wrote:
...
> You must re-implement all the callbacks registered by libgdi within
> dfb_win.c and provide a full GDI implementation using DirectFB. This is
> unfortunately the only way to benefit from those accelerated graphical
> operations through D
Hi Howard,
I have written dfbfreerdp along with libgdi mainly as a "proof of concept"
for libgdi in the first. libgdi, however, is not the ideal way of rendering
GDI for dfbfreerdp, I agree. It was, however, a good way of getting
something that renders correctly, which I was having a lot of troubl
On Fri, May 6, 2011 at 10:39, Howard Su wrote:
> I am reading your code change. But i do have a question about libgdi. In my
> case, I am using DFB in a ARM11 board. CPU is relative slow compare desktop
> machine. But Samsung offer a graphics card which supports some 2D function
> like BitBlt. Do
I am reading your code change. But i do have a question about libgdi. In my
case, I am using DFB in a ARM11 board. CPU is relative slow compare desktop
machine. But Samsung offer a graphics card which supports some 2D function
like BitBlt. Do you have any idea how we can support it in libgdi? We
de
