ScrollViewer is having hundreds of records and it has image views, these image views are not loading while setting the Scrollviewer.ScrollToVerticalOffset(100) , am trying to print the VerticalOffset value it shows '0'. This is the major problem i have read some where.But what is the solution for my problem?..
After doing some research I arrived at this solution:
scrollViewer1.UpdateLayout();
scrollViewer1.ScrollToVerticalOffset(200);
Related
I know that the question was submitted a lot of times, but this is driving me mad.
I'm trying to make a landscape A4 report, printer friendly. As I could see in lots of threads before I tried to respect the fact that the body size must be inferior or equal to the physical page, including margins, and columns in the count.
Here are my document properties
Report:
Body:
I inserted a first rectangle with some contents, at that point, no extra blank page, here is the rectangle location :
Right after I inserted a second rectangle with same dimensions as previous one:
Both first pages are rendered correctly with the rectangle at its expected location, but I get a 3rd extra blank page...
ConsumeContainerWhiteSpace property is set to true, and this did not help...
Do you have any trick to get definitely rid of these blank pages ?
Thanks a lot !
EDIT : Just added the report designer view, as requested
Don't know how I didn't notice it before, but your body height is bigger than your page height defined in the report properties. If your report is supposed to generate two pages, that second page will have to add an extra 3 centimeters and cause that third page.
I finally managed to handle this the following way : I put my first rectangle 0,5cm under the header (with a forced pagebreak after) and if I use the same size of rectangle for everypage, ensuring that there's a 0,5 cm space between each rectangle, I can manage to display content on multiple pages, with rectangle bordel always located at the same position. Guess I should keep this method for all future reports :) Thanks a lot for your advices !
I recently made a game with game maker and I've tried converting it to html5, but it's got some big errors... here is the game in html format: http://ivatrix.com/Game/index.html
First off, text is meant to appear in the top left like how you can see in this screenshot: http://gyazo.com/baa386fe06cfac9439c83b6e5192efd8 the text only appears after you create a combo.
Secondly, when you click on an orb it's meant to scale down to half it's size then scale up to 1.5x it's size, but instead it's shrinking until it's 1px large then infinitely increasing in size. Draw code is here:
if sl=1
{
if (s=0.6 or s=1) then d=d*(-1)
s+=d
if(frozen=1)
{
draw_sprite_ext(sprite_index,global.skin,x,y,s,s,0,c_blue,1)
}
}
And then there's other small errors like some text won't display, particle effects don't seem to draw, the game always returns saying there is no match on the board. That's all I've found so far.
Does anyone have any idea what I can do to fix this?
Thanks.
Since no one has provided an answer and I've found one myself, I'll put it up here so others in the same boat can benefit as well. Practically, the source of all my problems with floating point numbers being irregular, for example instead of it being 1 it could be 1.000000003, which meant if you were to check if that variable was equal to one, it would return false. Further information here: http://help.yoyogames.com/entries/77891197-HTML5-Issues-And-Differences
So for an example in my case, I changed the line
if (s=0.6 or s=1) then d=d*(-1)
to
if (s<0.6 or s>1) then d=d*(-1)
And now the problem is fixed.
Will I have to face any problem if i have large number of hidden divs in my page ??
i mean that in my page there is a loop which contains some hidden divs and some buttons which when clicked shows one of the hidden div...
i just want to ask that will i have to face any problem with these hidden div..
the code here is just an example ....
any help will be appreciated..
thanks in advance
<?php
for ( $a = 1; $a < 10; $a++ ) {
<div style='display:none'>
content goes here....
</div>
}
?>
I have many pages with over half a million divs that work fine. Probably the most important thing with many hidden divs is that you enclose the hidden divs within another element which is of fixed layout. If you have a massive amount of html and a fluid layout and you change the visibility of an element, the browser must calculate all the layout again which can be slow and give the user poor responsiveness.
No problem! but It will be indexed but can be frowned upon by Google if you are hiding/showing content for SEO reasons. In other words, what Google sees should be what the user sees when clicking the link.
No problem! But if you are having more and more your websites load will be heavy. That might cause slower performance and perhaps hangs up. It would take loading time too..
That depends on what you try to do.
If you fill your hidden divs with images and other heavy stuff, it all will be loaded immediately with page and may slow things down. Also, browsers would still take time for parsing everything you hid (but that is actually not much time).
So, if you are talking about like 1000x1000 grid of buttons or something like that (for making kind of a game maybe), it will result in sad performance.
If you are talking about dynamic loading of a lot of heavy content, like a whole facebook timeline, it won't work well neither.
But if you just want to show users some blocks, which would work okay if you didn't hide it at all, you will have no problems.
I have an HTML table that can be more than 1K rows and a dozen or so columns.
I want the columns to be a fixed size (controllable by the user) and not grow/shrink either vertically or horizontally. So visually the contents of a particular table cell will be on one line and the overflow gets cut off at the end of the cell.
Doing performance analysis in Chrome on a large table the main performance killer is overflow:hidden.
I've tried putting the contents of each cell inside of an input, since that would replicate the same visual behavior, but that has a similar performance impact.
What do people recommend to improve performance?
If necessary I don't have to use a table tag, but would prefer to stick with the table tag if good performance can be achieved.
Update 1: I've included a file that demonstrates the performance issue here. Warning the file is pretty massive (25MB) and will slow down your computer. By default the table does not have overflow set to hidden, and once the table has been loaded (can take a while) the browser performance relatively smoothly.
However, if you edit the file and uncomment lines 12-15 and then open it. You'll see after loading browser around the table is significantly less responsive.
FYI: I have run into this problem on the iPad/iOS causing performance problems with a page that has about a hundred rows in a table with table-layout:fixed.
As soon as a cell, or a div in a cell, gets an attribute that forces it the cell to be drawn individually, it takes about 300ms instead of 100ms to draw (which causes the UI to feel abysmally slow for my situation).
Either of two properties (position:relative or overflow:hidden) caused the problem for me, removing them optimised the speed but caused text overflow if cell text was too wide for the fixed width columns.
The slowdown was happening even after tables were drawn, because I am dynamically popping up an absolute div over the table. When profiling the javascript (using (new Date).getTime()), the slowdown in measured in places in the javascript that have nothing to do with the table.
[edit: added following as part solution]
Put all cell content inside a span element (so can measure offsetWidth of content rather than width of containing block element).
After appending the row into the document, test if each span.offsetWidth is greater than the column width, if so add the "overflow:hidden" to the style (or via a class) of the containing block.
Can skip 1 and 2 above for some columns (if it is known that the cell content will never need clipping).
Caveats:
Measurements only made for iOS5 Safari (I didn't profile any other browser).
Works for us because we dynamically create table rows (processing your example using javascript would be slow?).
Most cells for our data do not overflow (clipping is only required sparsely - only a limited number of cells).
Compromised initial page load (generation of table in page went from 80ms to 800ms).
But sped up dynamic combo popup (340ms down to 130ms) giving much better keyboard responsiveness.
For your situation, might be fast to first using variable width columns, measure offsetWidth of all columns, setting column widths to pixel widths and setting overflow:hidden only on columns where offsetWidth of column is greater than the pixel width you will be using for the column.
You could try using a tiled approach. It is a pretty typical approach to making things like infinitely side-scrollable games efficiently.
Put all of your data into a Javascript array, and then have N + 1 rows in a table that has N rows visible. When you scroll down, the last item would move into view. At the moment that you have scrolled far enough that the first item moves out of view, you shift all of the data up a row and reset the scroll position back to where it started. Done correctly, the shift would be completely transparent to the user. You would only ever be working with N + 1 rows in an N-rows-visible table.
I've done this before, but under very specific UI constraints. I kind of shutter at the thought of making this consistent using the built-in browser scrollbars and such.
first off, the amount of markup required to have a table is much larger than just using divs with clear:both css for a new row. so that's the first performance hit.
also, you are setting the overflow as a class ( ? )
<style type="text/css"> .ovfl { overflow:hidden; }</style>
<td class="ovfl"></td>
As an aside, 1000 rows is a weight to deliver.
With divs you at least have an easier opportunity to throw those out of sight ( beyond the scroll ) into a div with display:none until the visitor scrolls to them.
few skins to cat mostly likely on this job,
Hope had some good thoughts.
Webkit bug 75001 is related to this problem and it covers the work being done to solve it (also see bugzilla dependencies for information).
How do I get rid of the page breaks in an SSRS report, making the report display in a single page?
Open the report's .rdl file in a text editor and locate the <Page></Page> section.
In that section, insert the following:
<InteractiveHeight>0in</InteractiveHeight>
<InteractiveWidth>8.5in</InteractiveWidth>
In SSRS, an interactive height of 0 means the report has an infinite length and therefore, it will exist on a single page.
Make sure you do not have one of the properties set to true on one of your report items for PageBreakAtEnd or PageBreakAtStart. Also, make sure you keep the width of your report less than the width of your actual paper, keeping in mind extra space for the page margins (Report > Report Properties > Layout)
And according to Microsoft:
"Although it is not recommended, you can disable soft page breaks by setting InteractiveHeight to 0." I think this only works for HTML rendering though, I have not used it myself.
I'm not sure if there is a scale of any kind where no matter how big your report is it still prints on one page if that is what you are looking for.
Right Click anywhere in Body and select Properties.
select Reports From the DropDown. (When you select an element in report, the dropdown changes to TextBox/Header or the item you select)
In Report properties, Expand InteractiveSize Attribute.
Set Height -> 0in
If you're trying to display report data in one page, it is simple to do in SSRS. All you have to do is select an entire table and then go to the property pane. Update KeepTogather = True.
You can set the report's InteractiveHeight to 0 to disable paging.
Go to report properties -> Page -> InteractiveSize -> Height. Set this value to 0in.
Here is the similar question.
Dustin Brooks wrote:
Also, make sure you keep the width of your report less than the width of your actual paper, keeping in mind extra space for the page margins (Report > Report Properties > Layout)
Also be extra careful about this when working with subreports. I've lost count of the times I ended up with extra blank pages when I've accidently made a subreport wider than the main report.
When creating reports for the web, I would disable page breaks by setting the InteractiveSize to something really crazy, like 1000x1000". (I just checked, and setting it to 0x0" as Dustin Brooks mentioned in his answer has the same effect.)
I left the PageSize property at 8.5x11" and the reports printed across multiple pages normally.