|
Á¦ ¸ñ |
[RE][RE][RE]ȸéÀÌ ÀÌ»óÇÏ°Ô º¸¿©¿ä! |
|
ÀÛ¼ºÀÚ |
¹æÈ¿µ¿ |
ÀÛ¼ºÀÏ |
2004-03-05 |
Á¶È¸¼ö |
1391 ȸ |
|
÷ºÎÆÄÀÏ |
÷ºÎµÈ ÆÄÀϾøÀ½.
|
|
ilog¿¡¼ ¿Â ´äº¯ÀÔ´Ï´Ù.
The problem you described happens because of having reached the limits of the Windows GDI resources for a single application. The 32 panels you opened caused each container to allocate a bitmap for double buffering, and this bitmap consumed memory from the Windows GDI area.
By increasing the number of panels and due to their accumulated dimensions, the GDI resources were exhausted, so further drawing was not done correctly after that circumstance. Views uses bitmaps not allocated in the GDI memory space in some cases -to allow managing big bitmaps for example when read from files by the bitmap streamers-, but for the double buffering thing they still rely on the GDI resources which are limited.
We have taken this as a limitation. The problem is due to the limitation imposed by the Windows GDI resources capabilities in terms of memory space for the bitmaps used to draw the screen, hence the error message you can see about double buffering.
|
|
|
|