On Windows 10, Tablecruncher 1.8 opens an empty document instead of the selected CSV file when launched via file association or command line.
Steps to reproduce
- Install Tablecruncher 1.8 for Windows.
- Associate
.csv files with Tablecruncher.
- Double-click any
.csv file.
Expected behavior
The selected CSV file should open in Tablecruncher.
Actual behavior
Tablecruncher opens an empty document named Empty 1.
Also reproducible from PowerShell
& "C:\Program Files (x86)\Tablecruncher\Tablecruncher.exe" "C:\temp\test.csv"
This also opens Empty 1 instead of C:\temp\test.csv.
Environment
OS: Windows 10
Tablecruncher version: 1.8
Install path: C:\Program Files (x86)\Tablecruncher\Tablecruncher.exe
Possible cause
On Windows, main.cpp uses WinMain with lpCmdLine, but the file-opening logic for command-line arguments appears to be implemented only in the non-_WIN64 argc/argv path.
As a result, the Windows build seems to ignore the file path argument passed by Explorer or PowerShell.
On Windows 10, Tablecruncher 1.8 opens an empty document instead of the selected CSV file when launched via file association or command line.
Steps to reproduce
.csvfiles with Tablecruncher..csvfile.Expected behavior
The selected CSV file should open in Tablecruncher.
Actual behavior
Tablecruncher opens an empty document named
Empty 1.Also reproducible from PowerShell
This also opens Empty 1 instead of C:\temp\test.csv.
Environment
OS: Windows 10
Tablecruncher version: 1.8
Install path: C:\Program Files (x86)\Tablecruncher\Tablecruncher.exe
Possible cause
On Windows, main.cpp uses WinMain with lpCmdLine, but the file-opening logic for command-line arguments appears to be implemented only in the non-_WIN64 argc/argv path.
As a result, the Windows build seems to ignore the file path argument passed by Explorer or PowerShell.