 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Pages: 1
In APG 3.0.1 I noticed that adding %b to rendered file name also adds (-2) - I do not understand why?
I understand that this is cosmetic and APG still performs - Would it be possible to make it go away?
* This is clearly a bug - though not critical.
There is one more thing which has been on my chest for a long time - since pre APG times:
Would it be possible to rid of the brackets in FOV - %f please?
* This is a wish - it has been around for long time and it probably has some meaning - though it is not obvious to me what that bracketed number in FOV mean as APG cannot know true horizon without a bubble level.
Reasoning why I care:
1. Brackets in file names are nasty in any command line, regexp, etc. - all shells interpret it somehow and it is painful escaping game to deal with
2. it is ugly and lengthens file names without adding value
3. If user wants brackets they can add it to the file name formatting string
I hope people do not feel that I am picking on insignificant details.
Screenshot example attached.
Thank you, Tomas
Offline
Hello Tomas,
In APG 3.0.1 I noticed that adding %b to rendered file name also adds (-2) - I do not understand why?
I understand that this is cosmetic and APG still performs - Would it be possible to make it go away?
* This is clearly a bug - though not critical.
Not really a bug... When the selected blender is multiband, we also write the blend 'level', (here -2), so it 'means' something.
Concerning the FOV data, the bracketed value is the mean vertical angle.
Regards,
Thomas
Offline
Thank you for your answer about what that special character stuff means.
Would you be so kind and look into the merit of my original report - how to stop the brackets and other special characters in the file names?
Is there a way?
Are you willing to exercise the the idea of outputting "nice" unix file names and still being able to print useful search info such as FOV and blender type at all?
I absolutely do not want to be rat-holing about it - I asked nicely - so it would be nice to get nice and clear answer. Right now I am left to guess if this was even considered.
I mean my report and this response positively and constructively and understand your overprotective reaction - I hope I'm not offending.
Thanks, Tomas
Offline
We add your demand in the wish list. But we can't confirm that we will change apg naming rules for one user workflow.
Offline
Thank you.
By no means my post was meant as a demand - more like a plea - I understand that "demand" could be a translation issue. Still, I better make sure that I am not perceived wrongly.
I'm used to bad abuse of file naming... preventing easy command line and/or scripting work.
If you really believe that my suggestion has no merit and that I am the only one using command line or scripting stuff in shell - Then I understand that you would not want to sink time into it. Being this unique is kind of flattering.
:-) Tom
Offline
Pages: 1