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.
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.
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.
I set up a Google Maps v3 at our website at http://wallawalla.tk/services and I encounter a minor distortion issue. That is, if you look at the map very precisely, you'll see that there are random "white/gray stripes" appearing. Most important at the very left side of the map and especially when opening InfoWindows respectively closing them. It appears that "white/gray stripes" are somehow related to the border of the InfoWindow, i.e. it seems that if one of the borders doesn't show up (most of the time at the very left side of the respective InfoWindow), there is a random "white/gray stripe" appearing near or even through the InfoWindow. Unfortunately this isn't reproducible 100% of the time which makes it even more suspicious to me. Please try to open/close some of the InfoWindows to actually see it. I guess it is somehow related to our CSS. I read a lot about related distortions but nothing seem to fit my specific case. The "white/gray stripe" on the very left side of the map itself is reproducible almost 100% of attempts trying to reproduce. All "white/gray stripes" are 1px in width and they disappear if you either pan the map or scroll it out and back into the viewport of the Browser window. I'm testing with Google Chrome 22.0.1229.79/Webkit.
Doesn't seem to affect FF11.0/Gecko. Tried it just yet and while Chrome shows described behaviour, FF doesn't
My guess is that it is being caused by OverlappingMarkerSpiderfier. Can you build a simple test that displays your points and InfoWindows without using OMS and see if you still have the issue?
For some reason, the arrow on the tooltip for each graph point appears below the actual label(see image). I have tried doing everything to move it and can not figure out why this is happening. The tooltip is generated automatically by dojo's chart library. It appears fine in the demos.
Does anybody have an idea why?
EDIT:
I am using Dojo 1.7.2.
The code is question is
this.linePlotName is part of the object that the method below resides in.
var anim = new dojox.charting.action2d.Tooltip(newLineChart, this.linePlotName);
I had the same issue after I upgraded my Dojo from 1.6 to 1.7.2, but this issue was actually a bug and it is fixed now in 1.7.3: http://bugs.dojotoolkit.org/ticket/15016
Upgrade and it should be fine.
It's hard to say, without seeing what else is going on in your code. However, it's important to keep in mind that the tooltip's behavior is influenced by the widget/div/frame it's contained in. If there's not enough room to render the tooltip graphic on top of the plot line, it will be drawn under it. Try increasing the size of the container the chart is contained in, and try increasing the size of the chart itself, so there's plenty of room above the plot line for the tooltip to appear, or even try just scrolling up/down. It's best to rule out the easy fixes first. :) If that doesn't work, please comment, and we can go from there...
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.