Opened 15 years ago
Closed 5 years ago
#35 closed task (wontfix)
Finish QColormap
| Reported by: | Dmitry A. Kuminov | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | Qt Enhanced |
| Component: | QtGui | Version: | 4.5.1 Beta 1 |
| Severity: | low | Keywords: | |
| Cc: |
Description
Provide the OS/2 version of the QPaintDevice and QColormap classes.
Change History (5)
comment:1 Changed 15 years ago by
| Milestone: | QtGui Beta → Qt GA |
|---|
comment:2 Changed 15 years ago by
| Milestone: | Qt GA → Qt Enhanced |
|---|
The platform-dependent part QPaintDevice is actually very slim and doesn't need any porting in case of OS/2. On Win32, they add the getDC() and releaseDC() methods to QPaintDevice similar to getPS() and releasePS we provide for QWidget on OS/2. If other derivants of QPaintDevice besides QWisget will need this functionality too I'll move these methods to QPaintDevice as well.
Therefore, it's just QColormap. Basically, this class is about setting up the palette for 256 color modes. Not really relevant for modern hardware, therefore, I'm moving it outside the GA milestone.
comment:3 Changed 14 years ago by
| Severity: | → low |
|---|---|
| Summary: | Port QPaintDevice and QColormap → Finish QColormap |
Just for clarity, this task is narrowed down to implementing HPAL QColormap::hPal() method that will create a HPAL object that will be a GPI representation of the QColormap, and then using this HPAL object when creating presentation spaces (basically, for the needs of QPixmap) and when realizing the palette in response to the WM_REALIZEPALETTE message. Not really important unless we got a user with a 256 color display which is not satisfied with the current Qt4 behavior.
comment:4 Changed 14 years ago by
| Priority: | major → minor |
|---|
comment:5 Changed 5 years ago by
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
If we face that on Qt5 again we might consider it. So if needed open a ticket at https://github.com/bitwiseworks/qtbase-os2
No time (not too important).