03-07-2023, 08:33 AM
But this should be if you're using an "$UNSTABLE" feature, or if you're using a keyword/function that was added in a later version/release of QB64PE. Less likely, this could happen if you had been using the "dot-rip" or the "qb64-dot-com" edition of QB64 and then switched to Phoenix Edition v3.1 or later.
Now asking the system to acquire a library is not that easy, would need another maintainer for this project. The error message in the screenshot posted just above is vague: is it asking for a BI/BM file, or a DLL/SO? It is only telling the user to upgrade to a later version/release of QB64PE.
Indeed this might be triggered by "$UNSTABLE", but we'll need to consult with DSMan195276 or another of the developers.
Now asking the system to acquire a library is not that easy, would need another maintainer for this project. The error message in the screenshot posted just above is vague: is it asking for a BI/BM file, or a DLL/SO? It is only telling the user to upgrade to a later version/release of QB64PE.
Indeed this might be triggered by "$UNSTABLE", but we'll need to consult with DSMan195276 or another of the developers.