Closed
Bug 773999
Opened 13 years ago
Closed 13 years ago
Switch windows shell service to nsIWindowsRegKey
Categories
(SeaMonkey :: OS Integration, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: neil, Assigned: neil)
References
Details
Attachments
(1 file, 1 obsolete file)
This also allows us to port two new background constants from Firefox.
Assignee | ||
Comment 1•13 years ago
|
||
Assignee: nobody → neil
Status: NEW → ASSIGNED
Attachment #642281 -
Flags: review?(iann_bugzilla)
Attachment #642281 -
Flags: review?(bugzilla)
Comment on attachment 642281 [details] [diff] [review]
Proposed patch
On code inspection / comparison:
>+ int style = 0;
>+ switch (aPosition) {
>+ case BACKGROUND_TILE:
>+ style = 1;
In the Firefox code both BACKGROUND_TILE and BACKGROUND_CENTER have style = 0. Looking at http://code.msdn.microsoft.com/windowsdesktop/CSSetDesktopWallpaper-2107409c the valid values are 0, 2, 6 and 10. I guess, at the moment, the registry ignores the first bit but we probably shouldn't rely on this undocumented (potentially depreciated - information from 8-10 years ago does mention 1) behaviour.
>+ if (aPosition != BACKGROUND_TILE)
>+ value.Assign('0');
Depending on the resolution to the first point, this might have to change.
r=me with that addressed.
Attachment #642281 -
Flags: review?(iann_bugzilla) → review+
Assignee | ||
Comment 3•13 years ago
|
||
You're right, I totally overlooked that. (Perhaps I need to switch vim to a colour scheme with more contrast; I already have trouble reading comments in the default dark blue...)
f? is because IanN can't actually test this, so additional verification would be great. (Tweak the BACKGROUND_ setting in nsContextMenu.js if you want to give the patch a serious workout.)
Attachment #642281 -
Attachment is obsolete: true
Attachment #642281 -
Flags: review?(bugzilla)
Attachment #642363 -
Flags: review?(iann_bugzilla)
Attachment #642363 -
Flags: feedback?(philip.chee)
Attachment #642363 -
Flags: feedback?(ewong)
Comment on attachment 642363 [details] [diff] [review]
Fixed patch
r=me assuming the feedback is good
Attachment #642363 -
Flags: review?(iann_bugzilla) → review+
![]() |
||
Comment 5•13 years ago
|
||
Comment on attachment 642363 [details] [diff] [review]
Fixed patch
Runs well with no hiccups that I've noticed on my Vista build.
Attachment #642363 -
Flags: feedback?(ewong) → feedback+
![]() |
||
Comment 6•13 years ago
|
||
> neil@parkwaycc.co.uk 2012-07-15 16:39:05 PDT
> Blocks: 774130nsIWindowsRegKey
Surely Gnome doesn't use nsIWindowsRegKey?
No longer blocks: 774130
![]() |
||
Comment 8•13 years ago
|
||
Comment on attachment 642363 [details] [diff] [review]
Fixed patch
Tested on Windows 7. Also tested various options FILL, TILE, FIT.
> - nsAutoString path;
> + nsString path;
Just curious, why this change?
(I also notice that Firefox shell service is using the external string API).
Attachment #642363 -
Flags: feedback?(philip.chee) → feedback+
Assignee | ||
Comment 9•13 years ago
|
||
(In reply to Philip Chee from comment #8)
> > - nsAutoString path;
> > + nsString path;
> Just curious, why this change?
a) nsAutoString is just a typedef in the external API anyway.
b) The string never gets extended, which is where an nsAutoString shines
(an nsString often needs to be reallocated before it can be extended.)
Assignee | ||
Comment 10•13 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•