[NVO] Bug file handle not released

[ouly]

Hi everyone,
There is an annoying bug in NVO. When a file operation failed, the handle to this file is not always released and so the file leaves definitely locked until the app is closed.
Can you fix this issue? Thanks!
ouly

Example: http://files.magicspark.org/nvo-bug-file-handling.mfa

[z33z]

Okey, fixed it.. Try this..

[nivram]

z33z. Where do we put the corrected mfx? In the extension folder or runtime folder?

Thanks,

Marv

[LB]

MMF2 uses the one in the Extensions folder (the Edit Time version) and the Runtime version in the Data\Runtime folder is put into the compiled EXE. The Edit time version can be used for Runtime, but the idea is to have a smaller file size by not having edit time code in the run time MFX. For testing single MFXs in MMF2, just plop them in the Extensions folder after backing up the original, if any. Hope I explained it well, Marv

[z33z]

I'll try to release the final version soon then..

[nivram]

Thanks LB and z33z.

Marv

[ouly]

Sorry, the bug is still here.

[z33z]

Can you reproduce it with your example inside MMF? Or just in a built exe-file? (Meaning that you didn't replace the runtime version of the extension)

[ouly]

I have just redownloaded nvar.mfx from dropbox, deleted the old one and copied the new file to be sure. The example provided has been executed inside MMF. The data file read by NVO is still write-locked.

Perhaps the file on dropbox is not the last one?

Two others things:
- Condition "Last key exist" doesn't work with "Key exist". But works correctly with conditions "Number of keys ..."
- There is little mistake in texts for actions "Set at address".

Edit: and with the same nvar.mfx in runtime, it's the same.

[ouly]

Sorry to disturb you but are there any news on these issues?