google-code-export / zscreen

Automatically exported from code.google.com/p/zscreen
1 stars 0 forks source link

More flexible naming conventions #466

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What new or enhanced feature are you proposing?
Naming conventions like:
Last entered name
or/and
Fixed prefix + incremental  e.g.  25_1, 25_2, 25_3

What goal would this enhancement help you achieve?
Make easy entering difficult file names, that differ only in one symbol.

Original issue reported on code.google.com by vas...@gmail.com on 25 Jun 2011 at 6:55

GoogleCodeExporter commented 9 years ago
Sorry, just realized that prefix+inc is already implemented.
So only "last entered name" left.

Original comment by vas...@gmail.com on 25 Jun 2011 at 7:05

GoogleCodeExporter commented 9 years ago
but it would be convinient if prefix could be edited in the window where you 
specify name of screenshot.

Original comment by vas...@gmail.com on 25 Jun 2011 at 10:56

GoogleCodeExporter commented 9 years ago
Hi vaso82

When you have "Prompt for File name and Destinations" you get the Save File 
Dialog where you have the chance to change the file name even further. 

http://i.imgur.com/po8Ha.jpg

File Naming pattern can be changed here 

http://i.imgur.com/dIOTa.png

Do you mean you want to change this pattern for every screenshot you upload as 
part of "Prompt for File Name and Destinations" ? 

Thanks
Mike

Original comment by mcored on 10 Sep 2011 at 2:31

GoogleCodeExporter commented 9 years ago
Hi Mike.
I can't change name of file properly in latest stable version (4.2.5)
Before,i could change name in same window, that appeared after marking area and 
releasing left button.
Now i have to press button to the right of file name string and change name in 
save file window and i also have to type manually .jpg extension, otherwise 
file is saved in png even if i selected jpg in options.

Original comment by vas...@gmail.com on 17 Sep 2011 at 5:14

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r2556.

Original comment by mcored on 17 Sep 2011 at 7:06