Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The diagonal superfluous lines are there because you are adding points and segments to the same figure. The pen never gets lifted from the paper. You have to split your geometry into more figures.</p> <p>Copy your segment and figures creating into every place you want the pen to "go down", and the figure.Segments.Add(segment) and geometry.Figures.Add(figure) into every place you want the pen to "go up".</p> <p>That way your geometry will consist of many separate figures, and your diagonals should no longer be a problem.</p> <pre><code> for (int ra = 0; ra &lt;= 24; ra = ra + 3) { figure = new PathFigure(); segment = new PolyLineSegment(); for (int dec = -90; dec &lt;= 90; dec = dec + 3) { points = coords.GetAitoffCoord(ra, dec); double xCoord = xCenter + points.X * width / 2; double yCoord = yCenter + points.Y * height / 2; segment.Points.Add(new Point(xCoord, yCoord)); } figure.StartPoint = segment.Points[0]; figure.Segments.Add(segment); geometry.Figures.Add(figure); } for (int dec = -90; dec &lt;= 90; dec = dec + 30) { figure = new PathFigure(); segment = new PolyLineSegment(); for (int ra = 0; ra &lt;= 12; ra = ra + 1) { points = coords.GetAitoffCoord(ra, dec); double xCoord = xCenter + points.X * width / 2; double yCoord = yCenter + points.Y * height / 2; segment.Points.Add(new Point(xCoord, yCoord)); } figure.StartPoint = segment.Points[0]; figure.Segments.Add(segment); geometry.Figures.Add(figure); } for (int dec = -90; dec &lt;= 90; dec = dec + 30) { figure = new PathFigure(); segment = new PolyLineSegment(); for (double ra = 12.01; ra &lt;= 25; ra++) { points = coords.GetAitoffCoord(ra, dec); double xCoord = xCenter + points.X * width / 2; double yCoord = yCenter + points.Y * height / 2; segment.Points.Add(new Point(xCoord, yCoord)); } figure.StartPoint = segment.Points[0]; figure.Segments.Add(segment); geometry.Figures.Add(figure); } figure = new PathFigure(); segment = new PolyLineSegment(); for (int dec = -90; dec &lt;= 90; dec = dec + 3) { double ra = 12.01; points = coords.GetAitoffCoord(ra, dec); double xCoord = xCenter + points.X * width / 2; double yCoord = yCenter + points.Y * height / 2; segment.Points.Add(new Point(xCoord, yCoord)); } figure.StartPoint = segment.Points[0]; figure.Segments.Add(segment); geometry.Figures.Add(figure); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PODrawing programmatically using C# in Silverlight
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGuge
    1. USGuge
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODrawing programmatically using C# in Silverlight
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COunfortunately this approach does not appear to work. Probably because even if I do a new PolyLineSegment() within each loop, the overall figure still joins the points. I could do each little section but that would be a lot of code that does that same thing with seperate variables. Not the best way but I guess I may have to live with it if there are no other options.
      singulars
      1. PO
      1. USKamal
    2. COI was wrong. It's not enough to seperate the figures into segments. The segments in a figure are implicitly connected. You actually have to separate your geometry into more figures. I event tested it, looks pretty good now.
      singulars
      1. PO
      1. USGuge
    3. COGuge, you are THE MAN! Thanks a bunch! This really helped me out.
      singulars
      1. PO
      1. USKamal
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload