XYplorer Beta Club

admin wrote:Okay, it uses the LM GUI, but only because I faked it to be a simply List which it is not! It's a data structure for which LM is not made. Plus, most LM buttons are disabled. It is more likely that in a later stage I write a proper interface just for managing FVs. At the moment you want to edit FVs that are not currently active this will be needed anyway.

Yeah, I guess you're right...

j_c_hallgren wrote:Ok, so I was doing something that I shouldn't ..but still...the way XY presented it was not the most pretty...I was looking at "fvs.dat" via Raw View and then tried to do a "Save FVS"... we know file is obviously in use at that time but initially get this

Code: Select all

Error 	70 (00000046)
Desc	Permission denied
Dll	0
Proc	dumpFSS to: C:\PROGRA~1\XYplorer\fvs.dat

Source	XYplorer
XY ver	7.40.0016
OS	Win2K (Service Pack 4)
Date	8/11/2008 2:43:44 PM

before I got the "Save Settings failed" box...maybe a better handling of this might be in order, if possible?

For example "Stop playing with Raw View and continue working!"

admin wrote:

Code: Select all

Proc 	dumpFSS to: C:\PROGRA~1\XYplorer\fvs.dat

So, why does it still say FSS here, that function needs to be renamed!

jacky wrote:

admin wrote:

Code: Select all

Proc 	dumpFSS to: C:\PROGRA~1\XYplorer\fvs.dat

So, why does it still say FSS here, that function needs to be renamed!

It's FSS all over the place here in the code. I'll wait a couple of days until I change this again!

After that dump type error msg, it got me going back to a previous topic of discussion which is that using the word "Save" in the FVS sub-menu is somewhat misleading (IMHO) in that, until the settings are saved via File|Settings menu or exit, they are not truly saved so if XY/system were to crash in meantime, these would be lost...yes, I fully realize that other things work the same way, like INI and CKS and such, but they don't explicitly say save anywhere, but rather "Ok" or similar.

Even using the word "Keep" would remove the presumption that data has been really saved...maybe there's a better non-"save" word instead?

Could be it's just me, but trying to think of newer users who think save would do so, whereas "Keep" or similar may not unless some other action is taken.

j_c_hallgren wrote:Even using the word "Keep" would remove the presumption that data has been really saved...maybe there's a better non-"save" word instead?

Store?

----

Little bug : "Save FV As" does not get us feedback in the statusbar, especially confusing if you remove a FV, save as another one, and then look to your statusbar...

jacky wrote:

j_c_hallgren wrote:Even using the word "Keep" would remove the presumption that data has been really saved...maybe there's a better non-"save" word instead?

Store?

That was the other word I'd first thought of, but then forgot it by time I wrote the above post, so that'd work for me.

It's a minor thing, as I admit, but we don't want anyone to complain that it said it'd "saved" it and then lost it, whereas "store" doesn't 100% imply that it's been retained permanenty yet.

j_c_hallgren wrote:

jacky wrote:

j_c_hallgren wrote:Even using the word "Keep" would remove the presumption that data has been really saved...maybe there's a better non-"save" word instead?

Store?

That was the other word I'd first thought of, but then forgot it by time I wrote the above post, so that'd work for me.

It's a minor thing, as I admit, but we don't want anyone to complain that it said it'd "saved" it and then lost it, whereas "store" doesn't 100% imply that it's been retained permanenty yet.

I know what you mean, but I like to stay with Save anyway. "Store" is somehow weird and "Store As" even more so.

It's a minor thing, as I admit, but we don't want anyone to complain that it said it'd "saved" it and then lost it, whereas "store" doesn't 100% imply that it's been retained permanenty yet.

Store reminds me of mainframe speak!

I suggest that feedback in the statusbar includes the word memory or some word to show it is not saved to file at that time.


In addition I think a probably a good idea to add Save to File under Customize Toolbar. This is useful for users like me who only exit XY occasionally and this addition would make it quick to make the save permanent and be able to carry on working.

graham wrote:

It's a minor thing, as I admit, but we don't want anyone to complain that it said it'd "saved" it and then lost it, whereas "store" doesn't 100% imply that it's been retained permanenty yet.

Store reminds me of mainframe speak!

I suggest that feedback in the statusbar includes the word memory or some word to show it is not saved to file at that time.


In addition I think a probably a good idea to add Save to File under Customize Toolbar. This is useful for users like me who only exit XY occasionally and this addition would make it quick to make the save permanent and be able to carry on working.

