I would like to know what is the recommended way of designing a Silverlight page with many controls in it, like a lob application for example. What I think would be simpler, especially if there are many pages to make, is to make a template page with a large number of rows and columns of the same dimension, so that I can visually put every control into the grid. In this way, each control will have something like absolute coordinates, as well as rowspan and columnspan.
Isn't this one the easiest way to design? I think such a layout would also be easier to modify, since if I want to move a textbox from the left to the right side of the screen, I only have to change it's Grid.Column property, without minding all the interactions with the stackpanels and the grids on the right side, like I see in many layouts that are organized with a number of grids and stackpanels.
And can the fact of having a large number of rows and columns decrease the performances?
Thanks for any opinion.
You can use a Canvas control if you want to do absolute positioning.
Related
Querying https://nationalmap.gov/epqs to query for elevations make them available offline. Later on folks can specify a lat-long and can get it from the offline store.
The way I'd like to do this is to snap a given coordinates to a 10ft grid (or 100ft grid or whatever). So I'd prequery all values on the grid and store them, then when the offline query comes I can snap the request lat/long to the grid and just lookup the relevant value.
The problem is that I'd like my grids to be homogenized, that is that if two grids overlapped then their points would overlap if that makes sense. So I need a standardized offset for each grid so they all line up. Any ideas on how to achieve that?
I hope this makes sense.
I am using WinRTXamlToolkit to create a histogram in UWP.
I'd like to hide almost all elements in the chart, but displaying only the columns, is that possible?
EDIT:
Is it hard to hide only the confusing numbers displays along x Axis
I second Chris's suggestion that you'll need some serious retemplating. IMHO it would make more sense to simply build your own chart with a few bottom-aligned rectangles. It will be easier, it will perform better and be more satisfying to accomplish than chipping at the full chart control to trim it down to what is essentially - a few bottom-aligned rectangles. Bonus points for doing it in Win2D or other Direct2D way that should allow you to get real-time update performance.
See sample Win2D chart rendering implementation at https://github.com/xyzzer/Win2DChartSample
If an element is to be displayed at 4 columns wide regardless of viewport size, is there any reason to not use just the xs class?
Simple answer. No. the *-xs-* classes are not wrapped in any media queries so by design they are kind of the default, and unless you specify something else, such as a col-sm-* class, then the *-xs-* class will be applied throughout all screen sizes. So in your specific case, if you always wanted something 4 columns wide the col-xs-4 class would be the right way to go.
Just remember that 4 columns on a very small screen (i.e. a phone) is a very small area, so don't try and stick anything important or potentially long in there!
I am designing a simple music app where the user gets to play instruments i.e. Drums, and the problem that I am facing is with resolutions.
The drums are images, which I have converted them into buttons. Everything looks great at the state that I have designed it.
However, when I switch to other resolution states, the button(image) are distorted, e.g. skewed, scaled, and looks nasty.
I have tried designing or arranging them via selecting 'Enable state Recording', but the specific designs for that state are not being saved.
Have you tried the approaches discussed here? http://msdn.microsoft.com/en-us/library/windows/apps/hh465362.aspx For the actual button sizes, make sure you are not fixing the width/height with pixel values. Use * weighted rows and columns to layout your grids and have the buttons autosize to fill a given cell in the grid. Then match with the appropriate image resource per the article.
Grids are great for dividing up available space but they can't account for changes in aspect ratios. If your items are still set to Stretch (or Fill) then they can end up out of aspect ratio. Another option is to design the entire layout at a fixed size (let's say 1024 x 768 or 1366 x 768) and wrap the entire thing in a ViewBox. ViewBox will scale all elements equally and maintain the aspect ratio, adding letterboxing (or empty space) on the sides / top & bottom if necessary. This might be a better approach for a drum kit.
Hope that helps.
Redid the whole project of designing again.
This time, I put the image inside a specific grid and that made things lot better. :)
Actually, how can I extract size of gui elements in general in PyQt?
So far I have only found sizeHint mentioning anything regarding sizes in PyQt.
Could anyone please explain how sizes works in PyQt?
In general, it's not possible to guarantee the exact sizes of widgets, because there are so many different factors that come in to play. Widgets will rendered differently depending on the window manager in use, the current GUI style, the fonts, etc - and each platform has it's own peculiarities.
To get a better understanding of all this, I would suggest you take a look at Qt's own overviews of window geometry, widgets and layouts and layout management.
To answer the specific question on the height of QListWidgetItems: they will have whatever height is calculated by the QListWidget when it lays out its items. This may take into account the items' sizeHint, which can be set programmatically with QListWidgetItem.setSizeHint.