I understand that “pc hardware” and various drivers could result into some odd complications. To me this fresh setup of a Pi 4 doesn’t look like an “odd set of circumstances”… so what could be the difference? There has to be one… Same if I build the app and run it on the Pi4. RemoteDebug - and boom - app dies on the Pi4, as soon as any PageSetup or Printer Dialog should be shown. Installed all updates, then installed Xojo’s RemoteDebugger, loaded an example project of Xojo (any of the printing ones) on macOS. Put it in the Pi 4 (4GB), setup with defaults (even configured to default US/English, to rule out possible european countries/localization issues). I have just flashed a Micro SD using Etcher with the latest available Raspbian Buster. My point is not to say that it’s not happening, but there has to be some odd set of circumstances involved to cause the error. I’ve also tried on 2 rPI 4’s (Raspbian) with no error. We can just let them know that this is important to us. And the more are requesting the case to be looked at again, the more likely it is they consider it once more - even though having closed it twice already. That way Xojo at least gets to know what is not working. You could ask the feedback://showreport?report_id=54807 to be reopened - providing information about Distribution/GTK3-version. While I don’t know if you’re having the same issue, it sure seems like it. And a shiny new HiDPI capable one compiled with 2018r4 for the others. A GTK2 one compiled with 2016r3 (for the “older Linux distributions” that may have this issue when printing). Not even a fix to not crash with a Segmentation FaultĪnd… for this very reason, we’re currently providing two Linux 32Bit builds. It seems that Xojo is not willing to fix this. Even just try-catch-do-nothing is better than crashing - since users of Xojo built applications may loose unsaved data…īut again… closed. Just a try-catch (in case of error: MsgBox) in that Framework function. I’m just asking to have the framework not crashing with a Segmentation Fault. I then have added another Feedback: feedback://showreport?report_id=54807 Since Xojo has closed that report: “ the behavior described is not a widely reproducible bug and in most distros this is not an issue, only affects certain configurations it seems.” This happens only with certain distributions: Ubuntu 14.04.5 LTS, Debian 8 (and possibly others). Xojo built 32Bit GTK3 apps may hard crash (with a segmentation fault) when trying to print. This is a known issue: feedback://showreport?report_id=48750 Linux, GTK3: Printing crashes the application There you find the 32-bit macOS plugin.What distribution are you using? And more specific: What GTK3 version does it have? Do you build for 32Bit or 64Bit? Older plugins versions can be found in our Archive. This way you always have latest plugins on your computer.
Once you have an account, you can email us, so we add you to our shared plugin folder.
With a trial key, you can test the plugin without an annoying dialog asking for a license.ĭo you use Dropbox? If not get an account here for free. You can request a trial key here: Request Form
Looking for demo/trial? Simply download and try plugin without license key in demo mode. You can download them here: The latest supported Visual C++ downloads or direct download.
The 64-bit version of MBS FileMaker Plugin for Windows needs the Visual Studio Runtime Libraries from 2019. You can calculate this with openssl in Terminal using "openssl sha256 -hex " followed by the path to the file. Download Download the MBS FileMaker Pluginīoth archives contain the macOS, iOS, Windows & Linux plugins.