I find some bug of the es1.1

This topic contains 11 replies, has 2 voices, and was last updated by  CarlosSarria 8 years, 8 months ago.

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #29614

    favormm
    Member

    I have downloaded the SDK for PC Emulation  Windows XP -OpenGL ES 1.1.

    In the TrainingCourse folder, I use the third code — 03_IntroducingPVRShell, I add a WM_LBUTTONDOWN message in the code, want to pop-up a common dialog of thes windows, and like following:

    case WM_LBUTTONDOWN:
      {
       OPENFILENAME ofn;
       char szFile[255];
         
       ZeroMemory(&ofn, sizeof(OPENFILENAME));
       //ofn.Flags = OFN_ALLOWMULTISELECT | OFN_EXPLORER | OFN_FILEMUSTEXIST | OFN_PATHMUSTEXIST;
       ofn.Flags = OFN_SHOWHELP | OFN_OVERWRITEPROMPT;
       ofn.lpstrFile = szFile;
       ofn.lpstrFile[0] = ‘’;
       ofn.nMaxFile = sizeof(szFile);
       ofn.lpstrFileTitle = NULL;
       ofn.lpstrFilter = “All*.*Text*.txtImage*.bmp”;
       ofn.lStructSize = sizeof(OPENFILENAME);
       ofn.hwndOwner = hWnd;
       GetOpenFileName(&ofn);
       return 0;
      }

     

     

    the issue come out: the first I click the left of my mouse, my father window’s graphics will disappear, It will not appear again until I close the pop-up dialog.

    It only have the issue when I first click the mouse,  the later all the things are ok.

     

    I want to know if  I do is ok? If not , please  give me some suggestions.
    #32412

    favormm
    Member

    supplement:

        In the same condition with OpenGL 1.5 on Windows,  have no issue.
    #32413

    Hello,

     

    I have tested this and it works fine for me.

    You should add your code in the PVRShellOS.cpp file. Do a searck for WM_LBUTTONDOWN. Once you have found where it is used in the WinProc callback function, just paste your code on it.

     

    Regards.

     

    Carlos.
    #32414

    favormm
    Member

    Ths,

    I done like you said, but it is the same result with my issue.

    When the first click mouse,I know the common dialog pop-up succeed, the 3D scene’s color is white, and have nothing, in fact there is a yellow triangle in the middle.

      I capture a picture,  you can see it is white

     

    Then the second click mouse, all the things are ok, the triangle display,the color is ok.

    As a contrast,  I capture a picture .

     

    I want to know ,why the first is error?

     
    #32415

    favormm
    Member

    sorry for that ,  maybe you can’t see the picture, so I give you the web address

    picture 2:

    #32417

    Hello,
    This problem only happens on WinXP or Vista with ‘classic desktop’. This is due to these styles not keeping the content of the parent window in a buffer (which is done properly on the new Vista styles). I do not know why this works fine on your OpenGL application. There might be differences when you create your windows and manage the ‘OpenFile’ dialog.
    This is just a Windows issue and we do not think it is related to our emulation library.

    Best regards.

    Carlos.

     
    #32418

    favormm
    Member

    hi,

    Thank you answer,

     

       In the OpenGL application, I use the wgl library, and have no error.  the only difference between my OpenGL application and OpenGL ES application is that Opengl use the wgl and the ES use the egl,  I don’t think it is windows issue, It is only my opinion.

     

    Regards
    #32419

    Hello,
    This is a very strange issue because there should not be much  difference between wgl or egl… I will file this issue as a bug and an engineer will have a look at it as soon as possible.

    Best regards.

    Carlos.

     
    #32420

    favormm
    Member

    This problem only happen when first pop-up the common dialog,  the dialog that created by myself and create by the API of MessageBox()  is ok,  but the second pop-up the common dialog is ok.

    If the first pop-up dialog is a non-common dialog, then pop-up the common dialog, all the things are ok.
    #32421

    Many thanks for the extra details.

     

    Carlos.
    #32422

    Hello,

    We looked at this issue but we have not been able to replicate it. We added to our tracking system as BRN26956 but we are closing this bug.

    Best regards.

    Carlos.

Viewing 12 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic.