PureBasic Forums - English

A new version is online => Purefiler now supports 64 Bit.
Though, in 64 Bit mode inline assembly is not compatible with Purefiler!

Well that was fast!

Thanks
-j

jassing wrote:Well that was fast!

Thanks
-j

Thought it would be usefull to you

Well -- good news is it seems to run (both 32 and 64). If I say "yes" to include purefiler, build takes much longer.
But, the bad news is neither result in data saved -- I launch purefiler and get a dialog telling me there is nothing available, and then it exits.

Dumb question: Did you actually rub your built executable?

Didelphodon wrote:Dumb question: Did you actually rub your built executable?

aye -- both letting it exit gracefully and pausing and/or killing the exe. Ran it for 30 seconds, and 2 hours; never anything for purefiler....

Purefiler needs a successful exit - so, no forced quit.
However, you said that you already had a successful exit - that makes me wonder, hm.
Do you find a Purefiler folder in your home-folder?

Didelphodon wrote:Purefiler needs a successful exit - so, no forced quit.
However, you said that you already had a successful exit - that makes me wonder, hm.
Do you find a Purefiler folder in your home-folder?

nope.

Tried a lot of things now on my system but couldn't get Purefiler to act as you described it.
Have you bound Purefiler to the "build" or "compile" event? It should be bound to "build".

A new build (142) is online. Details are in the "edit" area in the first post.

Didelphodon wrote:A new build (142) is online. Details are in the "edit" area in the first post.

Now when I build, I get a dialog "Line 36866 EmptyWorkingSet() is not a function,array,list,map or macro" --This procedure is declared and if I build to an exe (vs: F5 to run it with PureFiler) the exe is built, runs correctly, and makes this call w/o issue.

It's kinda hard to say from here what the reason is. You know your code best - maybe you can take a look at the file PB_EditorOutput.pb in your temp-folder right after building with Purefiler. This file contains all the altered sourcecode which matches to the error-line-number you got. I'm sure you'll find out what makes PB whine. If not and if you don't mind you can share the content of this file with me via PM so I can take a look.

However, I'm still not sure if you try to use Purefiler during normal compile (F5) or during building the executable.

Could you tell me please, is there an easy way to remove all "Purefiled Runs"? Currently I manually delete all *.pfl and *.pfr files from user profile directory, but its not very comfortable. Or did I miss something?

ostapas wrote:Could you tell me please, is there an easy way to remove all "Purefiled Runs"? Currently I manually delete all *.pfl and *.pfr files from user profile directory, but its not very comfortable. Or did I miss something?

Currently there's no way but deleting them manually. Do you feel that there is a "need" to add such a feature?

Didelphodon wrote: Do you feel that there is a "need" to add such a feature?

Hm, it seems like a downright necessary feature, at least for me Shouldn't it take just several minutes to implement?