2Clo: Thanx, you french.lng also will be added to plugin arhive. I will increase rooms for the long strings.
Some info about new plugin version: Two additional columns added, and plugins fields several units support added.
Question about super_wdx plugin
Moderators: Hacker, petermad, Stefan2, white
Hello, D1P
After updating to V1.0 prebeta, I got some problems.
1. plugin can't read the second content field. for example
[jpg]
ContentString1=%Width@Images.wdx%x%Height@Images.wdx%x%BPP@Images.wdx%
It shows like 800x800x800, which is supposed to be 800x600x24. The second and third content value can't read.
2. When Usedef=1, "Replace empty field values to file name" option is always actually on, no matter you set EmptyReplace=0 or 1.
3. SUPER_COLUMN #1 now has 4 types: default, file, folder, reparse point. I can't tell the difference of them. Especially what does "reparse point" mean?
Now I return back to v0.9b, it works fine.
After updating to V1.0 prebeta, I got some problems.
1. plugin can't read the second content field. for example
[jpg]
ContentString1=%Width@Images.wdx%x%Height@Images.wdx%x%BPP@Images.wdx%
It shows like 800x800x800, which is supposed to be 800x600x24. The second and third content value can't read.
2. When Usedef=1, "Replace empty field values to file name" option is always actually on, no matter you set EmptyReplace=0 or 1.
3. SUPER_COLUMN #1 now has 4 types: default, file, folder, reparse point. I can't tell the difference of them. Especially what does "reparse point" mean?
Now I return back to v0.9b, it works fine.
-
winflowers
- Junior Member
- Posts: 12
- Joined: 2004-08-27, 07:52 UTC
I got the same problem.Raymond wrote:Hello, D1P
After updating to V1.0 prebeta, I got some problems.
1. plugin can't read the second content field. for example
[jpg]
ContentString1=%Width@Images.wdx%x%Height@Images.wdx%x%BPP@Images.wdx%
It shows like 800x800x800, which is supposed to be 800x600x24. The second and third content value can't read.
2. When Usedef=1, "Replace empty field values to file name" option is always actually on, no matter you set EmptyReplace=0 or 1.
3. SUPER_COLUMN #1 now has 4 types: default, file, folder, reparse point. I can't tell the difference of them. Especially what does "reparse point" mean?
Now I return back to v0.9b, it works fine.
Each super_column can only read the first content field correctly.
Ok, i try to fix this bug.1. plugin can't read the second content field. for example
[jpg]
ContentString1=%Width@Images.wdx%x%Height@Images.wdx%x%BPP@Images.wdx%
It shows like 800x800x800, which is supposed to be 800x600x24. The second and third content value can't read.
Yes, i forgot change constant value to variable. Now fixed.2. When Usedef=1, "Replace empty field values to file name" option is always actually on, no matter you set EmptyReplace=0 or 1.
Hmmm, i realy confused. I don't know whence these field takes, but also fixed this bug.3. SUPER_COLUMN #1 now has 4 types: default, file, folder, reparse point. I can't tell the difference of them. Especially what does "reparse point" mean?
It works fine here too. 
Thanks for your work this plugin is great!
I don't quite understand your answer. You mean you don't know the definition of these 4 types youself either? Confused...Hmmm, i realy confused. I don't know whence these field takes, but also fixed this bug.3. SUPER_COLUMN #1 now has 4 types: default, file, folder, reparse point. I can't tell the difference of them. Especially what does "reparse point" mean?
This feature has not added yet, right? Just in case you've already added it but I didn't set it up correctly.2Raymond: problem with demand fields isn`t resolved at this time. May be in next versions (i'll add you reuest to my todo list).
Thanks for your work this plugin is great!
Last edited by Raymond on 2005-03-03, 19:44 UTC, edited 1 time in total.
>You mean you don't know the definition of these 4 types youself either?
Yeah, I don't know :^). I don't implement these types, and i think that is my compiler bug (after I recompile plugin sources, these units dissapeared).
>This feature has not added yet, right?
Yeah again. Working with demand fields is very hard to me, and I don't know, how implement this feature. However, demand fields showed in fields list, because plugin lists all plugin fields.
In any case, I will try to add these features in next versions.
Yeah, I don't know :^). I don't implement these types, and i think that is my compiler bug (after I recompile plugin sources, these units dissapeared).
>This feature has not added yet, right?
Yeah again
. Working with demand fields is very hard to me, and I don't know, how implement this feature. However, demand fields showed in fields list, because plugin lists all plugin fields.In any case, I will try to add these features in next versions.
