I always save vertices in csv
Please can you add an option to use .csv extension as extension in file name instead of .txt
This will save our time .
use .csv extension not .txt
Re: use .csv extension not .txt
I fear this is not possible since there can be only one default file extension by file type (ASCII here).
Daniel, CloudCompare admin
Re: use .csv extension not .txt
I mean just naming not file format
To set default to .CSV instead .TXT in file name not file format itself which is ASCII text
Now I have to use file manager to manually rename (points.txt) to (points.csv) so QGIS can accept it for layer import
.
.
Also, it will be helpful to set default separator to comma instead of space in ASCII saving box (or let CC remembers last choice"
.
To set default to .CSV instead .TXT in file name not file format itself which is ASCII text
Now I have to use file manager to manually rename (points.txt) to (points.csv) so QGIS can accept it for layer import
.
- 12.png (7.05 KiB) Viewed 4637 times
Also, it will be helpful to set default separator to comma instead of space in ASCII saving box (or let CC remembers last choice"
.
- 13.png (23.07 KiB) Viewed 4637 times
Re: use .csv extension not .txt
Yes that's what I understood, and that's why I said there can only be one default extension (and CSV is clearly not the default use case for the majority of users ;).
Of course one solution would be to make CC 'remember' the previous user input extension or separator. That should be not too hard for a motivated C++ developer.
Of course one solution would be to make CC 'remember' the previous user input extension or separator. That should be not too hard for a motivated C++ developer.
Daniel, CloudCompare admin
Re: use .csv extension not .txt
I prefer CSV and comma as separator because it is easily export to other software QGIS LibrieCALC etc
bu I understand
I did some research about if CC can remember parameters in cloud ASCII save dialogue
I compiled 2.12 from GitHub under Ubuntu 21
Result is
1- CC can remember your choice for cloud saving if (ASCII) or dxf etc
in Win and Linux
(in Linux CC save settings in /CCCor/CloudCompare.conf) at least on my PC
(in Win it is not clear how it save settings??)
2- However CC does not remember other parameters (separator "," or space precision etc)
3- In Linux CC saves settings in /CCCor/CloudCompare.conf including parameters (separator "," or space and precision etc) but unfortunately it can not remember (bug??)
4- I changed source file AsciiFilter.cpp to change default ASCII file extension to CSV and to change default separator to "," after I compiled CC changed its parameters to to CSV and ","
my change is
line:48
static int s_outputSeparatorIndex = 2;
line:93
"csv",
I hope in near future somebody let CC remember all parameters
bu I understand
(and CSV is clearly not the default use case for the majority of users ;).
I did some research about if CC can remember parameters in cloud ASCII save dialogue
I compiled 2.12 from GitHub under Ubuntu 21
Result is
1- CC can remember your choice for cloud saving if (ASCII) or dxf etc
in Win and Linux
(in Linux CC save settings in /CCCor/CloudCompare.conf) at least on my PC
(in Win it is not clear how it save settings??)
2- However CC does not remember other parameters (separator "," or space precision etc)
3- In Linux CC saves settings in /CCCor/CloudCompare.conf including parameters (separator "," or space and precision etc) but unfortunately it can not remember (bug??)
4- I changed source file AsciiFilter.cpp to change default ASCII file extension to CSV and to change default separator to "," after I compiled CC changed its parameters to to CSV and ","
my change is
line:48
static int s_outputSeparatorIndex = 2;
line:93
"csv",
I hope in near future somebody let CC remember all parameters