I have the latest build of RLMP installed. As I work on a project, I may make a number of modifications to the layout with RLMP, save and export again. Each time I export, RLMP goes back to the default install folder instead of staying where the project is actually saved.

Is this the same for everyone or is there a setting some place where I can make it stay where the project is saved?

Thanks for pointing that out. We will get that fixed in one of the next releases. How is that for support Brian!

I'm using this program nearly everyday and I didn't notice that, good spot that Brian

I noticed that but really never thought much of it because the form builder doesn't keep it's last location that you exported after closing it. Just got kind of use to browsing to the proper location.

I a with you on that one Eric. I do not like when it remembers. Because 90% of the time I do not want to save in the same location anyway.

Scott, I must say that CC support is impeccable.

Adam, I understand. In my case, I export from RLMP but I don't use the generated templates directly. I create a copy of the generated template(s) outside the export directory and link them to the css files inside the exported directory. In this way, it allows me to make future edits and tweaks and export without having to worry about writing over any custom parts. By allowing me to re-export frequently, all my css changes (except for customizations beyond what RLMP allows) make it back to the native RLMP file. As I approach the end of a project, I end up making a lot of css changes -- tweak, export, observe, repeat. Yes, it would be quicker to just make the change directly to the css, but I want to make sure that the change is also in RLMP so that if something major has to be changed in the future, I don't lose the customizations. (If there is a better way to do this, please let me know.)

To allow for both situations, those who do and do not want the path to the export to be saved, perhaps it's possible to have a checkbox in the options that allows the user to choose.

It's an idea.

-(If there is a better way to do this, please let me know.)

Even though we do recommend that you export to the same folder, I like to keep a repository of files. So when I build I have Version 1, Version 2, etc.

So I keep everything separate. It is pure preference on how you work.

I always keep my exports in the original folder but remove the _exported from the name. This way when I export to the same directory I don't lose the altered one. This makes it easy to transfer the custom changes to my new files.