#9185 closed bug (duplicate)
BDirectWindow::SupportsWindowMode() doesn't check for hardware cursor support
Reported by: | jua | Owned by: | jackburton |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Kits/Game Kit | Version: | R1/alpha4.1 |
Keywords: | BDirectWindow hardware cursor | Cc: | rudolfc |
Blocked By: | #4356 | Blocking: | |
Platform: | All |
Description
According to the BeBook, windowed mode for BDirectWindow should only work when the graphics accelerant supports hardware cursors (see the documentation on BDirectWindow::SupportsWindowMode()).
SupportsWindowMode() is supposed to check for it, however, in Haiku it only looks for B_PARALLEL_ACCESS. Using a BDirectWindow without hardware cursor causes any drawing in it to even draw over the mouse cursor.
The attached patch adds B_HARDWARE_CURSOR to the check.
Attachments (1)
Change History (11)
by , 12 years ago
Attachment: | Add-hw-cursor-check-to-SupportsWindowMode.patch added |
---|
comment:1 by , 12 years ago
patch: | 0 → 1 |
---|
comment:2 by , 12 years ago
I just learned about this ticket: http://dev.haiku-os.org/ticket/4356
If #4356 is implemented, this patch is not necessary anymore, because then hardware cursor is not a requirement for BDirectWindow... (although then there is no cursor in it).
comment:3 by , 10 years ago
Applying this as is would essentially make windowed BDirectWindow unusable, since very few of our drivers support hardware cursors. We should probably fix that first.
comment:4 by , 10 years ago
patch: | 1 → 0 |
---|
comment:5 by , 9 years ago
Guys,
Let it please be noted that my drivers all have 100 procent correct working hardware cursors under beos version 5 and dano. Also, I have explicitly tested all these drivers in pan and scan modes to work correctly. (also this is very handy btw for testing hardware overlay's correct move_overlay routines, executed when overlay is in use and the hardware cursor is moving) in the drivers (since overlay is connected to CRTC's and don't care about virtual workspaces..)
These drivers are: Nvidia, matrox, neomagic and via. If its not working correctly, the problem lies somewhere else.
Bye!,
Rudolf.
comment:6 by , 9 years ago
Cc: | added |
---|
comment:7 by , 9 years ago
BTW,
For these driver's there is HTML doc in the respective kerneldriver source folders, alongside the settings files for these drivers (all same style).
Rudolf.
comment:8 by , 4 years ago
Milestone: | R1 → R1.1 |
---|
comment:9 by , 18 months ago
Blocked By: | 4356 added |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Marking as duplicate of 4356, whichever solution we settle on in the end, we don't need multiple tickets to track it.
comment:10 by , 15 months ago
Milestone: | R1.1 → Unscheduled |
---|
Add hw cursor checking