Folder Specific Settings Bugs

[jacky]

Ok...but I relate it to other situations, such as Notepad...I can take xxx.txt, open it in Notepad, rework the entire contents, and do a "Save As" yyy.txt, so yes, yyy.txt is a brand new file based on xxx.txt, but it did reflect how the current working copy of xxx looked at the moment it was saved...and...Notepad doesn't have a "Save as New" but uses the "Save As" variant as most do.

Only difference is: you do changes, then you "Save As" something new. Here we hit "Save As" to do the changes, that's why it's different to me I guess. I saw this command not as "saving as" but as "creating a new one".

Anyways, I'm sure Don will find the best solution out of this mess as he always does, and...

I want to really thank you for the chance to have this discussion!

Yep, I concur.

[peterbonge]

Oops, am I too late?

What about using "List" instead of "Folder"?
-> Specific List Views

Code: Select all

Enable Specific List Views
---
Save Current View
Edit...
Remove
---
Use Current View As Default

There is no "Save As" because I think we don't need 2 save entries. Why not just letting "Save Current View" act like "Save As"?

This is just a idea. "Folder View" is also OK.

[admin]

Oops, am I too late?

Yes!

[j_c_hallgren]

Oops, am I too late?

I suspect so based on Don's most recent posts...shoulda been here earlier today! Update: I see Don gave his answer above...

What about using "List" instead of "Folder"?

I think Don has already decided.

There is no "Save As" because I think we don't need 2 save entries. Why not just letting "Save Current View" act like "Save As"?

See my prior post. They serve three distinct purposes: To save any changes to the working copy but keeping same name -or- to save changes under a new name -or- to save changes as the default, so I don't see any way to reduce it.

[admin]

Code: Select all

---------------------------
The settings to be removed are likely to match other folders as well:

C:\Dokumente und Einstellungen\Donald\*

Do you want to remove them anyway?
---------------------------

The torture never stops!

At this point we definitely need some word for what I called "scheme" before. What about "definition"?

Code: Select all

The folder view definition to be removed is likely to match other folders as well: ...

Works?

[jacky]

Works?

I guess. I still feel just saying "The folder view to be removed..." would work too, I don't see the need to have another term, but that's me I guess. Anyways yes, "definition" works just fine I think.

[eurytos]

Code: Select all

---------------------------
The settings to be removed are likely to match other folders as well:

C:\Dokumente und Einstellungen\Donald\*

Do you want to remove them anyway?
---------------------------

The torture never stops!

At this point we definitely need some word for what I called "scheme" before. What about "definition"?

Code: Select all

The folder view definition to be removed is likely to match other folders as well: ...

Works?

How about:

Code: Select all

The folder Layout to be removed is likely to match other folders as well: ...

[Pagat]

uh, i'm also too late for the great term-discussion. i just want to add: i'd go for jackys proposal because i look at it the same way he does (Save as []... vs. Save [] as... discussion)...

[graham]

the bug I referenced (if that is the right word) before only happens with preview active

to reproduce consistently ....

I think this is a bug

Error 70 (00000046)
Desc Permission denied
Dll 0
Proc dumpFSS to: C:\Program Files\XYplorer\fss.dat

Source XYplorer
XY ver 7.40.0013
OS WinXP (Service Pack 3)
Date 07/08/2008 16:03:43

reproduced by

go to xy folder
select fss.dat with preview
X to close or minimise in my case
exit from system tray results in above report.

[j_c_hallgren]

Code: Select all

The folder view definition to be removed is likely to match other folders as well: ... 

Works?

I guess. I still feel just saying "The folder view to be removed..." would work too, I don't see the need to have another term, but that's me I guess. Anyways yes, "definition" works just fine I think.

I also could go along without another term here, but if we did have one, (as I wrote before) I'd highly suggest "Profile" instead of 'definition" (or scheme) as it fits/works (IMO) much better in this usage.

But the sentence in code leads me to ask: How is "likely to match" determined? Is that a constant for all times or not? Or should it be more vague, such as "removed may match"? Or can it be determined that it actually does match and msg says so, as in "removed does match"?
More things to think about...

[admin]

Code: Select all

The folder view definition to be removed is likely to match other folders as well: ... 

Works?

I guess. I still feel just saying "The folder view to be removed..." would work too, I don't see the need to have another term, but that's me I guess. Anyways yes, "definition" works just fine I think.

I also could go along without another term here, but if we did have one, (as I wrote before) I'd highly suggest "Profile" instead of 'definition" (or scheme) as it fits/works (IMO) much better in this usage.

But the sentence in code leads me to ask: How is "likely to match" determined? Is that a constant for all times or not? Or should it be more vague, such as "removed may match"? Or can it be determined that it actually does match and msg says so, as in "removed does match"?
More things to think about...

I found a little trick (and thanks for the "may match"!):

Code: Select all

The Folder View to be removed may match other folders as well: ... 

(1) "Folder View" with upper case initials: the stored definition/scheme/profile/whatever that defines the "folder view".
(2) "folder view" with lower case initials: what the folder looks like.

[graham]

I am so confused with the latest debate but with version 15 there may be an anomaly

I set up a FVS folder general setting to catch all folders with name images as last part of name

vis.
C:\Documents and Settings\home\my documents\*Images*\

and set include sub folders

If the trailing * is missing then the sub folders are not included

Is this a bug?

[ivan]

I would just like to inform that once things are ironed out and this seeps through to a full official release, I will certainly update. However, I would only use this for a couple of folders because the rest of them are fine with the standard (Ln #, Name, Size, Type, Created, Modified) layout. The point is that without being ungrateful, I can appreciate all the excitement that people are buzzing with regarding FSS. I just hope that next time there's a wish in the relevant forum section people will jump onboard and recognise possible usefulness of that too without comments like "...just because WE has it..." and "...this would bloat XY..."

[admin]

I am so confused with the latest debate but with version 15 there may be an anomaly

I set up a FVS folder general setting to catch all folders with name images as last part of name

vis.
C:\Documents and Settings\home\my documents\*Images*\

and set include sub folders

If the trailing * is missing then the sub folders are not included

Is this a bug?

This should work without the trailing *, and it does here. Maybe you have a typo somewhere?

[graham]

I am so confused with the latest debate but with version 15 there may be an anomaly

I set up a FVS folder general setting to catch all folders with name images as last part of name

vis.
C:\Documents and Settings\home\my documents\*Images*\

and set include sub folders

If the trailing * is missing then the sub folders are not included

Is this a bug?

This should work without the trailing *, and it does here. Maybe you have a typo somewhere?

Well yes it should work and I checked for typos but none. I think maybe it is connected to the default and try as I have with different set ups it only works with a trailing * all of which makes no sense. For now I shall wait until I have more time to check it out and more experience with FVS.

Great feature and I guess you have even more bits to add to it.