I am not able to reproduce this issue. When an export happens and the preference is ".", it will save the files to the same directory as the project .xds file. Tested on Linux, OS X, and Windows.
Am I not understanding the issue? Are you just speaking about the output of the path, or are your files not exporting to the same directory as the .xds file? I need a very clear 1-2-3 way to reproduce this.
Does not save to user define path, instead it saves to project folder, placing 'http/' folder inside
Problems seemed to start happening immediately after I had EXPORTED my project so I could edit a .js file in another editor(as per your Ext Designer demo video/docs). After I edited the js doc, viewed the results in my browser, and was satisfied, I deleted all of those exported files(html/js), with the intention of doing a second/fresh EXPORT after making some new edits to the XDS project file. It was at the time of this second EXPORT that I noticed the EXPORT was no longer saving the files in the user defined path, but instead, it was saving it to the folder that the XDS file was saved in, and instead of just saving the files into that folder, it created a folder named 'http/' with one forward slash, and another folder inside of it called 'localhost' and another inside of it called 'extjs' and another one named 'demo' which in short is the path to my XDS file translated into nested folders. My user defined EXPORT PATH was/is http://localhost/extjs/export/ and my PROJECT PATH was/is in http://localhost/extjs/demo/.
To continue, I closed the app, started a new project using the same project folder to house the XDS file, and the same export folder as I used before and described above, but the problem still existed. I then closed/opened the app and created a new project in new folder and create a new export folder, and made those user settings(EXPORT PATH & PROJECT PATH) again, same problem... this time it placed the 'http/' folder inside of the new project folder where the XDS file is, instead of to the export path as was user defined in the Preferences. So definitely a bug.
Speaking of EXPORT PATH, and assuming it gets fixed... I would also suggest adding one more user control in that Preference menu... allow the user to set a GLOBAL PROJECT & EXPORT PATH that sticks even when the app is closed/opened, but also allow the user to set a unique path specific to that project(as is the case now). This way, the user does not always need to go in and edit the path for every new project file, as it always defaults back to stock settings. It would simply be nice to know/remember the user defined global path was/is saved and stuff will be saved there unless the user overrides it with settings specific for the project/XDS file.