I was looking in to that last year. With a few extras to set SDK level, code signing and the correct Simulator for that. Involved querying instruments to get various bits of information.they are changes to the IOS builder.
Dear Cerberus X User!
As we prepare to transition the forum ownership from Mike to Phil (TripleHead GmbH), we need your explicit consent to transfer your user data in accordance with our amended Terms and Rules in order to be compliant with data protection laws.
Please read the new Terms and Rules below, check the box to agree, and click "Accept" to continue enjoying your Cerberus X Forum experience. The deadline for consent is April 5, 2024.
Do not accept the amended Terms and Rules if you do not wish your personal data to be transferred to the future forum owner!
Accepting ensures:
- Continued access to your account with a short break for the actual transfer.
- Retention of your data under the same terms.
Without consent:
- You don't have further access to your forum user account.
- Your account and personal data will be deleted after April 5, 2024.
- Public posts remain, but usernames indicating real identity will be anonymized. If you disagree with a fictitious name you have the option to contact us so we can find a name that is acceptable to you.
We hope to keep you in our community and see you on the forum soon!
All the best
Your Cerberus X Team
I was looking in to that last year. With a few extras to set SDK level, code signing and the correct Simulator for that. Involved querying instruments to get various bits of information.they are changes to the IOS builder.
NICE! Much more enhanced then mine.I was looking in to that last year. With a few extras to set SDK level, code signing and the correct Simulator for that. Involved querying instruments to get various bits of information.
MAybe we could collaborate on that part later this year. Right now I won't have much time for it. Should finish other things first.@iOS: Only problem I have now it that my Apple hardware is just too old to work and test with. I could push it to Xcode 8.2 and iOS 9, but after that it would be pot look.
Sounds like a plan. I will dig out the code and clean it up a bit and upload it as a separate git project so not to mess up any main branches.MAybe we could collaborate on that part later this year
I know that feeling. I've got the VS C++Tool compiling with added icons for both MinGW and VS. Just got to work out what's wrong with the rebuildall script for Window when dealing with VS. Then the next task is to knock up a simple resource tools. I think I will just go for the quick and dirty for Window and get the end use to make their own .ico file with instructions on how to set up an icon folder for use.Edit: Of course, something I changed on my OSX version is not working on windows regarding the AGK target. Back to the drawing board.
if(!((t_var).Length()!=0))
The main things are out of the way. With the restructuring, C++Tool MSBuild and icons. There's still:Sounds like you are done with your changes, or?
Name der fehlerhaften Anwendung: Ted.exe, Version: 0.0.0.0, Zeitstempel: 0x5b6180e4
Name des fehlerhaften Moduls: Qt5WebEngineCore.dll, Version: 5.9.2.0, Zeitstempel: 0x59d389c7
Ausnahmecode: 0x80000003
Fehleroffset: 0x0000000000930b29
ID des fehlerhaften Prozesses: 0x1940
Startzeit der fehlerhaften Anwendung: 0x01d42b4ab63e0ad9
Pfad der fehlerhaften Anwendung: C:\Users\mike\Desktop\cerberus-preview\bin\Ted.exe
Pfad des fehlerhaften Moduls: C:\Users\mike\Desktop\cerberus-preview\bin\Qt5WebEngineCore.dll
Berichtskennung: 88f297bf-922b-43df-ae39-b005774cb2d1
Vollständiger Name des fehlerhaften Pakets:
That error there is pointing to QWebEngine it could mean that QWebEngineProcess.exe failed to start or there are multiple processes of QWebEngineProcess, a resource is missing, or a path problem (qt.conf in the bin directory may interfere with paths), or from what I've seen around a few others having a similar issue, video driver related. I would think that it would be worth checking out what processes if any are hanging.Name der fehlerhaften Anwendung: Ted.exe, Version: 0.0.0.0, Zeitstempel: 0x5b6180e4
Name des fehlerhaften Moduls: Qt5WebEngineCore.dll, Version: 5.9.2.0, Zeitstempel: 0x59d389c7
Ausnahmecode: 0x80000003
Fehleroffset: 0x0000000000930b29
ID des fehlerhaften Prozesses: 0x1940
Startzeit der fehlerhaften Anwendung: 0x01d42b4ab63e0ad9
Pfad der fehlerhaften Anwendung: C:\Users\mike\Desktop\cerberus-preview\bin\Ted.exe
Pfad des fehlerhaften Moduls: C:\Users\mike\Desktop\cerberus-preview\bin\Qt5WebEngineCore.dll
Berichtskennung: 88f297bf-922b-43df-ae39-b005774cb2d1
Vollständiger Name des fehlerhaften Pakets:
Well the compressed archives are previews for testing the binaries, but you can test out the build scripts. But the git deploy bit in the scripts won't work as the pre-built stuff I've linked are meant for the end user. And I've not updated the my git repo yet with the current updates with single instance Ted.Mmmh, regarding testing. Simple execution or the build scripts too? Because with later, I will fuckup all building stuff to the current version, or?
Best make sure that everything I've been working on works and is stable. Best keeping what's current and releasing the stuff I've been working on as alpha/beta tests.I think I should get that out first and then prepare the whole system to use your stuff.