Page 2 of 2
Re: XPorter and migration - complicated situation
Posted: Mon Apr 21, 2025 8:47 am
by wriedmann
Hi Chris,
there is another one I need often:
Code: Select all
TEXTBLOCK VXP-TOP
using WrikeHelper
Wolfgang
Re: XPorter and migration - complicated situation
Posted: Mon Apr 21, 2025 9:29 am
by Chris
Hi Wolfgang,
wriedmann wrote: Mon Apr 21, 2025 8:47 am
there is another one I need often:
Code: Select all
TEXTBLOCK VXP-TOP
using WrikeHelper
Ah, right, thanks, will also include it in the docs!
Re: XPorter and migration - complicated situation
Posted: Mon May 26, 2025 10:26 am
by Chris
Hi Wolfgang,
wriedmann wrote: Mon Apr 21, 2025 5:38 am
For the moment I will use the {VOXP:DEL} tag to solve that issue, but a possibility to ignore the file (or better: to not change it) would be very helpful.
Here's an update to VOXporter that supports the "{VOXP:NOCHANGE}" (and "VXP-NOCHANGE") tag, for not changing a module at all:
https://www.dropbox.com/scl/fi/u8xvgmk5 ... 4plma&dl=0
The tag can be placed anywhere in a module code, but preferably in the beginning, so it's more obvious. Can you please give it a test when you can to see if it works as you'd expect it?
Re: XPorter and migration - complicated situation
Posted: Mon May 26, 2025 11:37 am
by wriedmann
Hi Chris,
thank you very much!
Will try it out hopefully this week (I will be away next week for holiday).
Wolfgang
Re: XPorter and migration - complicated situation
Posted: Tue May 27, 2025 8:05 am
by wriedmann
Hi Chris,
I have tested that now, and it works very well, thank you very much!
Wolfgang
Re: XPorter and migration - complicated situation
Posted: Tue May 27, 2025 9:03 am
by Chris
Hi Wolfgang,
Great to hear, thanks for your answer!
Re: XPorter and migration - complicated situation
Posted: Tue May 27, 2025 9:04 am
by wriedmann
Hi Chris,
I have to say "thank you" for your continued support and work!
Wolfgang