I just upgraded to a new laptop w/ a UHD 4K display.
It looks beautiful, but my Chaco plot labels are now illegibly small.
I could solve the problem for myself, by increasing the font size of these labels, but then they would appear too large to people running the same application on standard resolution displays.
How can I automatically detect and adapt to a particular display resolution in my Chaco plotting application?
As per #Alexandre\ Chabot, below, I do appear to be using Qt 5:
$ conda list qt
# packages in environment at C:\Users\capnf\AppData\Local\Continuum\anaconda3\envs\pybert-dev:
#
# Name Version Build Channel
pyqt 5.12.3 py38haa244fe_7 conda-forge
pyqt-impl 5.12.3 py38h885f38d_7 conda-forge
pyqt5-sip 4.19.18 py38h885f38d_7 conda-forge
pyqtchart 5.12 py38h885f38d_7 conda-forge
pyqtwebengine 5.12.1 py38h885f38d_7 conda-forge
qt 5.12.9 h5909a2a_4 conda-forge
So, how do I "tweak" Qt, to enlarge the font sizes of my Chaco plot index and value axes?
Or, better yet, how do I "coax" Qt5 into displaying things in a DPI-independent fashion?
The screen resolution support is not part of Chaco but rather of the backend used to render the UI. I'm going to assume that you're using Qt, and not Wx. If it's possible for your project, I recommend upgrading to a Qt version that 5 or greater. Qt5 greatly improved the support for high-DPI screens.
Related
In the analytical designer, you can now change the configuration of the axes, legend, and canvas when creating an insight.
I know that the SDK supports setting the legend visibilty and position (https://sdk.gooddata.com/gooddata-ui/docs/chart_config.html) but is it possible to configure the axis and canvas in the same way as the designer?
all these configurations are available in latest alpha version and in 6.0.0-rc1 of #gooddata/react-components package, but it contains still few minor bugs. We plan to release final version of this functionality approximately in two weeks in 6.0.0 version including documentation and live examples
I have started using GNU radio and was following this YouTube tutorial series to get familiar with GRC.
While following along with the tutorials I noticed that I am missing many of the GUI widgets that the tutor was using, for example, the variable slider widget.
I realise that the blocks ultimately translate to some python code, and we could create our own widgets, but the issue is with missing default widgets.
It may be relevant to state here that the software was installed using the synaptic package manager following the instructions given here.
Is there a fix for this? Maybe some more packages available on Synaptic?
In your linked tutorial, I believe that wx widgets are used. These are deprecated and you should swap to a Qt gui top_block. To get the slider he used, you may stick to a WX GUI Slider or use a QT GUI Range block, depending on whether your flowgraph is in wx or qt
I am trying to use Kinect 2 and SDK v2 for capturing Infrared Images/videos.
Kinect shows Depth and RGB images properly, But when i try to visualize Infrared Basics in Kinect for Window. It does not show any image, rather a black screen.
What is the reason for it. I reinstalled SDK v2, but still the same problem. In a similar post some one suggested that reinstall a newer version, which I did. But still the same problem. Can any one suggest any solution?
thanks
it is better to use "KinectConfigurationVerifierSetup" for test system requirements. and i suggest you that use Infrared Basic-WPF Samples in SDK Browser, also you could use that sample code and install them to your computer. if still infrared data source not show, you could test Kinect on other computer
I fixed my problem by updating GPU Driver. It has a conflict/bug/error with older version. However Nvidia removed it. And if one install new driver, it start showing infrared images.
Attention for your graphics card setting, Maybe changing your computer to auto or Inter HD Graphics will work.
I am trying to use both bokeh and matplotlib in my IPython notebook... Neither work perfectly.
Attached is a screen shot of Bokeh. Matplotlib explanation is below.
Here are my system specs:
-Windows 7 with Vagrant
-Jupyter/IPython
BOKEH -- buttons are static images; there is no resizing, yet the graph is interactive
Should look like from this website: http://docs.bokeh.org/en/latest/docs/quickstart.html
MATPLOTLIB -- only static shots appear when it should be zoomable, etc (like bokeh)
1) read the documentation.
you would only change output_file() to a call to output_notebook() instead.
Which you did not seem to do above.
2) Why should it ? What di you do to make it zoomable ?
3) try not to post 2 unrelated question at the same time.
You appear to be using an older version of Bokeh. The issue with the CSS problems (button appearance) has been fixed for some time. As mentioned above, you will need to execute output_notebook() to load Bokeh for IPython notebook usage. For future reference, questions like this greatly benefit from providing as much information as possible (e.g., Bokeh and browser versions, platform information, etc.) Without that information it is impossible to diagnose problems with any certainty.
I was able to successfully port, cross compile and run the cairo gears
application in gles backend, on my embedded system target.
http://people.linaro.org/~afrantzis/cairogears-0~git20100719.2b01100+gles2.tar.gz
The ported samples trap, comp, text and shadow run well in cairo1.12.3
and 1.12.4.
But I face problem in running the same in 1.12.14.
I could not run the texture related samples like comp, text, shadow.
Trap plays well but the gradient could not be displayed in the gradient sample.
I use gles backend and converting all image surfaces I load from png
file to gl surface.
Let me know if there is something that should be done for the
texture+gradient samples to work in 1.12.14.
thanks
Sundara raghavan
The problem was because of the need to convert the GL_BGRA,the internal image format of cairo , to GL_RGBA for loading in to GL textures (which were GL_RGBA by default). I solved it by applying an existing patch which uses BGRA GL texture and hence avoids conversion. This was possible because my hardware is capable of both reading as well as creating bgra textures.
The Patch was found here:
http://lists.freedesktop.org/archives/cairo/2013-February/024038.html