View Issue Details

IDProjectCategoryView StatusLast Update
0001057OpenMPTUser Interfacepublic2017-12-18 13:51
Reporterblimey Assigned ToSaga Musix  
PrioritylowSeverityminorReproducibilityunable to reproduce
Status resolvedResolutionfixed 
Platformx86OSWindowsOS Version10
Product VersionOpenMPT / libopenmpt 0.3.2/0.3.3 (upgrade first) 
Target VersionOpenMPT / libopenmpt 0.4.0 (upgrade first)Fixed in VersionOpenMPT / libopenmpt 0.4.0 (upgrade first) 
Summary0001057: No error message when opening recent module files

If you try to access a recent file unsuccessfully, it should probably give you an error message. The current behaviour is a NO-OP.

Steps To Reproduce

Open a module file
Close the module file
Delete the module file from disk
Try opening the module file from the list of recently opened files
Nothing happens - should ideally report the error message generated by the operating system, e.g. file not found, disk not mounted etc.

TagsNo tags attached.
Has the bug occurred in previous versions?Yes
Tested code revision (in case you know it)


Saga Musix

Saga Musix

2017-11-08 23:30

administrator   ~0003323

Last edited: 2017-11-08 23:30

I know that the behaviour you describe definitely existed many years ago but nowadays you should get an error message like this when a file cannot be found: "Unable to open "<filename>": file does not exist."

Saga Musix

Saga Musix

2017-11-11 13:55

administrator   ~0003330

Without any further information how you managed to trigger this situation in the current OpenMPT release I cannot do anything about it.



2017-11-11 18:17

reporter   ~0003340

Try loading a file from recent, that was on a USB stick you no longer have plugged in. No error messages result in this specific case.

Saga Musix

Saga Musix

2017-11-11 18:30

administrator   ~0003342

Thanks, that was the missing information. Unfortunately there seems to be an inconsistency deep inside MFC regarding non-existing files depending on whether they are located on an existing or non-existing drive. I think we should be able to work around that, though.

Saga Musix

Saga Musix

2017-12-10 16:26

administrator   ~0003381

Fixed in r9351. Due to the size of the workaround (moving around stuff), this will most probably not be backported to OpenMPT 1.27 but instead be fixed in the upcoming OpenMPT 1.28.

Issue History

Date Modified Username Field Change
2017-11-08 21:45 blimey New Issue
2017-11-08 23:30 Saga Musix Note Added: 0003323
2017-11-08 23:30 Saga Musix Reproducibility always => unable to reproduce
2017-11-08 23:30 Saga Musix Note Edited: 0003323
2017-11-11 13:55 Saga Musix Note Added: 0003330
2017-11-11 18:17 geoffswift Note Added: 0003340
2017-11-11 18:30 Saga Musix Note Added: 0003342
2017-11-11 20:27 Saga Musix Assigned To => Saga Musix
2017-11-11 20:27 Saga Musix Status new => assigned
2017-11-11 20:27 Saga Musix Target Version => OpenMPT / libopenmpt 0.4.0 (upgrade first)
2017-12-10 16:26 Saga Musix Note Added: 0003381
2017-12-10 16:27 Saga Musix Status assigned => resolved
2017-12-10 16:27 Saga Musix Resolution open => fixed
2017-12-18 13:51 Saga Musix Fixed in Version => OpenMPT / libopenmpt 0.4.0 (upgrade first)