Skip to main content
panduvittala
Inspiring
March 3, 2014
Answered

plugin panel with qt GUI turns white while moving panel on windows

  • March 3, 2014
  • 1 reply
  • 3400 views

The subject says it all. My plugin has a panel rendered by qt (using qwinwidget). When I try to move the panel by dragging using mouse, the qt UI part turns completely white. It goes back to normal when the mouse is released. This  happens only on windows - mac works fine. Has anybody faced this issue? How to fix this? Thanks in advance.

Qt: 485

Illustrator: CC

OS: Windows 7 64 bit

This topic has been closed for replies.
Correct answer A. Patterson

Thank you so much.


You can find the sample here. I built it using the upcoming CC SDK but I think it should be okay for compiling on the older CC. If you need to run this on CS6 you may need to tweak a few things, but I think most of the Empty Panel sample code is the same CS6+.

You'll need to have QTDIR defined before opening Studio for this to work. It also uses an environment variable called ILLUSTRATOR that points to the root of the Illustrator folder, but only for debugging.

http://file-post.net/en/fs5/data/1402427655_2834312253_72/?id=Og6sjxBLISjU

Note that this download expires in 3 days. I built the code and got the white-while-dragging bug. Then I dropped in my windows message proc function and it went away, so that should be a good example of the fix.

1 reply

panduvittala
Inspiring
April 1, 2014

Help please! I am stuck

Known Participant
April 1, 2014

Post the code and any info relevant info for us to understand the big picture before attempting to guess the problem.

Qt and Ai Plugin solution is very complicated, we all faced many problems and if you don't describle visually and accurately it is hard to help you solve it.

A. Patterson
Inspiring
June 2, 2014

Help please!


I remember we used to have this problem and I had to look up how we handled it. In a nutshell, you need to fill in a missing message propagation by drawing the widget yourself.

Qt isn't processing WM_PRINT or WM_PRINTCLIENT properly (though if its AI's fault for not passing along the message or Qt's fault I don't actually know). We attached a Windows Message proc to the result of AIPanelSuite::GetPlatformWindow() (invoked on the panel), and inside you need something that handles those messages like this:

LRESULT CALLBACK WindowMessageProc(HWND window, UINT message, WPARAM wParam, LPARAM lParam)

{

     switch (message) {

          // .. other messages to handle

          case WM_PRINTCLIENT:

               if (!(PRF_CLIENT & lParam)) {

                    break;

               }

          case WM_PRINT:

               {

                    // I wrote this off the top of my head, so you will need to fill in some bits, most notably widget_inside_panel

                    // We put this inside a class that we attached to the widget and made sure it contained a QWidget* that pointed to the widget inside the panel

                    // Also note that this code is doing zero error checking; you should really be checking the results of GetObject(), SelectDCObject(), etc.

                    QPixmap widgetPixmap = QPixmap::grabWidget(widget_inside_panel);

                    HBITMAP bitmap = widgetPixmap.toWinHTBITMAP();

                    HDC dc = 0;

                    HGDIOBJ oldObject = 0;

                    CreateDC(dc);

                    SelectDCObject(dc, bitmap, oldObject);

                    DIBSECTION dibSection;

                    GetObjectW(widgetBitmap, sizeof(dibSection), &dibSection);

                    BitBlt(reinterpret_cast<HDC>(wParam, 0, 0, dibSection.dsBmih.biWidget, dibSection.dsBmih.biHeight, dc, 0, 0, SRCCOPY);

                    if (oldObject) {

                         SelectObject(oldObject);

                    }

                    DeleteDC(dc);

                    DeleteObject(widgetBitmap);

               }

               break;

     }
}

This is useful method to have to work around other bugs, like if you have trouble with mouse wheel (we had several problems with that) or focus bugs.