Support and General Use > Theming and Appearance Customization
Specific Clip Plus issue - Pixel Artefacts on Lock Screen
JdGordon:
I find it hard to believe that it doesnt.... are you sure you're running the same config?
KiwiCam:
Not really. The config.cfg file?
KiwiCam:
I'd like to throw in a few examples. Hopefully, the solution is something as simple as changing a setting:
I'm using my pULsE theme http://themes.rockbox.org/index.php?themeid=1428&target=sansaclipplus , so you can use that to check the Veiwport Areas.
Clip V2 - Before changing to Lock Screen:
Clip V2 - During Lock Screen:
Clip V2 - After Lock Screen - Note, NO artefacts at all (the overlapping characters are just the camera catching the text scrolling:
Clip PLUS - Before changing to Lock Screen:
Clip PLUS - During Lock Screen (Shows Artefacts):
Clip PLUS - After Lock Screen - Play Mode (Artefacts remaining):
Clip PLUS - After Lock Screen - Hold/Pause Mode - Some artefacts disappear:
Clip PLUS - Hold/Pause Mode - HOLD text changes to Clock - Note artefacts still remain, even though the Clock Viewport overlaps artefacts:
[Saint]:
I'm glad you posted these images...
What you described as "artefacts" gave me a /totally/ different idea of the problem in my mind.
This isn't what I would describe as being an artefact, that would be the correct term to use if there were items left from the previous screen still left onscreen after changing from one screen/state to another.
But the images you've posted suggest that these aren't actually any part of the previous screen at all...or if they are, they definitely (from what I can see with the example images at least) aren't in the same position as they were in the previous screen/state.
I now, officially, have "absolutely no frickin' idea" what's happening here ;)
The fact that its device specific (or seems to be) is also very curious...I would expect the same issues to be present on both devices were it to be a theme issue but I will admit I haven't actually looked at your code to see if there's something obviously wrong in there (being a themer myself I know the value of a second, fresh set of eyes to look at code). It can be rather easy to miss your own mistakes, sometimes repeatedly, especially if you're not aware that its a mistake ;)
In saying that, I shall have a look over this tonight if I get the time to...there's definitely *something* wrong here...
[Saint]
KiwiCam:
--- Quote from: [Saint] on October 22, 2011, 01:25:27 AM ---I'm glad you posted these images...
What you described as "artefacts" gave me a /totally/ different idea of the problem in my mind.
This isn't what I would describe as being an artefact, that would be the correct term to use if there were items left from the previous screen still left onscreen after changing from one screen/state to another.
But the images you've posted suggest that these aren't actually any part of the previous screen at all...or if they are, they definitely (from what I can see with the example images at least) aren't in the same position as they were in the previous screen/state.
I now, officially, have "absolutely no frickin' idea" what's happening here ;)
In saying that, I shall have a look over this tonight if I get the time to...there's definitely *something* wrong here...
[Saint]
--- End quote ---
8) I'm glad that I persevered.
--- Quote from: [Saint] on October 22, 2011, 01:25:27 AM ---
I haven't actually looked at your code to see if there's something obviously wrong in there (being a themer myself I know the value of a second, fresh set of eyes to look at code). It can be rather easy to miss your own mistakes, sometimes repeatedly, especially if you're not aware that its a mistake ;)
[Saint]
--- End quote ---
I'd like that a lot. I completely agree about the fresh set of eyes. That's really why I posted the My Themes thread. I look forward to it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version