XBS: Name of file and name of configuration [Solved in 1.20]

[Peter2]

It seems that there is a problem with the XBS-configuration. I can save config "abc" under 123.xbs and then under 456.xbs. After restarting XnConvert the menu displays twice the entry "abc" ...

For the user there is no relation (connection) between loaded XBS-file and existing config-name. I don't know what the best way should be - maybe

a) config-name is the same as file-name OR
b) display a combination of file-name and configname, like "abc <- 123.xbs" and "123 <- 456.xbs" OR
c) let it be??

Regards

Peter

[Peter2]

Any comments?

Peter

[xnview]

b) display a combination of file-name and configname, like "abc <- 123.xbs" and "123 <- 456.xbs" OR

yes, perhaps it's better to show filename, what do you think?

[Peter2]

Filename should be Config-name.

Code: Select all

test.xbs = test-config
pdf2Tiff.xbs = pdf2Tiff-config

Peter

[xnview]

so when you save the xbs, you choose only the folder?

[Peter2]

Maybe the confusion starts when I save the XBS the first time...

The user defines
- a name for the config and
- then he can define another name for the XBS.

When you cancel the first step (name of the config) and offer only the "save as .." - then there is it always consistent.
Later, when the user opens "test.xbs", there will be the config "test" in it.

Peter

[xnview]

Please check XnViewMP 0.48

[Peter2]

hello

The usage of existing files is improved, but the creation of new ones is still confusing.

Still the same problem:
- There can be a name entered in the drop-down-list (also the tooltip tells me that I have to enter the name of a new script here).
- Under button "save" (next problem: the tooltip tells me "save", but in fact it is "save as ...") I can enter another name.

So there can be two names:
- One name inside the file: <XnView_script version="1.0" name="PDF_TIFF.xbs">
- One name as filename (outside the file) "test.xbs"

The loading (usage) of the files uses only the filename - that's OK.

My proposal:
- remove the entry "name" from the file-content (or set it to a standard-dummy-value)
- change the drop-down-list that the user can not write something
- rename the "save"-button to "save as ..."
- use only filenames for saving and loading

Peter