06-14-2006, 12:48 PM
I was thinking, yes still lol, and i thought about even more securing shareware macros.
If it would be posible to lock folders like you can lock a whole file it would be very nice feature.
Then you can distribute a macro file which has public accessible, and editable, parts and parts that are protected from listing/viewing etc.
Ofcourse this needs to take into account that it should still be posible to update parts in that protected folderspace when you implement that "patch" functionality i mentioned earlier in this forum...
(Maybe check passwords in patch file and compare to passwords of folder etc in file tobe patched...)
I think momentarily only, partialy, posibility for this is to use 2 seperate macro files where one includes the other as shared file?
Or will QM then still need the password to access the locked file from the first unprotected file?
If it would be posible to lock folders like you can lock a whole file it would be very nice feature.
Then you can distribute a macro file which has public accessible, and editable, parts and parts that are protected from listing/viewing etc.
Ofcourse this needs to take into account that it should still be posible to update parts in that protected folderspace when you implement that "patch" functionality i mentioned earlier in this forum...
(Maybe check passwords in patch file and compare to passwords of folder etc in file tobe patched...)
I think momentarily only, partialy, posibility for this is to use 2 seperate macro files where one includes the other as shared file?
Or will QM then still need the password to access the locked file from the first unprotected file?
Well thats all for now, 3M