Litestep Tracker - ISSUES

0000087: Add "About LiteStep" and "Switch to Explorer" options in recovery menu

I think it would be applicable to have an "About LiteStep..." entry in the recovery menu.

I think it would be benefitial to have "Switch to Explorer" entry in the recovery menu to help people restore their desktop. This should probably use the same code iplemented in the -explorer command line switch.

0000060: Open Containing Folder in Search does nothing

In explorers search results view, choosing "Open Containing Folder" from the context menu while running LS does nothing. Launching the file, and viewing the actual folder path works as it should.

0000040: Implement Vista changes to NOTIFYICONDATA

The NOTIFYICONDATA struct has a few new flags and a new member, hBalloonIcon. We're probably leaking the latter currently.

0000039: Shortcuts to 64-bit progams broken when running in WOW64

On 64-bit Windows there are both 32-bit and 64-bit binaries for some programs like IE, Media Player, or Calculator, in "Program Files (x86)" and "Program Files", respectively.
A 32-bit Litestep cannot currently invoke shortcuts to the 64-bit versions because ShellExecuteEx appears to read out FOLDERID_ProgramFiles from the .lnk, which resolves to "Program Files (x86)" for 32-bit processes. Thus the 32-bit versions are launched. Note that if only a 64-bit version exists it is launched all the same.

0000106: handling an additional case in trayservice for correct positioning of new vista+ trayicons

0000104: handling an additional case in trayservice for correct positioning of new vista+ trayicons

0000077: Folder Options cannot be opened from Control Panel

The control panel item "Folder Options" is broken when LiteStep is running. Clicking it has no effect.

0000109: Provide API access to the Wow64FsRedirection functions

There are times when modules need to read from files or the registry, and when they do, they need to temporarily disable file system redirection, if they are on a 64bit os.

While module developers could easily copy the LSDisableWow64FsRedirection and LSRevertWow64FsRedirection code from the core, it might be a good idea to provide API functions for them so that they don't accidentally call Wow64DisableWow64FsRedirection directly (since it wont work on all systems).

0000110: Unable to open folders on some systems with the current version os LSExecute/Ex

For some reason, when file system redirection is disabled, which it currently will be on all x64 systems, calling ShellExecute/Ex with a directory path results in nothing happening.

0000066: Changes to global environment variables have no effect

Changes to environment variables via sysdm.cpl don't propagate to LiteStep or its child processes.

0000108: ShDocVw.ShellWindows / CreateObject("Shell.Application").Windows does not work

It is not possible to retrieve the list of windows from the shell using

ShDocVw.ShellWindows or CreateObject("Shell.Application").Windows

http://msdn.microsoft.com/en-us/library/bb774094%28VS.85%29.aspx [^]

0000070: 64-Bit startup items are not run

On 64-Bit versions of Windows, some registry keys exist as separate 32-Bit and 64-Bit versions. Currently, LiteStep only parses those that are in the 32-Bit registry branch and consequently skips the 64-Bit keys.

0000061: The "Status" page for network connections doesn't work while using litestep.

Trying to open the "Status" page in Control Panel -> Network Connections doesn't do anything while running LS.

0000053: The "Find Target" button in shortcut properties doesn't work while using litestep.

The "Find Target..." button in shortcut properties doesn't work while using litestep.

0000107: handling additional case in trayservice allows correct positioning of vista+ icons

An unhandled case in trayservice is hit when the new icons ask for position info after, and independent from being clicked. Patch handles this case. More changes are needed in the various tray modules, but afaict, this change is needed in core.

Patch below, attaching it is failing. Is also here, in case the below gets mangled: http://www.sendspace.com/file/vqmoo3 [^]

0000103: Unable to select Microsoft Live Mesh Options

I can see the Microsoft Live Mesh icon in the notification area, but right-clicking on the icon does not bring up the menu. I have installed LiteStep and Live Mesh on three computers and I have the same problem on all three.

0000095: Add fullscreen app notification

A notification such as a LM_FULLSCREENAPP message should be added to let modules benefit from the core's fullscren app detection code.

0000101: WM_SETTINGCHANGE is not sent when the wallpaper slideshow changes wallpaper in Windows 7.

In Windows 7, desktop modules won't repaint their main windows automatically when the wallpaper changes. Something like this is required to avoid the old wallpaper staying.

case WM_SETTINGCHANGE:
{
if (wParam == SPI_SETDESKWALLPAPER)
{
RedrawWindow(hwnd, NULL, NULL, RDW_INVALIDATE | RDW_ERASE | RDW_UPDATENOW);
}
break;
}

However, if you use the integrated wallpaper slide show the wallpaper is changed without any WM_SETTINGCHANGE message being sent so the old wallpaper remains unless you recycle or reload the desktop module.

When explorer is running, it seems to send the WM_SETTINGCHANGE message with wParam SPI_SETDESKWALLPAPER twice after the wallpaper has been changed.

0000102: GetLSBitmapSize crashes when passed a NULL pointer

GetLSBitmapSize() takes two pointers as parameters, and if passed NULL, it will de-reference the NULL pointer and crash.

0000035: External DLLs cannot be placed in module directory

If a module links to a 3rd party DLL, that DLL needs to be placed in our application directory. This is incompatible with NLM, among other things.

0000089: litestep crashes on recursively included .rc files

The step.rc preprocessor "Include" statement allows recursively including files and thus crashes with a stack overflow

0000078: Balloon tip timeout value is not boundary-checked

The timeout value of balloon tips (in the tray in particular) has bounds - previous to Vista, balloons were shown at least 10 seconds and at most 30 seconds. See http://msdn.microsoft.com/en-us/library/bb773352(VS.85).aspx [^]

On Vista, the timeout is set to nine seconds. SPI_GETMESSAGEDURATION returns ERROR_NOT_IMPLEMENTED on Vista, but works on Windows 7, where it returns a value of five seconds (Beta 1).

LiteStep doesn't currently enforce any of this at all.

0000013: Logging, please!

Logging is very handy to diagnose various failures in LS. The ideal logging system would do some of the following :

- Disable message boxes of severity less than or equal to the current logging level. Top logging mode would disable all message boxes.
- Provide similar, more informative error information stemming from RC code issues (e.g. conditionals)
- Export the logging implementation for use by external modules.

0000097: XP user switching screen does not show number of tasks

When Explorer is used as the shell, the XP user switching screen (accessible with Win+L on some but not all configs) shows the number of programs running (actually the number of task windows). If LiteStep is used as the shell, the number of programs running is not shown (It just says "Logged on", which is the same thing it says if there are zero tasks running). If there are multiple users logged on simultaneously, then users who use Explorer have the number of programs running shown, while users who use LiteStep do not.

0000096: Improve Safe Mode behavior

As per jugg's suggestion in response to Bug 33:

In Safe Mode, LiteStep currently launches Explorer and exits silently. Instead, it could wait for the TaskbarCreated message and show a "dialog or balloon tip explaining that litestep will be restored at the next reboot, unless they uninstall Litestep from add/remove programs."