Column profiles simply do not work anymore for me (build 832)
Column profiles simply do not work anymore for me (build 832)
Hello,
I'm experiencing a weird thing : just applying the fc_default_view (to reset to default columns) doesn't work anymore when I've simply added manually an extra column (say "Folders")
The added column simply remains.
The rest of column profiles et auto-select views obviously do not work better.
Just to make sure, I suppressed the [FcDetailedViews*] sections from FreeCommander.ini and deleted FreeCommander.views.ini file.
They rebuild OK on the next run but the behavior remains (if I add an extra column, choosing fc_default_view won't bring me the default columns set)
Am I the only one to experience that ?
(I'm using FreeCommander XE 2020 Build 832 64-bit donor upon Windows 10.0.18363)
Thanks
K.
I'm experiencing a weird thing : just applying the fc_default_view (to reset to default columns) doesn't work anymore when I've simply added manually an extra column (say "Folders")
The added column simply remains.
The rest of column profiles et auto-select views obviously do not work better.
Just to make sure, I suppressed the [FcDetailedViews*] sections from FreeCommander.ini and deleted FreeCommander.views.ini file.
They rebuild OK on the next run but the behavior remains (if I add an extra column, choosing fc_default_view won't bring me the default columns set)
Am I the only one to experience that ?
(I'm using FreeCommander XE 2020 Build 832 64-bit donor upon Windows 10.0.18363)
Thanks
K.
Re: Column profiles simply do not work anymore for me (build 832)
It is not clear for me what does not work?
If possible, send me your settings and describe more exactly your problem.
If possible, send me your settings and describe more exactly your problem.
Re: Column profiles simply do not work anymore for me (build 832)
Hello Marek,
Thanks for your time.
My explanation remains the same.
I just reset all custom views to get back to initial default FC configuration.
Then I add DOS-Name column (one I never use) :
From then on, select View > Column_profiles > fc_default_view won't change anything (although that column does not belong to my default as you will see in my config files)
I expect DOS-Name column (among others) to be replaced by fc_default_view columns right ?
Besides, I wonder what are all thosesections in my .ini file (?) could they interfer ?
Thanks
K.
Thanks for your time.
My explanation remains the same.
I just reset all custom views to get back to initial default FC configuration.
Then I add DOS-Name column (one I never use) :
From then on, select View > Column_profiles > fc_default_view won't change anything (although that column does not belong to my default as you will see in my config files)
I expect DOS-Name column (among others) to be replaced by fc_default_view columns right ?
Besides, I wonder what are all those
Code: Select all
[FcDetailedViews_{<UUID>}]
Thanks
K.
Re: Column profiles simply do not work anymore for me (build 832)
+ .ini files
- Attachments
-
- FreeCommander.views.ini
- (377 Bytes) Downloaded 524 times
-
- FreeCommander.ini
- (52.23 KiB) Downloaded 523 times
-
- FreeCommander.fc_default_view_excerpt.ini
- (1.94 KiB) Downloaded 535 times
Re: Column profiles simply do not work anymore for me (build 832)
If you add some new column - the column is added to the active profile.
In your example it is "fc_default_view" profile.
If you now click on "View > Column_profiles > fc_default_view" no change is to see because you have selected exactly the same profile as currently loaded ( you have changed fc_default_view).
If you want to remove some columns from fc_default_view (e.g. DOS-Name) you can make it with Shift+F1 and "Add/remove columns".
In your example it is "fc_default_view" profile.
If you now click on "View > Column_profiles > fc_default_view" no change is to see because you have selected exactly the same profile as currently loaded ( you have changed fc_default_view).
If you want to remove some columns from fc_default_view (e.g. DOS-Name) you can make it with Shift+F1 and "Add/remove columns".
Re: Column profiles simply do not work anymore for me (build 832)
Hello Marek,
I did not know about altering the active profile indeed so I may have been misreasoning.
I still encounter problems using auto profiles and views (<sub>, <mask>, <plain> conditions)
In order to elaborate cases, can you tell me whether there's a way to effectively know the active profile ?
(haven't found it in status bar options ; any log where I could find which profile has ultimately been activated according to rules ?)
Thanks.
K.
I did not know about altering the active profile indeed so I may have been misreasoning.
I still encounter problems using auto profiles and views (<sub>, <mask>, <plain> conditions)
In order to elaborate cases, can you tell me whether there's a way to effectively know the active profile ?
(haven't found it in status bar options ; any log where I could find which profile has ultimately been activated according to rules ?)
Thanks.
K.
Re: Column profiles simply do not work anymore for me (build 832)
Currently you can identify the currently used profile from the used columns.
Re: Column profiles simply do not work anymore for me (build 832)
OK.
Maybe I should put a feature request on it (active profile status)
...on concurrent rules/conditions, infering from the final set of used columns preclude the very concept of a possible bug :-]
But I'll work on isolating a case from an empty conf.
Thanks for your time.
K.
Maybe I should put a feature request on it (active profile status)
...on concurrent rules/conditions, infering from the final set of used columns preclude the very concept of a possible bug :-]
But I'll work on isolating a case from an empty conf.
Thanks for your time.
K.
Re: Column profiles simply do not work anymore for me (build 832)
Sorry for the hold I left here.
I couldn't find any evidence of dysfunction (nice ! )
Thanks for the clarification about active column profile alteration behavior.
K.
I couldn't find any evidence of dysfunction (nice ! )
Thanks for the clarification about active column profile alteration behavior.
K.
Re: Column profiles simply do not work anymore for me (build 832)
Hi Marek,
> as of build 834 -> Implemented: New placeholder for using in the status bar: [fc_columnProfile] - name of the used column profile
That was quite fast, and useful, thanks.
I still encounter shortcomings with column profiles auto-selection but it's related to the auto selectable views -> column profile cascade (switch mode automatically on folder change being checked) ; I'll elaborate a specific case.
Meanwhile, it would also be useful to include a [fc_viewName] text pattern placeholder in custom status bar in order to trace what actual ultimate automatic view was selected through the set of rules.
Many thanks (I dare thinking Humanity hasn't ever encountered such a sophisticated file manager as FreeCommander, ain't that a thrill ? )
K.
> as of build 834 -> Implemented: New placeholder for using in the status bar: [fc_columnProfile] - name of the used column profile
That was quite fast, and useful, thanks.
I still encounter shortcomings with column profiles auto-selection but it's related to the auto selectable views -> column profile cascade (switch mode automatically on folder change being checked) ; I'll elaborate a specific case.
Meanwhile, it would also be useful to include a [fc_viewName] text pattern placeholder in custom status bar in order to trace what actual ultimate automatic view was selected through the set of rules.
Many thanks (I dare thinking Humanity hasn't ever encountered such a sophisticated file manager as FreeCommander, ain't that a thrill ? )
K.
Re: Column profiles simply do not work anymore for me (build 832)
Hi Marek,
I've spotted a few intricate problems within that (precious) functionality, specifically with "Switch view mode automatically on folder change" option.
Case setup :
2 dummy files (1 flac, 1 mp3) in 2 different subdirs : I've defined a profile that works perfectly by itself when subdir containts "FLAC" or "MP3" substring : (prf_FLACMP3 has the peculiarity to show "Album" column)
...and I also have defined auto selectable views based on subdir content : (to be continued, it seems I can't attach more than 3 images event if they are very small (?))
I've spotted a few intricate problems within that (precious) functionality, specifically with "Switch view mode automatically on folder change" option.
Case setup :
2 dummy files (1 flac, 1 mp3) in 2 different subdirs : I've defined a profile that works perfectly by itself when subdir containts "FLAC" or "MP3" substring : (prf_FLACMP3 has the peculiarity to show "Album" column)
...and I also have defined auto selectable views based on subdir content : (to be continued, it seems I can't attach more than 3 images event if they are very small (?))
841 / NOK / Switch view mode automatically on folder change
Now (Case Scenario) :
When "Switch view mode automatically on folder change" is checked out,
entering MP3 subdir works fine because folder name is "MP3" : When "Switch view mode automatically on folder change" is checked (activated),
entering ContainsLossless subdir works fine because folder contains mostly (only) .flac files (one) :
But oddly enough when I get back to MP3 subdir, then fc_default_view is activated : ...like if having both auto-view and column profile applicable would clash in some way ?
I here attach my FreeCommander.views.ini
Thanks !
When "Switch view mode automatically on folder change" is checked out,
entering MP3 subdir works fine because folder name is "MP3" : When "Switch view mode automatically on folder change" is checked (activated),
entering ContainsLossless subdir works fine because folder contains mostly (only) .flac files (one) :
But oddly enough when I get back to MP3 subdir, then fc_default_view is activated : ...like if having both auto-view and column profile applicable would clash in some way ?
I here attach my FreeCommander.views.ini
Thanks !
841 / Auto-views bug in column profile drop-down selector
Another weird one...
I define target column profile for <plain> condition : ...then for "mostly" .flac : ...then for "mostly" .mp3 : (to be continued...)
I define target column profile for <plain> condition : ...then for "mostly" .flac : ...then for "mostly" .mp3 : (to be continued...)
841 / Auto-views bug in column profile drop-down selector (cont'd)
...but if I get back to vw_Plain and again directly to vw_mostlyMP3 :
prf_Plain appears (visually) to be associated with vw_mostlyMP3 (!)
I here attach my FreeCommander.views.ini file.
Thanks
prf_Plain appears (visually) to be associated with vw_mostlyMP3 (!)
I here attach my FreeCommander.views.ini file.
Thanks
- Attachments
-
- 841_FreeCommander.views.ini
- (1.37 KiB) Downloaded 414 times
Re: Column profiles simply do not work anymore for me (build 832)
A final word around these cases :
- why are those two tabs separated ? (cols profiles and auto-views)
wouldn't be as simple to extend cols profiles (already auto-selectable) with the few more options available in auto-views (content conditions) ?
- it would be nice for those cols profiles to be defined (defineable) in Favorites (as an alternative to "View") because one knows in general pretty well what he/she is expecting to find in each favorite bookmarked folder.
Thanks (stick to it !
- why are those two tabs separated ? (cols profiles and auto-views)
wouldn't be as simple to extend cols profiles (already auto-selectable) with the few more options available in auto-views (content conditions) ?
- it would be nice for those cols profiles to be defined (defineable) in Favorites (as an alternative to "View") because one knows in general pretty well what he/she is expecting to find in each favorite bookmarked folder.
Thanks (stick to it !
Who is online
Users browsing this forum: No registered users and 100 guests