search for: fillcolor

...eof (CompOption)) +#define NUM_TOOLS (sizeof (tools) / sizeof (tools[0])) + static void annoCairoClear (CompScreen *s, cairo_t *cr) @@ -143,6 +175,335 @@ return as->cairo; } + +static void +annoDrawCircle (CompScreen *s, double xc, double yc, double radius, + unsigned short *fillColor, unsigned short *strokeColor, + double strokeWidth) +{ + REGION reg; + cairo_t *cr; + + ANNO_SCREEN (s); + + cr = annoCairoContext (s); + + if (cr) + { + + double ex1, ey1, ex2, ey2; + cairo_set_source_rgba (cr, + (double) fillColor[0] / 0xffff, + (double) fill...

...layer.bindPopup(feature.properties.popup) } !#', pointToLayer = "#! function(feature, latlng){ return L.circleMarker(latlng, { radius: 6, fillColor: feature.properties.fillColor || 'blue', color: '#333', weight: 1, fillOpacity: 0.8 }) } !#") Un head(data_) ahora muestra esto -&gt...

...layer.bindPopup(feature.properties.popup) } !#', pointToLayer = "#! function(feature, latlng){ return L.circleMarker(latlng, { radius: 6, fillColor: feature.properties.fillColor || 'blue', color: '#333', weight: 1, fillOpacity: 0.8 }) } !#") donde mi variable data_, es la que con...

...tr(3,2),16),parseInt(this.color.substr(5,2),16), opacity); }else{ color = new VEColor(0,255,0, opacity); } mpolyline = new VEShape(VEShapeType.Polygon, mpoints); mpolyline.SetLineColor(color); mpolyline.SetLineWidth(this.width || 1); mpolyline.HideIcon(); if(this.fillColor){ var fillColor = new VEColor(parseInt(this.fillColor.substr(1,2),16),parseInt(this.fillColor.substr(3,2),16),parseInt(this.fillColor.substr(5,2),16), opacity); mpolyline.SetFillColor(fillColor); } return mpolyline; }; -------------- next part -------------- An HTML attachm...

