On first thought, I would assume that JAVA has no means of
'reinitialising' the graphics when DirectFB is done.
Not sure how to proceed.
A possible approach would be to tailor your DFB app to a fixed
resolution (the one that JAVA initialises to), and remove set-up ioctls
from the fbdev.c driver in DirectFB, assuming you are not using hardware
acceleration. This also means same number of FB buffers, probably 1 if
your JAVA FB driver is simple.
Greets
Niels
Homam Dabis wrote:
Hi,
I have an unusual situation.
My main application is a JAVA app. using awt graphics. Additionally, I
have a C app using directfb.
The task I have is to integrate the main JAVA app. with the C app. I
can do this by loading the C app. as a .so from JAVA and use JNI to
call it.
Problem:
JAVA app starts graphics. Upon calling the DFB app., a DFB instance is
created and that runs fine. However, when I exit the DFB app. and go
back to JAVA, I lose all graphics. The JAVA app. is still alive and I
can reload and run the DFB app. in the same session but blindly i.e. I
just use the same RC key to start and exit the DFB app.
I guess DFB is getting hold of the FB and that is messing up the JAVA
FB control.
Does anyone have any suggestions/ideas on how to solve such a problem?
Thanks
Homam.
------------------------------------------------------------------------
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
