Minimal desc for all tweaks in INI to aid in locate/setting

[j_c_hallgren]

Some tweaks in the INI are not described on the "; Tweak" line and this can make locating the desired one slightly more difficult, since the actual line doesn't show in WordPad after a "Find" as shown on screen prints below.
In addition, even a few words can make it much clearer what the tweak on the next line is for and what value(s) it may have...so could these be added as time permits, even one or two at a time?

This isn't as good:

SS - 05-26-10 @ 01-31-47001.jpg

Preferred is this:

SS - 05-26-10 @ 01-32-47001.jpg

[admin]

There are even some tweaks without the "Tweak:"! As time permits...

[j_c_hallgren]

There are even some tweaks without the "Tweak:"!

Say what?

As time permits...

That's all I asked for...maybe just at least 1 per day? Or 2 if possible...

[zer0]

JC,

Things like these can be done by power users who have the knowledge of undocumented tweaks. By the same token, many options in "Configuration" don't have info tips -- those can be user-generated too. The only question is -- what channels can be utilised to provide such content to Don and how often can he integrate it into XYplorer?

[j_c_hallgren]

Things like these can be done by power users who have the knowledge of undocumented tweaks.

Not really...because we can't add a desc to INI file that is distributed to all users whereas Don can do so quite easily, I believe.

And my issue only related to the INI tweaks that only have "; Tweak" as I showed via screen prints which makes locating them more difficult.

[zer0]

Things like these can be done by power users who have the knowledge of undocumented tweaks.

Not really...because we can't add a desc to INI file that is distributed to all users whereas Don can do so quite easily, I believe.

Not entirely true. An INI can be hosted in a file/source code repository -- like Google Code -- where select few can checkout, make amends and commit. And everyone can have read rights to checkout/read and make changes to their local INI. It is probably easier for Don to do it, but this way he doesn't have to interrupt his 12-hours-a-day coding sessions

[Stefan]

But we could just collect here this tweaks incl. proposals for description, so Don just can check out and copy them.

[j_c_hallgren]

But we could just collect here this tweaks incl. proposals for description, so Don just can check out and copy them.

True...though I'd suspect that using a (separate from the existing INI tweak) page on the wiki might be better for some collaborative editing since we just first need to identify/list the actual tweak line and its associated description line.

[SkyFrontier]

...to anyone who stumble upon this query or those wanting to in fact DO such a thing.
Earlier this year I've started such a thing and did a very good job, considering my limited knowledge on the vast XYuniverse - there's not only documented stuff but also such "invisible functions" and hidden tricks. All handcrafted out of History.txt, forums and XYwiki and included in "New User's Reference Guide". Inside, there's

Code: Select all

xyPlorer_NewUsersGuide_pt1:
ReversedChanges.txt
Scripting.txt

xyPlorer_NewUsersGuide_pt2:
CoolFeats_SeeAlsoHTMs.txt
GeneralChanges_Jokes_Other.txt
InstallPacks.txt
3D_Style.txt
Tweaks.txt
MainFeatures.txt
Tricks_Hidden_UndocFeats.txt
Lics.txt
EnvironmentVars.txt

zer0:

Things like these can be done by power users who have the knowledge of undocumented tweaks.

So if you guys still want to contribute regarding that matter, check that stuff, PM me or directly post such treasure at the "New User's Reference Guide". As soon as my raw compilation gets a more polished, professional look (XY power-users revision, for instance), we could port that into XYwiki, too, why not?

[SkyFrontier]

Due to what was discussed in this thread, I also consider that "New User's..." is probably misleading - it can and must be split into "New" and "Power" users sections. Will think about it and act accordingly when I find the time for it.