I followed the Bugtracker tutorial on the Uno Platform page
For some reason even simple text boxes don't seem to get rendered correctly on the Skia.Gtk backend. This is what the final example is supposed to look like:
Here's what I see with Skia.Gtk:
The description box is supposed to contain some text and label on the slider isn't showing either.
I get no pertinent warnings or errors, which makes it difficult to pin down the source of the problem. I've run the sample on WSL (running Ubuntu 18.04) as well as a real Debian buster machine. Reassuring is that the GUI renders the same on both.
Got in touch with the maintainer and it turns out that TextBox isn't implemented yet. His reponse https://github.com/unoplatform/uno/issues/4578#issuecomment-731268315
That feature is on the roadmap for the upcoming release 3.4 scheduled to be released on December 4th... But it was previously planned for 3.2, so who knows
Related
I am experiencing an issue related to the displaying of any content within the JxBrowser, but only for 1 specific client PC.
The JxBrowser seems to correctly process the content that is sort of present, because if I click on an area where I know there is a link, the new page is opened (but not rendered too).
The "pages are not displayed" means that the content is completely white. Furthemore, the pointer is repetitively blinking between the normal arrow icon and the waiting circle, as something is going on in the background every about 1 sec.
A previous version of the application that embeds the JxBrowser doesn't produce the same problem.
Later on, I have also upgraded the JxBrowser version from the 6.23 to 6.24.3, but this did not solve.
Deleting any caches produced by the presence of the JxBrowser on the PC did not solve either.
What should I investigate to try and address this situation?
First of all, please note that JxBrowser 6 is no longer supported and it's a very old version based on Chromium 69. A lot of popular websites might not work properly in this Chromium version.
If the issue is reproducible only in a specific environment, then it's probably an environment-specific issue. If we are talking about rendering, then usually Chromium cannot render content when there's an issue with GPU drivers and the rendering mode (heavyweight or lightweight).
From our practice, disabling GPU very often helps in such cases. Please try passing the --disable-gpu switch and see if it helps. If it doesn't help, then the issue is probably in something else and additional research or even access to this environment is required. But again JxBrowser 6 is no longer supported.
As an option you can try JxBrowser 7 and see if it helps, but it's not that easy because this version has a new API which is not backward-compatible with the previous version.
Hi guys I'm new to Raspberry coding, for my three year thesis I'm writing a twitter wall application in javafx to be runned on a Raspberry Pi Model B+ v1.2.
I programmed it in eclipse neon under windows 10 and everything works correctly there, but when i moved the .jar on the raspberry initially it wasn't working at all. After a bit of googling i finally managed to make it work, i was on Raspbian Stretch with Desktop at that time and I only installed Gluon JavaFX Embedded SDK on my raspberry. After that the application started to run, a bit lagging and there was a problem with the input devices (which for me isn't really a problem because my app doesn't need any input from the user). The major issue is that whenever the app prints something on the terminal it shows up over the javafx app covering it.
After that i tried to install Raspbian Stretch Lite and after some steps i managed to make the app works, but with the same issue.
To make it works on Raspbian Stretch Lite i installed jdk8, gluon javafx sdk and xwindows (via sudo apt install xorg libgtk2.0-0).
I make a video of it to show you clearly what is the problem: (you can skip to 1 minute to see the issue)
https://drive.google.com/file/d/1EyvdpLuLnGwV3xrvgCqBU8e5T3go3-up
Hope someone can help me, thanks!
when searching the internet, i came across the TideSDK which I learnt was made for develoing desktop apps with HTML, CSS & Javascript. As an experienced web designer I downloaded it hoping to begin creating desktop apps with my HTML, CSS & Jscript experience immediately. But, that wasn't the case.
Immediately I launched it I saw just two buttons one to import, the other to create new project. Since I had nothing to import, i opt to create new project. After filling the spaces for project type(project type was fixed on desktop), name, app id, directory, company/personal URL,the Titanium SDK Version was left inactive ( I don't know why but i thought it was minor), I expected to see some spaces to write my codes but none. Rather after saving my changes, I brought to a 'console' which was also inactive. No cursor at all except some buttons with lauch app, kill app, package with Runtime, package without runtime which were all not yielding any result. Infact after clicking each of them, I still remained in the inactive console.
In my curiousity to get things working, I have done many researches on the net without a fruitful result. The best article I have gotten so far is from: http://seyekuyinu.com/how-to-set-up-the-tide-sdk-developing-desktop-applications-with-html5-css3-and-javascript/ but even that did not work fine. I downloaded the Tiv Community App which suppose to serve as the IDE but it could not be installed.The installer always stop on the way. I have tried to instal it on my home laptop and the office desktop but it could not be completed in any of them. Please if you want to reply to this question, i would love you to download the Tiv Community app and see what am talking about. I have also downloaded the helloworld from Github but when I try to import, it gives an error message something like "Importing desktop project, but not desktop SDK found in your system". I downloaded the desktopsdk-1.2.0.C4-win32 but the installer is not work - 'cannot locate application path'.
Please, am curious about this whole project and would appreciate any useful reply. I would also appreciate if TideSDK Developer team could write a comprehensive 'getting started guide' but the guide avaiable now is not meeting up with our curiousity for getting started in SDK. Thanks
Checkout Getting Started Guide http://tidesdk.multipart.net/docs/user-dev/generated/#!/guide/getting_started
TideSDK's latest release version is 1.3.1-beta
You need to download the SDK from http://tidesdk.org and extract the same in appropriate directory as mentioned in getting started guide.
Symptoms: Running any iOS 5.1 application from Xcode 4.4 (and 4.4.1) will launch the iPhone simulator but result in a plain black screen. In the Xcode console, the message "error: Failed to attach process to id " is displayed, being different each time. Attempting to 'Stop' the application from Xcode does nothing, and only Force Quit will return Xcode to a working state. Pressing the 'Home' button on the simulator shows that the app was successfully installed. Sometimes, opening the app from the simulator will show the UI, but no console messages are displayed, even after manually performing 'Product->Attach to process.'
Attempted Solutions: Xcode 4.3.x was originally installed on Lion, working charmingly. The problem started at installation of Xcode 4.4 in early August, for a project which was working before. I upgraded to Mountain Lion, didn't help. I reinstalled Xcode, didn't help. I upgraded to 4.4.1 Aug 7, didn't help. I deleted all trace of Xcode data, running: find / -name '[xX]code' and deleting all super-folders where it seemed relevant. That (not surprisingly) caused some OS issues, since subsequently reinstalling Xcode just didn't work. I then did it again, reinstalled Mountain Lion (to restore some OS files I probably killed), then reinstalled Xcode 4.4.1.
For projects, I typically ran new, single-view projects each time. Lately I've tried using this sample project from Apple, per link 3 below. I tried all the clean builds, etc., but honestly, one would assume opening a fresh project should just work. Just for kicks, I put a single 'Label' object in the iPhone storyboard at times.
After doing some homework I managed to find the following questions most similar to mine, but none are exact nor do any of the solutions work (in order of decreasing relevance):
xcode-4-4-ios-5-1-simulator-problems
crash-of-xcode-4-4-for-mac
failed-to-attach-to-process-id-xcode
unit-test-target-doesnt-run-on-xcode-4-5
xcode-4-4-freezing-on-project-close
simulator-keeps-crashing-in-xcode-4-4
Any help would be greatly appreciated. I apologize for the lack of brevity, but I've spent probably 15 hours trying to find/implement solutions to a seemingly trivial problem, and I would rather provide all relevant information than to have you guess at what I did. I'm not going to specify all the build info, just because it's whatever comes stock on the fresh install of Xcode.
I had similar problem (although with different configuration) and found incredibly simple solution by chance. I just used Product->Stop, then Product->Run (through keyboard shortcuts if that matters). Just once! Then the problem disappeared.
configuration: XCode 4.2, iPhone Simulator 5.0
symptom difference: process attaching didn't fail
It seems to me that the problem stems from the XCode-Simulator communication, and that's why I've shared my experience here despite the differences.
EDIT: It comes out Stop; Run didn't provide permanent solution for me. The problem is recurring from time to time. Still it is a temporary workaround for me.
I got this a few times, especially when I kept running my app and cancelling it or interrupting it too often, it's not something you can put your finger on, but yes I always managed to get back up and running by deleting the app in the simulator, cleaning project and build folder, deleting derived data (in Xcode organiser > projects view), restarting simulator and Xcode.
This also happened a few times on the device, and I needed to restart the device, iPhone in my case. I hope these infos help you out.
I got this to work by building and running the simulator using the Xcode 4.5 developer preview. I then closed it out and reopened Xcode 4.4.1 and it built and ran fine.
While none of the solutions above worked for me, thanks for putting this all together. I figured I'd answer here since this was the most comprehensive.
While this isn't exactly a solution, after today's OSX 10.8.1 update from Apple, this issue has been resolved. It's safe to say that some bug arose in the process of installing Mountain Lion and Xcode 4.4 that was fixed with this update to OSX.
I think I've cracked this one for my particular case, and I admit it's somewhat a mistake only newbies should do but I had overrided
viewWillApear:(bool)animated {}
in a ViewController of mine, without calling back
[super viewWillApear:animated]
It might be a good idea to search for all view lifecycle methods in your project and see if you have similar problem.
I have this jailbroken iPhone 3G with iOS version 4.2.1 (the latest supported version). When I connect it to Xcode 4.2, Xcode starts copying the debug symbols. It stops copying towards the end of the process, and shows the following error:
Xcode has encountered an unexpected error (0xC002)
No such file or directory, at ‘/SourceCache/DTDeviceKit/DTDeviceKit-867/DTDeviceKit/DTDeviceKit_Utilities.m:864’
Anybody experiencing anything similar?
I know I should try and restore the phone, but I'm asking just in case anybody can come up with a solution that doesn't involve restoring it.
In this post on mactechnews.de, one guy reports the same problem -- with no solution, so far.
Alright, after a lot of testing and digging up the filesystem... I solved it.
It turns out that there are just a few files that are not downloaded from the device (for reasons still unknown). They are related to the dyld cache (don't really know what this is and what it's for). Here are the steps to make your 4.2.1 device debuggable in XCode 4.2 and 4.3.x:
Close Xcode
Go to: ~/Library/Developer/Xcode/iOS DeviceSupport/4.2.1 (8C148)/Symbols/System/Library/Caches/com.apple.dyld/ Note: if you don't have this folder, run Xcode, connect your device, and wait until the error 0xC002 appears in Organizer - the folder should be created by that time.
Create 3 empty files there called:
.copied_dyld_shared_cache_armv6
.processed_dyld_shared_cache_armv6
dyld_shared_cache_armv6
Run Xcode and enjoy the light next to your device eventually go green:)
Or, for the terminal lovers:
cd ~/Library/Developer/Xcode/iOS\ DeviceSupport/4.2.1\ \(8C148\)/Symbols/System/Library/Caches/com.apple.dyld/
touch .copied_dyld_shared_cache_armv6
touch .processed_dyld_shared_cache_armv6
touch dyld_shared_cache_armv6
This is obviously a hack but it works perfectly for debugging and I haven't noticed any side-effects so far.
Enjoy!
Small update:
I tested it on my snow leopard hackintosh, with the Xcode 4.2 (most recent to date) and although the device is active in the organizer and it is possible to run the app on the device, i get black screen on launch. It gets installed but apparently debugger cannot get attached. I had the same problem with 4.0.2, when the 0xC002 problem didn't yet occur so I think it's unrelated and might even not happen to others. Nevertheless, 0xC002 is still solved.
On my main development machine with Lion and Xcode 4.3.2, device is perfectly debuggable.
The answer above (https://stackoverflow.com/a/9944892/1390251) works, basically,
but for newer versions of Xcode you probably need to rename the files as follows,
having them end with '7' instead of '6':
touch .copied_dyld_shared_cache_armv7
touch .processed_dyld_shared_cache_armv7
touch dyld_shared_cache_armv7
If not sure, you can keep both sets of files (...6 and ...7)
in the relevant folder (can also be 5.1.1 for that matter)
and it should work.
(have tested it on iPhone 4 with iOS v5.1.1 genuine)
It seems that you cannot debug apps on iOS 4.2.1. I tried several restores to iOS 4.2.1 with same effect. Downgrading to iOS 4.0 was the only thing that worked.
The reason for whole problem is that iOS 4.2.1 is not supported in XCode, according to this website.
Error in Xcode getting debugging info from 5.0.1 iphone
solved, see the link to archive with iOS5.0.1 debug info
download & unpack to "~/Library/Developer/xCode/iOS DeviceSupport/" & be happy =)
I fixed this bug in![enter image description here][1] this way:
I duplicate the 5.1.1(9B206), rename it to 5.1.1(9A405)[my ios device is this version], then the error is gone.