This repository has been archived by the owner. It is now read-only.

Default config does not point to the default audio file #1956

Closed
bastik-1001 opened this Issue Apr 23, 2017 · 4 comments

Comments

2 participants
@bastik-1001

bastik-1001 commented Apr 23, 2017

With version 11.0.0. (64bit) on Windows 7 (64bit), the config points to <MTX_INSTALLATION_DIRECTORY>\sounds\finished-1.ogg, while the file was placed by the installer in \data\sounds. That results in the file not being played (of course).

I can't tell if that is due to system specific placement by the installer.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Apr 23, 2017

Owner

Meh. Thanks. I'll fix that.

Owner

mbunkus commented Apr 23, 2017

Meh. Thanks. I'll fix that.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Apr 23, 2017

Owner

New pre-builds for Windows are compiling and should be available shortly. They'll also update existing, wrong paths in your configuration.

Owner

mbunkus commented Apr 23, 2017

New pre-builds for Windows are compiling and should be available shortly. They'll also update existing, wrong paths in your configuration.

@bastik-1001

This comment has been minimized.

Show comment
Hide comment
@bastik-1001

bastik-1001 Apr 23, 2017

Not that it would have been important in any way, but I downloaded the pre-build and it does indeed fix the issue.

BTW, I had noticed before that the input field was cleared upon canceling the selection, but I assumed that it would check if a file exists it has been configured to use and if it wouldn't exist it would clear it.

bastik-1001 commented Apr 23, 2017

Not that it would have been important in any way, but I downloaded the pre-build and it does indeed fix the issue.

BTW, I had noticed before that the input field was cleared upon canceling the selection, but I assumed that it would check if a file exists it has been configured to use and if it wouldn't exist it would clear it.

@mbunkus

This comment has been minimized.

Show comment
Hide comment
@mbunkus

mbunkus Apr 23, 2017

Owner

BTW, I had noticed before that the input field was cleared upon canceling the selection, but I assumed that it would check if a file exists it has been configured to use and if it wouldn't exist it would clear it.

No, that was a straight-up bug. Canceling any file dialog should not alter anything ever. I noticed this during the investigation of the wrong audio file location and fixed it in 2a7be92.

Owner

mbunkus commented Apr 23, 2017

BTW, I had noticed before that the input field was cleared upon canceling the selection, but I assumed that it would check if a file exists it has been configured to use and if it wouldn't exist it would clear it.

No, that was a straight-up bug. Canceling any file dialog should not alter anything ever. I noticed this during the investigation of the wrong audio file location and fixed it in 2a7be92.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.