Downloaded the testScrollView file and can't get it to work right.
https://github.com/C4Code
It seems everything is in order for the most part, no major errors pop up or anything, but when I try to run it on the simulator it pops up in the bottom right saying "destination buffer size too large (15360 x 768); cannot be larger than 4096 x 4096", and the debugging window pops up as well.
Is there some sort of special command that needs to be added?
I ran into this issue last week, apparently the simulator doesn't like the large image. However, this example works just fine on a device. The reason is that there is a large 15360x768 image that the example breaks down into 256x256 tiles.
Try compiling for an iPad if you have access to one.
Related
As you can see in the images I provided, the upper left menu options text is huge. I don't know why this is, I think I updated Qt and then suddenly it looked like this the next time I ran it. I have tried to search for solutions for how to get regular size back but I find pretty much only things related to code font size. Does anyone know how I can get back the original, much smaller and easy-on-the eyes text size?
This is a bug in QtCreator 9.0.0. It will be fixed in version 9.0.1. which will hopefully come out soon. If you do not want to wait, you can download and install some snapshot of QtCreator 9.0.1. here https://download.qt.io/snapshots/qtcreator/9.0/9.0.1/ See also https://bugreports.qt.io/browse/QTCREATORBUG-28499 for some other workarounds.
I've been using Bokeh for years and just updated to 2.1.1, and I can't get the SaveTool in the toolbar next to plots to work properly anymore. Instead of downloading the entire image, it downloads the upper left corner and omits everything else. The ubiquity of the phenomenon is a little overwhelming. It happens in all browsers, in all the Jupyter notebooks I use, in all HTML outputs. However, if I revert to an earlier version everything is fine.
As for code, I can even generate the problem at docs.bokeh.org in a single Chrome browser:
Here I get the entirety of the first plot on the page:
https://docs.bokeh.org/en/1.0.0/docs/gallery/image.html
Here I just get the upper left corner of the first plot on the page:
https://docs.bokeh.org/en/latest/docs/gallery/image.html
Can anyone explain why this is happening and how I can stop this behavior?
This is a bug. The fix is already in the release branch and will be part of the next release.
I'm using a PiTFT on my pi and running a JavaFX program. I got the output going to the PiTFT by running fbcp in the background.
I had to set disable_overscan=1 in /boot/config.txt to get it to show the whole image. That all works fine now.
My problem is that the touch screen calibration doesn't seem to effect JavaFX apps. The X and Y axis are swapped. Does anybody know how to calibrate the touch screen for JavaFX apps?
I don't know if this is a problem with the touchscreen driver for the PiTFT or a JavaFX configuration problem, so I'm going to post the same question to the adafruit forums and if I get an answer in one place, I'll copy it to the other.
I've struggled with the same problem today, and I managed to figure it out.
The PiTFT is by default a portrait display with a resolution of 240x320. The driver conf is originally made to rotate the display. The touchscreen setting for X are aware of that and have the rotate option set accordingly. And yes, this will not affect JavaFX since it doesn't run in X.
What I did:
in /boot/config.txt
disable_overscan=1
framebuffer_width=480
framebuffer_height=640
#set specific CVT mode
hdmi_cvt 480 640 60 1 0 0 0
#set CVT as default
hdmi_group=2
hdmi_mode=87
hdmi_force_hotplug=1
With this, the main display resolution is set to 480x640, and overscan is disabled.
Next, in /etc/modprobe.d/adafruit.conf, change the rotate option to be 0.
Save everything and reboot. Then fbcp & java Main, and it should be working OK.
Btw, be aware that I used the pre-built raspbian image from adafruit.
Now i am using macbook pro with 13 inches.
Yesterday i upgraded XCodes version to 4.3.2.
In that iPad Simulator is too big and iPad Retina Simulator is also too big.
It's not fix my screen.
iPad Retina Simulator size is take all of my screen and it's can only show iPad's dock.
I can't see overview iPad screen.
I always scroll down and up to test.
When i change Simulator's Window > Scale into 75 %, It's still too big.
50% is too small and can't see anything clearly.
When i develop with XCodes 4.2 , iPad Simulator is fix size and okay to test.
I want iPad simulator size fix my screen.
Is there anyways?
If my question is out of question, so sorry for that.
Thanks.
Maybe it's because the iPad 3 have a really large resolution (2048x1536). That's more than most computer screens. You will need to zoom out to display the entire screen just because of this, or you must get a larger (higher resolution) screen for your computer if you don't want to scale the program.
The reason for this is that the iPad 3 have much tighter pixel density than most other computer screens so each pixel on the iPad is smaller than each pixel on your computer screen.
What you can do is make the simulator start by suppressing the title bar and your dock if it happens to be shown.
Follow these steps, please be responsible and back-up your files before editing anything as I do not take responsibility for things going wrong.
Before you start close any running simulators.
In Finder Press CMD+SHIFT+G and enter the folder /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone Simulator.app/Contents/; this folder may differ for you depending on your location of the simulator/SDK.
Backup the file called Info.plist
Copy Info.plist to your home directory.
Double click Info.plist in your home directory. You will be presented with the plist editor.
Select the first entry called Information Property List and click the plus (+) sign immediately to the right.
Enter Application UI Presentation Mode into the Key field of the new entry, tip: it will auto populate after typing Application UI.
Enter 4 in the Value field, this will then change to All Suppressed.
Save and close the file.
Replace the original plist file with this new one, remember to back the original up first.
Now when you run the simulator it will not show the menu bar when it becomes active. The reason you needed to copy the file to your home directory is because you do not have write permission to it. It also stops you mucking it up and preventing the simulator running while editing the file.
You can apply this trick to any application by finding it's plist file, thus I also change Xcode.app to do this too.
You will need to scale the simulator to 75%, however it will now be almost the full height of the screen with no loss of the iPad window.
Now It's more flexible with Xcode 9- Simulator. You can pick & drag any corner or simulator to resize it and set it according to your requirement.
Look at this snapshot.
https://apple.stackexchange.com/questions/205865/ios-simulator-screen-size-not-equal-to-window-size
My Xcode has suddenly began to display unreadable text in the source editor. No other apps are affected. It is most notable with white/bright-colored text on a black background but it occurs in every theme.
The text looks like the the background is bleeding through the foreground text characters. It doesn't really look like "the jaggies" that you used to see with bitmapped fonts.
Here is s side by side comparison between Xcode and the terminal using the same orange on black theme, at the same font of Menlo 12. Even in the reduced resolution screen shot, the difference is obvious. On screen, the terminal text display is crisp and easily readable while the Xcode text is barely readable and, as a practical matter, useless.
I don't know when the problem may have started because I haven't been working in Xcode recently. The only change is that I added a second monitor to my dev box but removing the monitor did not resolve the problem.
I tried using the com.apple.dt.Xcode defaults to set the anti-aliasing of Xcode to 24 point but that too had no effect.
I'm stumped. My next step will be to reinstall Xcode but I was hoping someone else may have hit this problem before and has a neater resolution.
A reinstall of Xcode resolved the issue. Haven't the foggiest why.
Update:
This answer over at Ask Different might be relevant as well.