Menus from windows are not skinned such as:
Right click on icons, folders in explorer, File|Edit menus in any application.
Should these be skinned or does it not work on this level?
Kind of throws off the aesthetics of a skin to see some bland gray menu poppin up all the time.
Speaking of gray, I don't recall my menus being gray before installing litestep. Has litestep made changes? If so what's the original color for xp?
To find your quicklaunch folder bring up your litestep menu, select quicklaunch, right click and select properties. Look for your "location."
If you had done your homework you'd know that LiteStep has nothing to do with Windows skinning. But yes, some LS themes does change the system colors. What distro are you using?
Litestep 0.24.7 RC 3
I believe I installed LS on an old machine a long time ago, ever since then menu's have been resetting themselves to dark grey. I'm sure LS is not the culprit since I have uninstalled from that machine long ago.
I knew LS has nothing to do with windows skinning, I just questioned if it went as far as the menu since mine had changed, hence my peaked intrest in posing a question.
Anywhoo, I've been trying to edit the quicklaunch and according to MANY posts about this, I've come to the conclusion that it should be in my users folder. However I searched my entire hardrives only to come up with "quicklaunch" references in litestep folders. That which are uneditable. Any ideas?
Thanks for the reply.
There is/was a module called SysColors (or something) that could change you windows colors.
Austerity did this.
But if you uninstalled LS and it still changes, it must be something else. (Duh :D)
"That which are uneditable."
What does that mean?
That which are uneditable... sounds Lovecraftean.
I figured it couldn't be lightstep from the recycle bin, lol.
Uneditable as in LiteStep\themes\austerity\config\quicklaunch_icons.rc "Access Denied."
Which I'm sure isn't the file I need to edit anyway, the only others are:
quicklaunch_bot.ini
quicklaunch_top.ini
quicklaunch.png
quicklaunch_actual.png
quicklaunch_icons.png
That's all that's on my comp.
West: Dictionary.com -> Horror novelest?
Litestep my already be operating in the ethereal, lol. j/k
;------------------------------------------------------------------------------
; personal settings: syscolor
;------------------------------------------------------------------------------
;--> Some themes use syscolor.dll to automatically set system colours.
; If you do not want themes to automatically change your system colours,
; uncomment the following line.
SCNoChange
If SCNoChange is commented, uncomment it. This should be a fix, but if it doesn't work 100% of the time, lsnothing will.
psyfect: associate .rc files with a text editor. Newer revisions of Windows 2000 and XP cause that access error with the default settings.
Cerbie, after changing association:
Windows cannot access the specified path, you may not have permission...
Litestep -> edit config -> personal config
I assume syscolor should be there?
I guess my main question has now become editing the quicklaunch...it's not in the specified area other threads suggest to turn to.
Edit: I'm thinking I may be missing files or something. The only syscolor's I have is the dll and a folder with a txt and html file. Still no quicklaunch files found. I downloaded and installed (edit)Omar's(edit) LS, then updated to RC3, shouldn't I be fine?
Dunno about the popup. I mean, it sdhould work (I'm not on a LS-enabled PC right now :)), but open personal\personal.rc in notepad or another text editor.
The exact (aside from a ";") set of text is in personal.rc.
I guess the file association did not completly register with my system. Did an open with and uncommented SCNoChange. Thanks alot for the tip.
You said if it doesn't work 100% lsnothing will. Typo?
Found the quicklaunch folder! Check my first post for how I did if anyone is interested. I have no idea why windows search didn't find it or why I never saw an internet explorer folder under microsoft earlier.
Thanks for all the replies.
No, lsnothing is a module that does...nothing. Pandora, FI, will still set system colors for me, ansd this has been an issue over several Win2k installs. So, I deleted syscolor-2.3.dll, got lsnothing, and renamed lsnothing's DLL to syscolor-2.3.dll. So, when something wants to load syscolor-2.3, it actually loads lsnothing, so syscolor's settings won't do anything.
Interesting. Sounds like it works.