I've used Codepro for dependency graphs before and I like it. It is unsupported and discontinued. Why?
My (real) question is that I've installed the Indigo 3.7 version (it wouldn't work on Eclipse 4.2 so installed 3.7 just for this purpose) and it does its dependency analysis as expected. However when I drill in a level the picture is far too big but there seems to be no way zoom out.
I tried a font-size change plugin and that doesn't work.
Does anyone know how to zoom out/in or could suggest plugins that might achieve this?
Maybe you cannot zoom in or zoom out the dependency graph, but you can right click on the graph, select 'Explore graph' and select 'As Image' to obtain the image of the graph. The image could be zoomed in and out as needed :P.
Related
We are experimenting with using OpenLayers within a PHP application that displays data from PostgreSQL/PostGIS and GeoServer.
The initial use of OpenLayers is terrific except for one problem:
A lot of our data has very small extent eg < 0.1m.
When we zoom in to look at the features they disappear.
We have read the documentation, looked for examples, tried setting zoom values > 19 but to no avail.
There are NO scale thresholds in the SLD so this is not the issue.
Can anyone suggest how to get around this? Is there a NO-LEVELs mode for OpenLayers as we are not interested in mimicking Google Maps etc.
I am using chrome dev tools memory tab to isolate a memory leak in an application. When I look at the snapshot of the JS heap, there should be a way for me to distinguish which pieces of data DO NOT have direct references as indicated by the docs – these were highlighted in red (https://developers.google.com/web/tools/chrome-devtools/memory-problems/).
This issue explains why there are no colors, and instead there should be icons (Chrome Heap Snapshot -- no colors for detached nodes).
Now, the issue I am having is that the icons that should be there are rendering as just a box 🗖.
I have tried the solutions listed here: https://support.google.com/chrome/forum/AAAAP1KN0B0QyAwmbsj7iU/?hl=en&gpf=%23!topic%2Fchrome%2FQyAwmbsj7iU
Nothing seemed to work for me. I DO have adobe create cloud, but nothing was running at the time, and I did not have the option to manage fonts as described in the most popular solution.
I should get an icon describing the data's heigher archy in the heap.
I know this is an old issue but I just run into this myself. The way I fixed it for me was to install Unicode Fonts for Ancient Scripts (ttf-ancient-fonts package in ubuntu) and then restart Chrome. After that I was able to see the icons properly.
I have red-blue-coloured edges.
It is bad for me.
How to configure SDK to get rid of it?
I started samples (Tiny room).
But shaders are somewhere else (possibly in dll, so I cant fix them).
edit 1)
Tiny room demo is working.
I have unpleasant effect of distortion that made by program.
It is aimed to prevent chromatic abberation, but it make it worse.
Or I need some kind of red-blue glasses in addition to Oculus ? (it's ridiculus, but I must to ask)
There is two bad solution.
1) The problem can be solved by using different copy of the product.
2) There is also possibility of switching off the whole image distortion in Oculus SDK in modules which contain OpenGL- or DirectX-specific commands.(but it also disables the barrel distortion)
I want to draw line on Firebreath Plugin. While searching I have came acrossed this Link where FB::Rect is used to display text. I also tried for FB::Line but not available. Should I use D2D1 with Firebreath?
Please let me know for the same.
You have not sufficiently read the code to understand what is going on. FB::Rect is just a structure containing dimentions. Drawing in FireBreath is just using the appropriate platform APIs to draw. On windows that means GDI. Learn to draw a line using GDI and you'll be able to draw with FireBreath on windows.
I am reaching out because I feel like we can't be the only ones who are experiencing this problem, however right now based on my research I feel quite alone!
Last night I got the android update (4.3) on my HTC One which I installed right away. Now the app we developed with Sencha Touch + Cordova hardly functions at all. This is after a successful submission to the app store and successful testing in multiple android devices.
Some of the issues we are experiencing:
Back button in list view no longer responds
Page transitions (left->right and right<-left) functioning bizarrely. For example the title transitions right to left while the body left to right, simultaneously.
The title on our home screen suddenly reverting to "undefined."
I know probably all we need to do is get back to the emulator and just start debugging, but we really would like to know whether anyone else has experienced problems like this and could help point us in the right direction on some solutions.
Also the problems persist after updating to the very latest version of Sencha Touch 2.3 which has Cordova integrated.
The following patch resolves the issue!
http://www.sencha.com/forum/showthread.php?273492-Back-button-broke-in-navigationview-Sencha-Touch-2.3-Android-4.3&p=1009111&viewfull=1#post1009111
Looking forward to seeing this implemented in the next Sencha Touch update.