Hi Nick, just found an issue when using the installation files explorer. I have 2 files to be installed, both listed under "%installdir%". I wanted to get rid of them, so right clicked on 1 and selected 'Delete'. Answered yes to the prompt, but the file remained. Same happened with the other file.

Also when trying this earlier I was getting "list out of bounds" errors when both were selected and right-clicking to select delete. However this seemed to stop happening at some point - not sure what I did to make this happen.

I was to busy updating the whole source code to be unicode compatible, to hunt bugs

To this post there is the 2.1 beta, with the bug fixed.
www.aperitto.com/component/option,com_ku...view/id,148/catid,9/

Regards,
Nick Protopapas

Hmm, the change you've made is working but only some of the time - it still seems quite inconsistent, sometimes deleting the file from the explorer works and other times it doesn't? Apologies, I can't find exactly what sequence of events results in a successful delete and what doesn't.

Also had an issue with creating a new project, I added a file then deleted it, before I had saved the project (was successfully removed from the explorer). Then forgot about this until I had completed the project and went to build it. It seemed that there was still a record of the original file that I had deleted there.

The reason I had deleted it was that I accidentally used the drop file with relative path setting before I had saved the project, which resulted in an incorrect relative path being used. But then after deleting it I got an error in the build process where it was still referring to the incorrect path.

So maybe as well as the delete issue there is another problem with the relative path feature? If you save the project to another directory (or set the paths while the project is unsaved, then save it) do you dynamically update all the relative paths - by the looks of this issue maybe not?

Really like the relative path feature though, makes sharing a project amongst developers who use the same overall file structure for a project but at possibly different locations on their PCs much easier!

I think and hope that the majority problems with the ppc file explorer are solved.

Simply delete all the old code and write it from the scratch. Now the builder generates on the fly the SourceDisks and CopyFiles sections just before the user shows the builder dialog.

As for the relative path, no i don't update the paths dynamic after the project is saved.
Do you think that is good to be happen ?
Also i think to have the user forced to save the project every time it creates a new one.

Redownload the 2.1b with fixes of the ppc file explorer, and tomorrow I'll upload the dynamic relative paths.

www.aperitto.com/media/downloads/ppcic_2.1_beta.exe

Regards,
Nick Protopapas