Registry plugin: Bugs

[Nigurrath]

Yes I do,
i never had any problems till now, no conflicts and easier handling for me.

[Dalai]

Easier handling if you don't know which file belongs to what plugin? I certainly don't believe that! It's pure luck that you didn't have any conflicts (at least as far as you know since not every conflict is directly visible). I'm certain that if you had more plugins there would have been conflicts for sure. You do know that you can create directories in TC, don't you?

Regards
Dalai, still stunned

[petermad]

You dump all your plugins to a common folder??

Yes I do,

Amazing - I just did a search for duplicates in my 112 plugin folders - I have 645 duplicate filenames - of these 316 are *.lng files. Imagine those in one folder!

2Nigurrath
Do you have a small number of plugins?

[krasusczak]

in my 112 plugin folders - I have 645 duplicate filenames - of these 316 are *.lng files.

you just kill me lol ^^

[karapuz79]

Uploaded new version:

v 5.1 - 21.07.2012
- Fixed: 32-bit plugin was not working properly with Wow6432Node key in WinXP x64 when accessing x64 registry
- Fixed: Main TC window was not captured properly in TC 8.01 and sometimes plugin dialogs were not working
- Added: Icon substitution - *.ico files with predefined names are loaded from plugin folder before falling back to icons from resources.
File names are (w/o extension) - Main, String, StringSpecial, DWORD, Binary, BinarySpecial, Add, Connect, Disconnect, Host, Key, Search.
Main icon cannot be changed, file "Main.ico" changes search window icon.
- Added: Hungarian translation
- Changed: Danish column translation

[petermad]

2karapuz79

There is still a problem with using the Registry.lng - the string "date" is not translated - it shows writedate when I want to set up the custom columns for the plugin.

Already mentioned here: http://ghisler.ch/board/viewtopic.php?p=252385#252385

[Dalai]

Thanks for the new version!

- Fixed: 32-bit plugin was not working properly with Wow6432Node key in WinXP x64 when accessing x64 registry

Confirm the fix.

There is still a problem with using the Registry.lng - the string "date" is not translated - it shows writedate when I want to set up the custom columns for the plugin.

I can confirm the problem.

Regards
Dalai

[krasusczak]

Hi

There is still problem with "Go to key"
When you search main TC window going to for ex. "c:\" not "\\\Reg\HKEY_LOCAL_MACHINE\SOFTWARE\*"

Problem persist on:
Win7 x86, TC 8
Win7 x86, TC 8.01rc4
Win2k, TC 8
xp x86, TC 8

xp x86, TC 7.57a works fine :/

[karapuz79]

2krasusczak

Take a look at registry_vk.ini:

; Plugin name (you must change this when you rename the plugin in TC)
Name=Registry

[krasusczak]

ok, now works thanks:)

[Bluestar]

2karapuz79:

A little glitch in the pluginst.inf (regarding Hungarian language & it's accented letters), caused by the difference between the character coding of the actual "pluginst.inf" (Unicode) and my previous "pluginst.inf" file (ANSI) with the Hungarian line in it.

I fixed the problem, you can download the fixed Unicode Hungarian translation of "pluginst.inf" from: http://bluesoft.hu/software/others/registry_wfx_500_hungarian_pluginstfix.zip

[jvh]

2karapuz79

There is still a problem with using the Registry.lng - the string "date" is not translated - it shows writedate when I want to set up the custom columns for the plugin.
Already mentioned here: http://ghisler.ch/board/viewtopic.php?p=252385#252385

Only small addition to petermad's post:
- string "date" shows in Customs columns [=tc.writedate]
- string "writedate" should show e.g. [=<fs>.writedate.D.M.Y hs] but actually there is no output (no data in file window - empty field only)

Note: It is possible to translate "writedate" string, just add new line to Registry.lng with "writedate=<your translation>".

[petermad]

Note: It is possible to translate "writedate" string, just add new line to Registry.lng with "writedate=<your translation>".

As already mentioned here: http://ghisler.ch/board/viewtopic.php?p=252385#252385

[karapuz79]

To tell the truth, I do not get all this anxiety about "date" vs "writedate".

Let's consider 2 options for German language and "Default" plugin column set.

Option 1: date=Datum2
I do see "Datum2" in the custom column name (after TC restart). So to me it looks like a perfectly valid behaviour.

Option 2: writedate=Datum2
I see "Date" instead of "Datum2" in the custom column name (after TC restart). Which is clearly wrong.

Why do you insist on "writedate"?

[petermad]

Option 1: date=Datum2
I do see "Datum2" in the custom column name (after TC restart). So to me it looks like a perfectly valid behaviour.

No, that is not what I get. Here is what I see when using the default registry.lng file: http://madsenworld.dk/tcmd/writedate.png

Clearly the line in registry.lng:
[deu]
date=Datum

is not used! - and that is the same for the other languages.

This is what I see when I try to set the custom fields manually - not what I see when the plugin uses its default custom columns, as you are referring to.

If I delete my [CustomFields_Registry] section in wincmd.ini and restart TC, you are right - then the string for date in registry.lng is used, but if I want to manually make the column for writedate, then the string is not used, as you can see from my screenshot.