similar to: Tinc graph and label info.

Daniel, muchas gracias por contestar y tan rápido. Pues puede ser la solución, he hecho el cambio y sigue sin pintarme los puntos -> data_ <- toJSONArray(data_, json = F) map$geoJson( # leafletR::toGeoJSON(data_, # # lat.lon = c('Lat', 'Long'), # dest=output_geofile), data_, onEachFeature =

Hola, Ando un poco desesperado con los mapas interactivos de Rcharts <https://github.com/ramnathv/rCharts>+Leaflet. Estoy intentando pintar en un mapa las cámaras de tráfico de madrid, y las estaciones de calidad del aire, simplemente donde están, es decir, aun no estoy recogiendo los datos de medida. Proyecto -> https://github.com/ADIRSE/maddata He conseguido pintar ambos, con

I am trying to understand how bundler works. Looking at the manual [1] it says "If a Gemfile.lock does exist, and you have not updated your Gemfile(5), bundler will fetch all remote sources, but use the dependencies specified in the Gemfile.lock instead of resolving dependencies." The question is how does it know whether Gemfile has been updated? I expected to find something in

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

Using Rgraphviz, I draw the undirected graph with vertices A,B,C and D and edges A:B, B:C, C:D, D:A, A:C. I want the vertices A and B to be red and C and D to be blue. The problem is the following: I want the edges A:B and B:C to be green and the edges C:D and C:A to be yellow, while the edge A:C can have the default colour black. I assume that I have to specify this using the edgeAttrs-argument

On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > The current way of handling refcounting in the DP MST helpers is really > confusing and probably just plain wrong because it's been hacked up many > times over the years without anyone actually going over the code and > seeing if things could be simplified. > > To the best of my understanding, the current scheme

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

On Tue, Dec 18, 2018 at 04:27:58PM -0500, Lyude Paul wrote: > On Fri, 2018-12-14 at 10:29 +0100, Daniel Vetter wrote: > > On Thu, Dec 13, 2018 at 08:25:32PM -0500, Lyude Paul wrote: > > > The current way of handling refcounting in the DP MST helpers is really > > > confusing and probably just plain wrong because it's been hacked up many > > > times over the

This is the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream implementation requires a

This is a WIP version of the series I've been working on for a while now to get all of the atomic DRM drivers in the tree to use the atomic MST helpers, and to make the atomic MST helpers actually idempotent. Turns out it's a lot more difficult to do that without also fixing how port and branch device refcounting works so that it actually makes sense, since the current upstream

Good morning, I'm trying to draw a graph, and I'm using the following code. test.matrix<-read.table("~/Desktop/Results/testgephi.csv", header = T, sep=",") colnames(test.matrix) <- gsub("X", "", colnames(test.matrix)) #drop first column drops <- c("") test.matrix<-test.matrix[,!(names(test.matrix) %in% drops)] test.matrix

Hi All, After a lengthy battle just to get the package installed, I am not able to actually use Rgraphviz to generate any plots. I tried just using the sample code in the documentation (http://www2.warwick.ac.uk/fac/sci/moac/people/students/peter_cock/r/rgraphviz/) and I get the following: *> > library(Rgraphviz) > test.matrix<-matrix(rep(c(0,1,0,0), 9), ncol=6, nrow=6) >

Dear All, I think I have a useful idea for how shorewall startup could be speeded up in a more automatic manner. Apologies if this is daft, but I think it might work.... Motivation: not all users understand the intricacies of shoreall beyond using the distro setup tool. [And on this particular laptop, shorewall takes 15 seconds during boot.] I have already read this (about shorewall

Here are my patches to add extra shapes to the annotate plugin. I have also added dbus support and made a few things configurable. The new tools available are Line, Rectangle and Circle, the original is called Brush. There is no selection line at the moment because I do not understand OpenGL yet. Hopefully these patches can be added and something added later. There is an extra action called

Hi guys at mapstraction, I made a change in the Polyline.toMicrosoft() function, in order to have all the power that a VEShape has, for instance fill color. Below is the new code, if you want to use it, change it, or whatever. Cheers, Beta /** * toMicrosoft returns a Microsoft polyline * @returns a VEShape */ Polyline.prototype.toMicrosoft = function() { var mpolyline; var mpoints

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When

The current way of handling refcounting in the DP MST helpers is really confusing and probably just plain wrong because it's been hacked up many times over the years without anyone actually going over the code and seeing if things could be simplified. To the best of my understanding, the current scheme works like this: drm_dp_mst_port and drm_dp_mst_branch both have a single refcount. When