Ismailtaktak / freemedforms

Automatically exported from code.google.com/p/freemedforms
Other
0 stars 0 forks source link

Calendar item drag item is drawn poorly under Linux #180

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
See attached screenshot. The pixmap that is attached via setPixmap() to the 
drag is drawn very badly, and sometimes really ugly.
The problem is, according to a www.stackoverflow.com question 
(http://stackoverflow.com/questions/7737913/qt-drag-and-drop-change-image-displa
y-while-dragging) the painting methods on Win/Mac/Linux are comepletely 
different:

Qt uses:

* a frameless windows which follow the mouse on X11. The pixmap is painted on 
the widget, and setGrabMouse is used to receive mouse events, since the widget 
is not directly under the mouse.
* the function SetCursor on Windows, with a copy of the pixmap where the 
cursors for each action has been painted in the corner.
* the function SetDragImageWithCGImage on Mac, but needs a DragRef object which 
is declared as an inaccessible local variable in qdnd_mac.mm.

So maybe you can confirm on mac/windows if this is also a problem?

Original issue reported on code.google.com by christian.a.reiter@gmail.com on 1 Oct 2012 at 4:40

Attachments:

GoogleCodeExporter commented 9 years ago
Oh, the problem seems to be in another point: I used the big png 
"global_resources/pixmap/splashscreens/newpatient-wizard.png" as drag pixmap 
and it had no drawing problems at all.
So I suggest that the problem lies in the render() function of the painter?

Original comment by christian.a.reiter@gmail.com on 1 Oct 2012 at 4:55

GoogleCodeExporter commented 9 years ago
all renders fine of the opacity is not set to 0.3 - the overlapping of the 
original widget below and the dragged pixmap seems to cause the drawing 
problems.
I'll deactivate the opacity reducing by now th workaround this problem.

Original comment by christian.a.reiter@gmail.com on 1 Oct 2012 at 5:07

GoogleCodeExporter commented 9 years ago
Ok, yes I'd noticed this bug and I can confirm that it is directly linked with 
the opacity priority.
Ok to remove the opacity.

Original comment by berenger...@gmail.com on 1 Oct 2012 at 5:35