On 12.07.2007 18:29, Stefan Dösinger wrote: > I am not sure if it is a good idea to wrap the winecfg functionality into > something complex like a control panel applet(which is tied to shell folders > in some way). A user can easilly break core parts of wine with winecfg. The > more complex the requirements for winecfg are the more likely it is that a > user can't get back into winecfg to undo a bad option.
Control Panel applets are just DLLs... You could provide an alternative way to launch the wine configuration in case something is too borked, like an entry point for RunDll32, or turn winecfg into a simple launcher for the configuration applet. -f.r.
