https://app.box.com/s/0wyy94qs6mtaatds5r9v
The two bugs in the above export are probably connected, since they happened pretty much simultaneously:
1: Changing normal widget background actually changed the image for selected and focused as well. This doesn’t happen every time, but I’ve seen it more than once. The last time it happened,
2: Panel (dock) disappeared from view, though not from the item hierarchy, after #1: occurred.
Panel shows up in the desktop item hierarchy, and the item menu is accessible still. After “move out of panel” is clicked, the shortcut lands in the upper left corner of the desktop, the way its supposed to.
EDIT: 2014MAR23 18:05 PDT
The llx export linked above is derived from +Chris Chastain’s TopTab apk. (I had an idea, wasn’t sure I knew exactly how to do it from scratch, so, like any good programmer, I stole something :-). He still has the apk shared at https://app.box.com/s/oxgtxnpa79tax96snpsx.
It uses a dock-like row of 5 pinned shortcuts with top to bottom and bottom to top stop scroll, stop drag, barrier stop points. I unpinned the shortcuts, put them into a panel, leaving the stop points in place surrounding the panel, so that I could slide the dock items to the left and right, so that the dock is no longer limited to the 5 in the original. I was able to use the dock this way off and on for days, Beyond the addition of shortcuts, there were absolutely no changes made to the dock panel.
Then I changed the background of the little clock widget at the top of the screen. The background change didn’t work right (#1:) and immediately afterward, the dock, which had been happily bouncing up and down at the bottom of the screen until then, disappeared from view.
D5 Creation
< ![CDATA[
Next time you can also use my ‘find items’ script. I made it so, if the item is pinned outside the screen, you will see it.
]]>
< ![CDATA[
One thing that could explain the background to be set for normal, selected and focused is the switch to “non expert” mode. In this mode, setting a color or an image affects all three states at once.
]]>
< ![CDATA[
Pierre Hébert that’s a good thought. But expert mode was most definitely unquestionably (not a solitary doubt about it 🙂 checked. Whether or not it was actually activated may be another story but the error was definitely with the app, not the user. If expert mode had not been checked, then it would have been impossible to have a different background for the three different states . In fact I was able to use this feature the way I always do. I don’t like my phone to vibrate or make obnoxious clicking noises, so I always set it up, wherever possible , to provide visual feedback. If it does it again I will forward whatever info I can to you.
(BTW did I mention that I had checked expert mode? 😛 )
]]>
< ![CDATA[
I am surprised you had to check this option yourself, there is a hard-coded check inside the app: if(user == Carolyn Boyle) { expert_mode = true; }
Joking appart, I will check what is wrong 😉
]]>
< ![CDATA[
Ok, now I understand for the color: when the selection effect is set to holo, normal and selected colors are shared (visually, not internally). As of today the selection effect can only be overridden for apps, shortcuts, folders so it cannot be changed for widget, but this is something I can change
]]>
< ![CDATA[
Pierre Hébert I don’t think I’ve gotten that update yet. Mine still says:
… )
while (true)
{ everything = foobar}
;-P
]]>
< ![CDATA[
Pierre Hébert You could have just said RTFM, but then I would have said WTFM and that wouldn’t being very productive… 😉
Seriously, I freely admit that I’m a little buggy too, but there’s also something weird in the software.
Which takes me back to the reason I posted these two issues together as one bug report.
I made a change to the widget at the top of the screen, and the dock at the of the screen abruptly disappeared from view.
SCOPE seems to be screwy somewhere . A local change to a single item somehow had a more global effect.
Thanks to the item hierarchy menu, (absolutely my favorite new feature XD) I had no problem locating the dock after I could no longer see it.
And Chris sledge’s suggestion of looking at the “honor pinned items in edit mode” setting was helpful in restoring the dock.
But why was it necessary to restore the dock? I hadn’t done anything to it. It fled from view all on its own X-P
]]>