Closed Bug 204219 Opened 23 years ago Closed 23 years ago

Investigate nsWidget::SetCursor

Categories

(Core Graveyard :: GFX: Gtk, defect)

Product:
Core Graveyard
Component:
GFX: Gtk
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: janv, Assigned: blizzard)

Details

From bug 189719: Any idea when nsWidget::SetCursor is called? If ever, could you file a bug on making it have the same functionality as nsWindow::SetCursor?
nsWidget is the parent class for all of the various widgets in the widget/ code. Since the only widget that we use right now is nsWindow, there's no reason to implement it. Just leave it be. :)
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
The problem is that these two methods are out of sync. nsWindow:SetCursor seems to be more recent.
How are they out of sync?
e.g. nsWidget:SetCursor doesn't support custom icons loaded from static data
My point was that nsWidget::SetCursor is never used - only nsWindow::SetCursor does and that can load cursors from static data.
I see, but why don't we get rid of that additional code in nsWidget:SetCursor ?
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.