"...saved to memory." -- good idea!


Save to File under Customize Toolbar? What/Where do you mean?

admin wrote:

graham wrote:In addition I think a probably a good idea to add Save to File under Customize Toolbar.

Save to File under Customize Toolbar? What/Where do you mean?

Maybe he's like me and didn't realize there is a TB icon for "Save Settings"?

And when I did see it (based on this post), I don't have any room to add it anyway...maybe if there was a way to have Tabs & Addr Bar together with Toolbar above it? I presently have TB & AB above Tabs, but would give up a bit of tab room to have a minimal AB and more TB icons....but that's for a separate thread...

j_c_hallgren wrote:

admin wrote:

graham wrote:In addition I think a probably a good idea to add Save to File under Customize Toolbar.

Save to File under Customize Toolbar? What/Where do you mean?

Maybe he's like me and didn't realize there is a TB icon for "Save Settings"?

And when I did see it (based on this post), I don't have any room to add it anyway...maybe if there was a way to have Tabs & Addr Bar together with Toolbar above it? I presently have TB & AB above Tabs, but would give up a bit of tab room to have a minimal AB and more TB icons....but that's for a separate thread...

This is actually coming soon...

Save to File under Customize Toolbar? What/Where do you mean?

In the same context menu as the save folder view ......


Yes I realise there is a TB button for this purpose and actually have it but whilst attending to FV matters it is very convenient to have an entry in the list to save settings permanently.

Well, getting busy to (try to) be ready for Monday let me repeat a few things said previously, because they haven't changed and I still feel they should, and add new ones while at it...

jacky wrote: ...an unexpected (to me) behavior : you're in a folder using a FV w/subfolders. You change something and press "Save" to update your settings, right? Well, wrong: it creates a new one for this subfolder only!

Maybe it should ask us : update current one (D:\Folder w/sub) or create a new one (D:\Folder\Sub) ?

This one is especially wrong to me, and I'd definitely classify this as a bug, because :
- changes done when using "Auto-save changes" apply to the loaded (w/sub) FV
- using "Edit" allow us to change the loaded (w/sub) FV
- Yet changes saved manually using "Save Folder View" will create a new FV !! This is, to me, unexpected behavior on its own, and even more so given that as I said all other functions apply to the loaded (w/sub) FV

I really feel that a popup asking us what to do, create a new FV for this specific folder or update the currently used/loaded one is the way to go. (Note that same applies when using pattern.) I know popups aren't good when they get in the way, but here this is definitely not the case.

jacky wrote: Relative syntax "?:\" seems to work, but not ".\Scripts\" or "..\"

Well, that's it, and that's a bug. What reasons could there be not to support this syntax as well like everywhere else in XY ? It's not like it could be used in patterns or anything...

Okay I got confused for a bit over this one. Recap: At first, you said that tabs "took over" FV. That is, when changing tab XY would use the Tab settings and not the FV (if any). It seems you changed that, which is good.

But, apparently it seems to be somewhat buggy right now and not to work with column visibility, possibly resulting in quite confusing things...

Finally, little thing : Imagine I want to set a FV for all folders containing "pictures" in their names, wherever they are located, but not their subfolders. Right now I can't obviously, since "*pictures*\" will include any subfolders anyways. Maybe it's a silly example, but maybe for that and other cases, regexp support (prefix >) could help ?

Prompt update/create new: Yes! I added it.

jacky wrote: Relative syntax "?:\" seems to work, but not ".\Scripts\" or "..\"

Relative syntax: "?:\" as pattern would match any drive, as portable only XY's drive. I will see what I can do about .\ and ..\ -- but relative to what? To app path or app data path?

jacky wrote: Okay I got confused for a bit over this one. Recap: At first, you said that tabs "took over" FV. That is, when changing tab XY would use the Tab settings and not the FV (if any). It seems you changed that, which is good.

But, apparently it seems to be somewhat buggy right now and not to work with column visibility, possibly resulting in quite confusing things...

I'm not aware of having changed anything. The interaction between tab memory and FV is a bit complex, especially with locked tabs that lead to automatic tab switches. I don't see where I could improve this.

jacky wrote: Finally, little thing : Imagine I want to set a FV for all folders containing "pictures" in their names, wherever they are located, but not their subfolders. Right now I can't obviously, since "*pictures*\" will include any subfolders anyways. Maybe it's a silly example, but maybe for that and other cases, regexp support (prefix >) could help ?

Yes, later.