>> You might try to make some of those that have an analogue work in
>> Wine, especially the "Legacy Control Panel Commands" "desktop" and
>> "color".
>
> That's something I can look into, indeed.
Having had a brief look into it, currently the control panel attempts to
launch the appropriate .cpl
> Wine's builtin control does just launch the shell's version of the
> control panel, unless it's given an argument like "DESKTOP",
> "DATE/TIME", etc. See programs/control.c.
Indeed, I'm aware of that. Effectively, there are two versions of the
control panel in the shell of course, the namespac
> I'll look into that, then. I know that the shell namespace control panel
> does check the registry for entries (could you try using a program like the
> ReactOS Explorer to browse the control panel and see if it shows up there?),
> but I'm not sure if the standalone control.exe does. Ideally, the
Hi Reece,
> I just tested Cepstral SwiftTalker with latest git (see bug:
> http://bugs.winehq.org/show_bug.cgi?id=12534) and I can't see the
> options from the `control` program. You might want to get this and
> other applets displaying/working before creating default Wine-specific
> ones (e.g. li
Owen Rudge <[EMAIL PROTECTED]> writes:
> I personally believe this control panel applet (which also adds icons
> for the Registry Editor and Task Manager, two other key utilities, which
> would be useful to have easy access for) is a useful stepping-stone, as
> it were.
The control panel is no
2008/7/2 Owen Rudge <[EMAIL PROTECTED]>:
> Well, the first part of the project was to get the shell namespace
> implementation of Control Panel working properly, which is now
> effectively complete.
Hi,
I just tested Cepstral SwiftTalker with latest git (see bug:
http://bugs.winehq.org/show_bug.c
> I still don't see the need for a winecfg cpl applet at this point.
> You say that the Wine Configuration icon is ok for the time being.
> Take your time and design it correctly the first time, so you or
> others don't have to go back and fix it later. Measure twice, cut
> once, as they say.
On Tue, Jul 1, 2008 at 6:15 PM, Owen Rudge <[EMAIL PROTECTED]> wrote:
> > First, that's not what I was suggesting. I was disagreeing with
> > adding a winecfg cpl applet. Second, I'm likening winecfg to a very
> > poorly-designed control panel. There are several categories that can
> > go into
> First, that's not what I was suggesting. I was disagreeing with
> adding a winecfg cpl applet. Second, I'm likening winecfg to a very
> poorly-designed control panel. There are several categories that can
> go into their own cpl applet, like 'Sound' and 'Graphics' (or whatever
> you want to
On Tue, Jul 1, 2008 at 6:05 PM, Rob Thornton <[EMAIL PROTECTED]> wrote:
> Owen Rudge wrote:
>> > As we said before, implementing a control panel applet doesn't mean
>> > you have to do anything to the current winecfg code.
>>
>> True, but would it really benefit to add an icon for each winecfg ta
On Tue, Jul 1, 2008 at 5:47 PM, Owen Rudge <[EMAIL PROTECTED]> wrote:
> > As we said before, implementing a control panel applet doesn't mean
> > you have to do anything to the current winecfg code.
>
> True, but would it really benefit to add an icon for each winecfg tab
> (which I think is what
Owen Rudge wrote:
> > As we said before, implementing a control panel applet doesn't mean
> > you have to do anything to the current winecfg code.
>
> True, but would it really benefit to add an icon for each winecfg tab
> (which I think is what you are suggesting, yes?) to the control panel,
>
> As we said before, implementing a control panel applet doesn't mean
> you have to do anything to the current winecfg code.
True, but would it really benefit to add an icon for each winecfg tab
(which I think is what you are suggesting, yes?) to the control panel,
compared to having one gener
On Tue, Jul 1, 2008 at 4:22 PM, Owen Rudge <[EMAIL PROTECTED]> wrote:
>> Isn't it more logical (and closer to native) to have a control panel
>> applet for each category/tab already in winecfg instead of having one
>> winecfg applet? Otherwise you're just moving winecfg to another
>> place.
>
> We
> Isn't it more logical (and closer to native) to have a control panel
> applet for each category/tab already in winecfg instead of having one
> winecfg applet? Otherwise you're just moving winecfg to another
> place.
Well, my plan, as mentioned before in another thread, is to split up winecfg
a
On Tue, Jul 1, 2008 at 2:17 PM, Owen Rudge <[EMAIL PROTECTED]> wrote:
> This patch adds a new applet, winecfg.cpl, to Wine, based on a patch sent a
> few months ago by Metody Stefanov (pure_evil @ mail.bg). The control panel
> features three icons, for Wine Configuration, the Registry Editor, and t
16 matches
Mail list logo
