Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You said:</p> <blockquote> <p>Decomposing the play area into smaller user controls would leverage the WPF layout capabilities, but it seems like decomposition would prevent the cards from expanding into adjacent user controls during the mouse-over, so that doesn't seem feasible either.</p> </blockquote> <p>But this is not correct. Decomposition is absolutely the right approach to take, and this would not prevent the cards from expanding into adjacent user controls. The reason being that you can use a <code>RenderTransform</code> rather than a <code>LayoutTransform</code>. See <a href="http://www.charlespetzold.com/blog/2006/03/211105.html" rel="nofollow noreferrer">this example</a>, by Charles Petzold, or <a href="http://patconroy.wordpress.com/2009/03/24/layouttransform-vs-rendertransform-in-wpf/" rel="nofollow noreferrer">this article</a>, to visualize the difference. Because a <code>RenderTransform</code> is applied after the layout has already occurred, your cards would be able to expand outside their bounds.</p> <p>Given that decomposition is the right approach, I would arrange your various card collections into a <code>Grid</code>, with each collection being an <code>ItemsControl</code>. The <code>ItemsControl</code> should bind its <code>ItemsSource</code> property to some collection, and then you can provide a custom <code>ItemTemplate</code> that would display the image and any other information. I would be hesitant to use a <code>Canvas</code>, as this would restrict you to hard-coding the positions for the cards (which is a very WinForms-like solution for a problem that can be far more elegantly solved). Take advantage of WPF's fantastic layout engine and use nested grids and items controls to create a dynamic layout. This will ensure that your game board looks good at any resolution and when stretched to various sizes.</p>
    singulars
    1. This table or related slice is empty.
    1. POWPF layout for complex card game
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCharlie
    1. USCharlie
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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
    1. COThank you for the helpful info. RenderTransform should solve the card overflow problem. One other problem with decomposition, however, is keeping the cards the same size across all the children. As an example, consider a parent container control and two child controls (one for each player's cards). When the outer window is resized, I need to calculate new card sizes based on whichever child area has the most cards. Is there an event I can hook in the container after the children have been positioned (and sized) so that I can calculate the card size and send it to the children?
      singulars
      1. PO
      1. USDoug
    2. CORather than hooking into an event, you should bind the card size (for all cards) to a single consistent property on your view-model. Then when a child area gains or loses a card, you recalculate this size property, and all of the bindings are updated automatically.
      singulars
      1. PO
      1. USCharlie
 

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