|Anonymous | Login | Signup for a new account||2019-05-24 21:18 PDT|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004824||Dwarf Fortress||Legends Mode -- Map Export||public||2011-08-12 20:50||2014-01-21 19:56|
|Platform||Windows||OS||Windows 7||OS Version|
|Target Version||Fixed in Version|
|Summary||0004824: DF doesn't notice if "export image/info" fails due to file system permissions etc|
|Description||When I finish generating a world, and I hit 'p' to export the map, nothing happens. The game provides no feedback that a button was pressed, and no new files are created in my Dwarf Fortress directory, or anywhere else I can find.|
|Steps To Reproduce||1) Generate a world (any parameters).|
2) When it finishes, hit 'p'.
A map image and some text files with generation parameters appear in the directory with the Dwarf Fortress executable.
|Tags||No tags attached.|
|Works OK for me (0.31.25). However I'm on Linux, not Windows, so could potentially be OS-related.|
I'm using windows 7 and experiencing no problems.
This issue DOES however occur if DF is installed in a system directory (like "program files") and not run in administrator mode, since the DF process is not authorized to create new files there.
This is more of a bug with the fact that windows fails to inform you of the aborted file creation than it is a problem with DF itself.
Reminder sent to: herufeanor
Does caldfir's post at 0004824:0018506 clear things up?
edited on: 2011-08-15 22:00
Actually, I can recreate the problem on Linux by simply removing write permissions on the game directory; after doing so, the game itself fails to report the failure to write the worldgen info (or savegames, etc)
The difference with Linux is that at least if you run the game from a terminal window, the failure gets reported there. I'm guessing on Windows, if you ran DF from a cmd.exe window, you might get the same; but I'd imagine very, very few Windows players run the game that way.
I'd also point out that this means it's not a "Windows problem". While I'm sure the proportion of Linux users who are command-line-disabled is much smaller, I'm also sure they exist, and are growing.
Yes, that was the problem.
I also agree with UristMcDorf: It's not the OS' job to report the failure to the user. The OS should report the failure to the application, and leave it up to the application to report the failure to the user in the appropriate way. Even if you have a console open, the user shouldn't be expected to dig through the console output to figure out why the button they're pressing isn't doing anything.
|2011-08-12 20:50||herufeanor||New Issue|
|2011-08-12 21:53||UristMcDorf||Note Added: 0018495|
|2011-08-13 15:02||herufeanor||Note Added: 0018503|
|2011-08-13 17:53||herufeanor||Note Deleted: 0018503|
|2011-08-14 08:58||caldfir||Note Added: 0018506|
|2011-08-15 11:55||Footkerchief||Note Added: 0018518|
|2011-08-15 11:55||Footkerchief||Tag Attached: AWAITING UPDATE|
|2011-08-15 21:10||UristMcDorf||Note Added: 0018526|
|2011-08-15 21:10||UristMcDorf||Issue Monitored: UristMcDorf|
|2011-08-15 22:00||UristMcDorf||Note Edited: 0018526||View Revisions|
|2011-08-15 22:20||herufeanor||Note Added: 0018527|
|2011-08-16 08:02||Footkerchief||Summary||Export image/info doesn't do anything => DF doesn't notice if "export image/info" fails due to file system permissions etc|
|2014-01-20 19:03||Footkerchief||Tag Detached: AWAITING UPDATE|
|2014-01-20 19:39||Footkerchief||Relationship added||has duplicate 0005773|
|2014-01-21 19:56||Footkerchief||Relationship deleted||has duplicate 0005773|
|2014-01-21 19:56||Footkerchief||Relationship added||related to 0002587|
|Copyright © 2000 - 2010 MantisBT Group|