Winecfg and users

Tlarhices · Post by **Tlarhices** » Mon May 12, 2008 8:56 pm

Winecfg contains potentially harmful configuration parameters (like native overrides) and are shown in the same way as useful configuration parameters like windows version or virtual desktop.
Maybe creating a box where a user can select it's level of knowledge in wine and hide part of the interface accordingly.

It could also be used to show warning informations when changing this level for the first time, for instance one saying to not link wine and a real windows installation when activating the folder tab or one explaining that overrides are "bad"

This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation.

(or putting par of winecfg in another command like winecfg-wineguru ^^)

austin987 · Post by **austin987** » Mon May 12, 2008 8:59 pm

On Mon, May 12, 2008 at 8:56 PM, Tlarhices <[email protected]> wrote:

It could also be used to show warning informations when changing this level for the first time, for instance one saying to not link wine and a real windows installation when activating the folder tab

We already do this.

This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation.

(or putting par of winecfg in another command like winecfg-wineguru ^^)

Patches are welcome.

Tlarhices · Post by **Tlarhices** » Mon May 12, 2008 9:14 pm

austin987 wrote:On Mon, May 12, 2008 at 8:56 PM, Tlarhices <[email protected]> wrote:
It could also be used to show warning informations when changing this level for the first time, for instance one saying to not link wine and a real windows installation when activating the folder tab
We already do this.

Strange, for me the only thing like this contains the serial number of the drives and there type. It's true that c: can't be changed this easily but nothing for native overrides.

austin987 wrote:
This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation.

(or putting par of winecfg in another command like winecfg-wineguru ^^)
Patches are welcome.

For patches, you have to know how to program in C or to try to make someone that can program in C aware of this.

austin987 · Post by **austin987** » Mon May 12, 2008 9:27 pm

On Mon, May 12, 2008 at 9:14 PM, Tlarhices <[email protected]> wrote:

Strange, for me the only thing like this contains the serial number of the drives and there type. It's true that c: can't be changed this easily but nothing for native overrides.

Native overrides don't break things as easily and are often necessary.

For patches, you have to know how to program in C or to try to make someone that can program in C aware of this.

Agreed. File a bug if you'd like, but most people spending their time
developing on wine have higher priority bugs to fix, i.e., one's
affecting real applications. If someone has an interest in fixing this
and the skills to do so, ask Alexandre if he'd accept such a patch.

vitamin · Post by **vitamin** » Mon May 12, 2008 10:08 pm

Tlarhices wrote:This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation.

If users don't get that they shouldn't be changing something they don't know - then they will learn the hardway. Nothing wrong about that. Only dumb people won't learn from their mistakes.

Tlarhices · Post by **Tlarhices** » Tue May 13, 2008 1:47 am

vitamin wrote:
Tlarhices wrote:This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation.
If users don't get that they shouldn't be changing something they don't know - then they will learn the hardway. Nothing wrong about that. Only dumb people won't learn from their mistakes.

But you will not even want to learn if you consider that it is a misconception of the system and not your own mistake and just go away.

Jim · Post by **Jim** » Tue May 13, 2008 2:44 am

austin987 wrote:Native overrides don't break things as easily and are often necessary.

Additionally for overrides that are really bad choices users will get a warning that reads: "Changing the load order of this library is not Recommended. Are you sure you want to do this?"

This is true for the following: advapi32, capi2032, dbghelp, ddraw, gdi32, glu32, icmp, iphlpapi, kernel32, mswsock, ntdll, opengl32, stdole2.tlb, stdole32.tlb, twain_32, unicows, user32, vdmdbg, w32skrnl, winealsa.drv, wineaudioio.drv, wined3d, winedos, wineesd.drv, winejack.drv, winejoystick.drv, winemp3.acm, winenas.drv, wineoss.drv, wineps, wineps.drv, winex11.drv, winmm, wintab32, wnaspi32, wow32, ws2_32, wsock32

Also, the above libraries do not appear in the drop down list.

Safe enough?