Show messages:
1-5
6-25
26-45
46-48
From: SPARTAN-D421 (SIERRA-D421)
Right, right. What I'm asking is how the programming handles that bit. Is there a specific file that contains the expiration date and relevant code? And if that's the case, can the files be modified?
Just curious.
(I'd also like to apologize if I seem like I'm not making sense. I struggle with phrasing my queries in a clear manner, as a neurodivergent individual.)
(side note: thanks for adding SVG import/export. I use MoI as part of my workflow for vector graphics and 3D animation, in addition to CAD. Adding SVG import/export makes it much easier, especially since I don't have to worry about any loss of data - and thus, potential loss of detail - when using intermediary formats like PDF like I used to.)
From: Michael Gibson
Hi Spartan,
re:
> What I'm asking is how the programming handles that bit. Is there a specific file that contains the expiration date and relevant code?
Yes, it's part of the code in the main program module file moi_lib.dll .
> And if that's the case, can the files be modified?
Yes, it's possible to do that, it's called "cracking":
https://en.wikipedia.org/wiki/Software_cracking
But usually it's done by people who are distributing pirated versions of the software.
- Michael
From: SPARTAN-D421 (SIERRA-D421)
Gotcha.
Admittedly, I had entertained the idea of cracking - though:
A.) I'd put the kibosh on the idea after thinking it through, and:
B.) it woulda been for personal use anyway had I cracked it,
so there's that.
That said, my line of thinking often goes toward "can it be done" more than "should it be done" and "what are the repercussions thereof" - hence my asking in the first place.
On an unrelated note, is there one more beta build after this, or is V5's public release the next release?
Show messages:
1-5
6-25
26-45
46-48
