>How about merge folder.ini into super_wdx.ini, something like
Probably so it will be made. At present we with Dmitry Vorotilin (the so-developer of a plugin) did not come yet to a final conclusion as it is necessary to make support of an custom views.
Storage of the information on folders in one ini-file will complicate a little and will slow down work of a plug-in so we should find the optimum decision. If someone has opinions in this occasion - suggest it.
Question about super_wdx plugin
Moderators: white, Hacker, petermad, Stefan2
How to use 4-10 columns?
I saw your words:
'Additional columns in plugin shows automatically, if you set some of this column in SSettings program. '
I've tried it with this
[mp3]
ContentString1=%Album@anytag.wdx%
ContentString2=%Artist@anytag.wdx%
ContentString3=%Title@anytag.wdx%
ContentString4=%Track@anytag.wdx%
First 3 columns work fine. But there's no 4th column show up.
Actually I'm interested in "shows automaticaly". With some file types, extra columns shows up. For other file types, they don't show. Does it suppose to work like this?
But I wonder how it could work. Custom column is defined in TC itself, you can add only no more than 3 columns. Where should 4-10 columns be?
I saw your words:
'Additional columns in plugin shows automatically, if you set some of this column in SSettings program. '
I've tried it with this
[mp3]
ContentString1=%Album@anytag.wdx%
ContentString2=%Artist@anytag.wdx%
ContentString3=%Title@anytag.wdx%
ContentString4=%Track@anytag.wdx%
First 3 columns work fine. But there's no 4th column show up.
Actually I'm interested in "shows automaticaly". With some file types, extra columns shows up. For other file types, they don't show. Does it suppose to work like this?
But I wonder how it could work. Custom column is defined in TC itself, you can add only no more than 3 columns. Where should 4-10 columns be?
SUPER_WDX 2.0 prebeta 1 released.
Can seems, that changes cosmetic, and it only completion of the previous release, but it not absolutely so. We with Genius have done the big work, and we hope, that you will like our work.
Unfortunately, we had to change structure of a ini-file, and also to make some changes to lng-files.
As it is usual, we wait for your offers and bugreports.
Can seems, that changes cosmetic, and it only completion of the previous release, but it not absolutely so. We with Genius have done the big work, and we hope, that you will like our work.
Unfortunately, we had to change structure of a ini-file, and also to make some changes to lng-files.
As it is usual, we wait for your offers and bugreports.
"Database only" seems don't work.
Custom folders view settings are supposed to be saved in dirdata.zip, right? But after finish setting, I can't find it anywhere, and it doesn't work.
Or did I missing something?
Another problem:
With
DelayMode=2
then
<DIR>=%Directory Count (on demand)@DirSizeCalc.wdx% %File Count (on demand)@DirSizeCalc.wdx%
All fields become on demand too, don't show up untill I press space key on the file.
If with DelayMode=0 or 1, those on demoand fields show up automatically.
It would be better 'usual' fields will show up as usual. Only 'on demond' fields reponse to space key.
Custom folders view settings are supposed to be saved in dirdata.zip, right? But after finish setting, I can't find it anywhere, and it doesn't work.
Or did I missing something?
Another problem:
With
DelayMode=2
then
<DIR>=%Directory Count (on demand)@DirSizeCalc.wdx% %File Count (on demand)@DirSizeCalc.wdx%
All fields become on demand too, don't show up untill I press space key on the file.
If with DelayMode=0 or 1, those on demoand fields show up automatically.
It would be better 'usual' fields will show up as usual. Only 'on demond' fields reponse to space key.
2Raymond:
).
Thanks for response.
Existence of dirdata.zip checked at program each start, and if it is not present SSettings recreate this file. The file must be in the same folder, where plugin. Check, whether there are at you rights of files create in this folder."Database only" seems don't work.
Custom folders view settings are supposed to be saved in dirdata.zip, right? But after finish setting, I can't find it anywhere, and it doesn't work.
Or did I missing something?
Hmmm... You right, all plugin fields work as it setted in SSettings. But I'm not confident, whether it is necessary to change it... I shall check a source code, and I shall choose the optimum decision (optimum - in my humble opinionIt would be better 'usual' fields will show up as usual. Only 'on demond' fields reponse to space key.
).Thanks for response.
dirdata.zip is right in the super_wdx plugin folder.D1P wrote:Existence of dirdata.zip checked at program each start, and if it is not present SSettings recreate this file. The file must be in the same folder, where plugin. Check, whether there are at you rights of files create in this folder.
No matter what I set for custom folders view, its size is always 22b, unchangedly.
IMHO, it's necessary.But I'm not confident, whether it is necessary to change it...
While other fields show up quickly, Directory Count and File Count are more time-consuming, especially for large size folders. I guess that's why the author of DirSizeCalc plugin made them optoinal on demond.
I wish keep this feature when use them in super_wdx.
1. Setup any catalog with mode "Database only"No matter what I set for custom folders view, its size is always 22b, unchangedly.
2. Close SSettings.
3. Enter to dirdata.zip in TC. Any files in archive?
4. If yes, and plugin again not worked, then please send me your super_wdx.ini (mail:no_spam[at]students[dot]ru). If no - also send me you ini-file.
Okay, okay, okay...IMHO, it's necessary.
I do this if it is possible I have received your mail, and now I can give answers to you questions.
First: All fields will be caused how it is adjusted in super_wdx, in independence of own filelds type (that is how it works now). Sorry, but this technical restriction, and I do not know as it to bypass. Probably, I shall think up something... But while I do not know.
Second: I have check your debug logs, and, apparently, I see, where a error causes. Soon I shall correct it.
Thanx.
First: All fields will be caused how it is adjusted in super_wdx, in independence of own filelds type (that is how it works now). Sorry, but this technical restriction, and I do not know as it to bypass. Probably, I shall think up something... But while I do not know.
Second: I have check your debug logs, and, apparently, I see, where a error causes. Soon I shall correct it.
Thanx.
One more question:
Is it possible to mix "on demand"-values and "delayed"- / "as usual"-values in one Super-column?
Example:
I have defined a Super-column "Merkmale" (="attributes" / "characteristics"). It shows some common attributes for files. Length for audio files, dimensions for graphics etc. Now I'd like to see the number of subdirectories and the number of files for "<Dir>"-entries, provided by Lefteous' plugin <DirSizeCalc.wdx> (fields "Directory count (on demand)" and "File count (on demand)"). I'd like to see these information "on demand", while all other values should be extracted "as usual" or "delayed", respectively.
Data request mode can be defined for all Super-columns only, right?
AFAIR, it isn't possible for a "normal" content plugin to mix on-demand- and in-background-fields in one column. <Super_wdx> is a "meta" content plugin, maybe <Super_wdx> can manage mixed data request modes in one column?
Thanks in advance for any useful hint
- van Dusen
Is it possible to mix "on demand"-values and "delayed"- / "as usual"-values in one Super-column?
Example:
I have defined a Super-column "Merkmale" (="attributes" / "characteristics"). It shows some common attributes for files. Length for audio files, dimensions for graphics etc. Now I'd like to see the number of subdirectories and the number of files for "<Dir>"-entries, provided by Lefteous' plugin <DirSizeCalc.wdx> (fields "Directory count (on demand)" and "File count (on demand)"). I'd like to see these information "on demand", while all other values should be extracted "as usual" or "delayed", respectively.
Data request mode can be defined for all Super-columns only, right?
AFAIR, it isn't possible for a "normal" content plugin to mix on-demand- and in-background-fields in one column. <Super_wdx> is a "meta" content plugin, maybe <Super_wdx> can manage mixed data request modes in one column?
Thanks in advance for any useful hint
- van Dusen