Hi,
> Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> > Hi,
> > why is first framebuffer (or X) blanked while using second? I shoul use
> > some switch to prevent this? Or vt from which the process is started is
> > always blanked?
>
> I guess the blanking is caused by the switch to a new vt that is
> allocated by DirectFB. You may try the "--no-vt-switch" option,
> but another problem will be the usage of input devices. I don't
Yes, it's true. Question to the developeres: could DirectFB open the new vt
on _propriate_ framebuffer?
Means if I tell Directfb to use second framebuffer it should also use
console on second framebuffer.
At this time even if I have my console on second fb and using directf from
application started here it still blanks primary fb.
JS
--
Info: To unsubscribe send a mail to [EMAIL PROTECTED] with
"unsubscribe directfb-dev" as subject.
