|
|
| Reporter | STiFU | Assigned To | | |
|---|
| Priority | normal | Severity | normal | Reproducibility | always |
|---|
| Status | closed | Resolution | no change required | |
|---|
| OS | Mandriva | OS Version | 2010.1 & 2011.0 | |
|---|
| Product Version | 1.4.0 | |
|---|
|
|
| Summary | 0002340: Saving XData definitions only works within one session of the Readable Editor |
|---|
| Description | Original report by PranQster in this thread (including screenshots and video): http://modetwo.net/darkmod/index.php?/topic/11438-xdata-trouble-with-readable/
We should try to reproduce this misbehavior on Ubuntu. After all, we can't support any existing Linux distribution. |
|---|
| Steps To Reproduce | Open the Readable Editor on a readable entity, create a text and hit save. Works! Hit save again. Works! Reopening the Readable editor on that entity and hitting save again results in an error message: "You have imported an XData definition that is contained in a PK4, which can't be accessed for saving." |
|---|
| Additional Information | First quick investigations showed that there might be something wrong with the following methods:
-GlobalGameManager().getModPath()
-GlobalGameManager().getModBasePath()
-GlobalRegistry().get(RKEY_ENGINE_PATH)
The storage path is always displayed in the titlebar of the editor. Before closing the editor after the initial save, the titlebar says ".doom3/darkmod/xdata/[xdata-file]", whereas it should typically just read "darkmod/xdata/[xdata-file]" (The engine path should be ommited). After reopening the editor, the titlebar says "rkmod/xdata/[xdata-file]".
This bug still exists after specifying a custom folder for the Readable Editor in the DR preferences, which is kind of a contra argument against my assumptions about the probable origin of the bug.
PranQster also tried to setup proper file access rights on the [xdata-file], which did not work as well. |
|---|
| Tags | No tags attached. |
|---|
|
|
