Help - Search - Members - Calendar
Full Version: Skin Editor Bugs
Desktop Sidebar Forums > Desktop Sidebar > Bugs/Issues
stuffedtiger79
I have used the skin editor a lot lately and here is a list of bugs i found so far.

1: .install bug in dspackages (see here)
2: doesnt work with skin names that contain and underscrore (_)
3: when you add or remove an attribute, the list scrolls up to the top (i think this is already fixed?)
4: doesnt support clock hand skinning
5: adds rightmargin, topmargin, bottommargin and leftmargin with a lowercase m. the correct format is an uppercase M. the lowecase m doesnt work.
6: tilebitmap doesnt work. it does the same as stretch bitmap. i reported this bug months ago, when i was trying to tile bitmaps using the xml file. it didnt work then, it doesnt work now. please fix this.
7: cant add new skin elements. the list of elements in the left is fixed. however, if i add new elements, like a hover or undock appearence to anything using the xml file, it shows up in the list and then i can edit it. id like to add it directly using the skin editor.
8: why does the skin editor save the skin files in the local directory? why not in the main program files directory. this way, all instances will have access to the skin. now, only the specific instance can use the skin.
9: cannot launch skin editor to edit a file without changing the DS to have the same skin. when i open Options and Appearence and chose the skin i want to edit and click edit, it opens up the editor, but also sets the DS to that skin. I dont want the two to be coupled.
10: no direct link to skin editor from start menu (already reported elsewhere)

ill keep this list updated as i find more bugs. hope the next version has all this fixed. i really enjoy skinning, but sometimes its frustrating to use the editor.
Alpaca
11. doesn't support adding/updating credits.
wues
Thank you for the list of bugs! I hope you won't be disappointed with the new version, which should be available soon. Comments for specific problems below (if a problem is not listed below, it means that the comment is "will be done" or "already fixed"):

2: doesnt work with skin names that contain and underscrore (_)

what do you mean? I have checked it just now and did not see any problem.

4: doesnt support clock hand skinning

what do you mean?

5: adds rightmargin, topmargin, bottommargin and leftmargin with a lowercase m. the correct format is an uppercase M. the lowecase m doesnt work.

In fact both forms are used in various skins. The real bug is that attribute names are case-sensitive, while should be case-insensitive. The form with capital M will be used.

8: why does the skin editor save the skin files in the local directory? why not in the main program files directory. this way, all instances will have access to the skin. now, only the specific instance can use the skin.

The idea is to keep in Program Files only what is normally installed, and to keep other things - e.g. new or modified skins - in the local directory. But if it is really big problem to you, we can negotiate smile.gif.

11. doesn't support adding/updating credits.

What do you mean? The "author" entry is supported - you have to select the skin name in the tree.
wues
4: doesnt support clock hand skinning

I have overlooked the thread where it was explained, so now I understand. The skin editor will support clock hand attributes in the next release.
Alpaca
QUOTE (wues @ Jul 23 2004, 10:05 AM)
11. doesn't support adding/updating credits.

What do you mean? The "author" entry is supported - you have to select the skin name in the tree.

Gosh! You are right! I better take off the eye mask next time I criticise the skin editor. ph34r.gif
GoMa
wues, I think that the Skin Editor should generate install.xml file instead of $SKINNAME.install files. This will eliminate two installation formats, and leave only a common one for both skins and plugins (also lots of skins already use the install.xml files). Also regarding the "$SKINS\$PACKAGE" path, I think it's better to replace $PACKAGE with the actual skin XML name. It will then install succesfully also when the DSPACKAGE file is renamed.
wues
GoMa, I will discuss it with kdam, since for the .dspackage contents I simply did what he told me to do smile.gif.
acommonjo
QUOTE (wues @ Jul 23 2004, 04:30 PM)
GoMa, I will discuss it with kdam, since for the .dspackage contents I simply did what he told me to do smile.gif.

At one point we were having a lot of trouble with the installation of Skins using the DSPACKAGEs which was one of the main reasons I think kdam starting creating the .install installation method. Since he started I figured out that it was a problem with the Forum server renaming the filenames to cause install problems with the $PACKAGE variable and skins that had spaces in the filename and he decided not to convert everything. This is all how I understood it. I could be wrong.

~acommonjo
yyy
The skin editor can't seem to find all of my installed skins - it shows only the ones that cam with the install, I think. I'm using b 85 - it didn't happen in previous builds, AFAI remember.
root
I also have several problems with the skin editor. I think it gets confused as to where the skin is, under Programs or under documents and settings.
I installed a new skin and when I went to edit it, the editor poped up and said it could not load it and loaded another skin. I found if I went to Docs and settings and copied the skin from there to the DS folder under Programs it would then see it.

I tried with install for all users and for me alone. Makes no difference. I make changes to the settings for the performance panel and the settings will just not change. I was able to replace a clock face though.

Last, the one feature I so wanted was to be able to use an image for the backgrounds in the performance panel and when I saw that is now possible, I was very happy indeed. Sadly, it doesn't work though.

I do think that the skins should reside in one directory only instead of two as is happening now. I think therein lies the problem.

Keep up the good work. I love playing with this program.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.