...on/gpu/dp-mst/topology-figure-1.dot new file mode 100644 index 000000000000..157e17c7e0b0 --- /dev/null +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot @@ -0,0 +1,52 @@ +digraph T { + /* Make sure our payloads are always drawn below the driver node */ + subgraph cluster_driver { + fillcolor = grey; + style = filled; + driver -> {payload1, payload2} [dir=none]; + } + + /* Driver malloc references */ + edge [style=dashed]; + driver -> port1; + driver -> port2; + driver -> port3:e; + driver -> port4; + + payload1:s -> port1:e; +...

...on/gpu/dp-mst/topology-figure-1.dot new file mode 100644 index 000000000000..157e17c7e0b0 --- /dev/null +++ b/Documentation/gpu/dp-mst/topology-figure-1.dot @@ -0,0 +1,52 @@ +digraph T { + /* Make sure our payloads are always drawn below the driver node */ + subgraph cluster_driver { + fillcolor = grey; + style = filled; + driver -> {payload1, payload2} [dir=none]; + } + + /* Driver malloc references */ + edge [style=dashed]; + driver -> port1; + driver -> port2; + driver -> port3:e; + driver -> port4; + + payload1:s -> port1:e; +...

Hi, I use tinc with the option GraphDumpFile=/etc/tinc/ci00036/grapd.dot In the graph there is the label section: ci00036 [label = "ci00036"]; ci00037 [label = "ci00037"]; ci00038 [label = "ci00038"]; Is there an option to set the label in the tinc config file or host file to a custom text ? Something that is easy to read and has some meaning

...) <- V for (i in 1:length(Eidx)){ tmp <- Eidx[[i]] print(tmp) edL[[tmp[1]]]$edges <- c(edL[[tmp[1]]]$edges, tmp[2]) edL[[tmp[2]]]$edges <- c(edL[[tmp[2]]]$edges, tmp[1]) } G <- new("graphNEL", nodes=V, edgeL=edL) nAttrs <- list() nAttrs$fillcolor <- c("red","red","blue","blue") names(nAttrs$fillcolor) <- V plot(G, "neato",nodeAttrs=nAttrs)

...-> {port3, port4}; + port3 -> mstb4; + + /* Malloc references */ + edge [style=dashed]; + mstb4 -> port3; + {port4, port3} -> mstb3; + mstb3 -> port2; + mstb2 -> port1; + {port1, port2} -> mstb1; + + edge [dir=back]; + node [style=filled;shape=box;fillcolor=lightblue]; + port1 -> "Payload #1"; + port3 -> "Payload #2"; + + mstb1 [label="MSTB #1";style=filled;fillcolor=palegreen]; + mstb2 [label="MSTB #2";style=filled;fillcolor=palegreen]; + mstb3 [label="MSTB #3";style=filled;fillco...

...gt; + /* Malloc references */ > + edge [style=dashed]; > + mstb4 -> port3; > + {port4, port3} -> mstb3; > + mstb3 -> port2; > + mstb2 -> port1; > + {port1, port2} -> mstb1; > + > + edge [dir=back]; > + node [style=filled;shape=box;fillcolor=lightblue]; > + port1 -> "Payload #1"; > + port3 -> "Payload #2"; > + > + mstb1 [label="MSTB #1";style=filled;fillcolor=palegreen]; > + mstb2 [label="MSTB #2";style=filled;fillcolor=palegreen]; > + mstb3 [label="MST...

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

...mstb4 -> port3; > > > + {port4, port3} -> mstb3; > > > + mstb3 -> port2; > > > + mstb2 -> port1; > > > + {port1, port2} -> mstb1; > > > + > > > + edge [dir=back]; > > > + node [style=filled;shape=box;fillcolor=lightblue]; > > > + port1 -> "Payload #1"; > > > + port3 -> "Payload #2"; > > > + > > > + mstb1 [label="MSTB #1";style=filled;fillcolor=palegreen]; > > > + mstb2 [label="MSTB #2";style=filled;fill...

...edge [style=dashed]; > > + mstb4 -> port3; > > + {port4, port3} -> mstb3; > > + mstb3 -> port2; > > + mstb2 -> port1; > > + {port1, port2} -> mstb1; > > + > > + edge [dir=back]; > > + node [style=filled;shape=box;fillcolor=lightblue]; > > + port1 -> "Payload #1"; > > + port3 -> "Payload #2"; > > + > > + mstb1 [label="MSTB #1";style=filled;fillcolor=palegreen]; > > + mstb2 [label="MSTB #2";style=filled;fillcolor=palegreen]; > &g...

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

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

...) <- V for (i in 1:length(Eidx)){ tmp <- Eidx[[i]] print(tmp) edL[[tmp[1]]]$edges <- c(edL[[tmp[1]]]$edges, tmp[2]) edL[[tmp[2]]]$edges <- c(edL[[tmp[2]]]$edges, tmp[1]) } G <- new("graphNEL", nodes=V, edgeL=edL) nAttrs <- list() nAttrs$fillcolor <- c("red","red","blue","blue") names(nAttrs$fillcolor) <- V eAttrs <- list(color = c("A~B" = "green", "B~C" = "green", "C~D" = "yellow", "A~C" = "yellow"))...

...drop first column drops <- c("") test.matrix<-test.matrix[,!(names(test.matrix) %in% drops)] test.matrix test.matrix<-data.matrix(test.matrix) am.graph<-new("graphAM", adjMat=test.matrix, edgemode="directed") am.graph plot(am.graph, attrs = list(node = list(fillcolor = "lightblue"),edge = list(arrowsize=0.5))) The file testgephi.csv is following. "","1","2","3","4","5" "1",393,55,66,44,88 "2",44,23,47,57,89 "3",57,87,98,456,43 "4",77,767,86,32,77 &quo...

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