I wish you did the same for OSX. There way too many plugin files generated for a simple app that uses MBS.
It does lengthen the verification process on macOS considerably.
I tried this afternoon and it works perfect with regular strings.
Still having issues with strings that have been set with DefineEncoding though.
With the build-in Split, the errors were random. I didn’t have time to check if the errors were consistent. If they are, I’ll try to forward an example within the next few days.
I mean without using DefineEncoding. I think they’re otherwise UTF-8 by default no? Or that’s what I always thought,
But what I saw after a quick compile:
With the build-in Split:
If I don’t use DefineEncoding, all goes ok on 32-bit but randomly wrong on 64-bit.
If I use DefineEncoding (Greek, Arabic etc.) all goes ok on 32 bit but it goes wrong at the same points on 64 bits (black diamonds).
With SplitMBS:
If I don’t use DefineEncoding, all goes ok on both 32-bit and 64-bit.
If I use DefineEncoding (Greek, Arabic etc.) …
It went wrong on 64 bit (black diamonds) but not sure if it was random, always at the same points or at the same points as the build-in Split.
I didn’t test if it went wrong on both 32 and 64 bit