On Thu 6.Nov'08 at 17:40:42 +0100, Gilbert wrote:
> Also, I have one 'gripe' about wmaker that bothers me, but I'm probably not a
> good enough
> coder to come up with a fix on my own. When right clicking on a un-docked
> DockApp and
> choosing 'Kill', the pop-window that follows thats says:
> 'Kill Application' shows the window class instead of the window
> name: 'DockApp will be forcibly closed' instead of:
> 'YawmPPP will be forcibly closed' (for example).
>
> This is not noticable with all DockApps because many, or most of them have
> the same
> window 'class' as window 'name'. For me, though, this happens with all my
> DockApps becuase
> i have them all patched to use 'DockApp' as the class, instead of using the
> same string as
> for the window 'name', if they are not already that way. In other words, some
> DockApps already
> have the class set to DockApp. the diference seems to be related to the
> libdockapp API -this
> was changed and the library was incorporated into Wutils libs.
>
> I deliberately patch the DockApps this way because I run wmaker with both the
> Dock
> and Clip disabled. I also disable all mini-windows and application and shared
> icons.
> This means that I get a completely clean desktop and only DockApps get shown
> when they
> are running (undocked). When started, they run with the icon in the location
> specified
> in the options. The key thing here, is that only DockApps which have their
> window 'class'
> set to 'DockApp' will show up. Those (many) DockApps which have the class set
> to the
> window 'name' will not display at all on the screen.
>
> I have no problem patching nearly any DockApp to change the class to DockApp,
> but the
> undelying behaviour of wmaker which doesn't show the name of the app in the
> kill panel is bothersome.
Have you tried to modify src/dock.c and src/appicon.c and change icon->wm_class
to
icon->command in this part of the code?
buffer = wstrconcat(icon->wm_class,
_(" will be forcibly closed.\n"
"Any unsaved changes will be lost.\n"
"Please confirm."));
I haven't tested this because this is non-issue for me, but I think it will
write
the 'command' you used to start the application. If you start them by invoking
only their name (with no options and not specifying the whole path) then this
give you more or less what you want, I think.
--
To unsubscribe, send mail to [EMAIL PROTECTED]
