After my sheet is frozen for maximum amount of rows (10) and columns (5), I'm inserting a drawing as a button. I assigned a script to the button. The problem is:
I can't move that drawing into the frozen quadrants of the sheet. The drawing pushes up against the frozen border. I want that button at all times as I scroll through the worksheet. However, if the button is not in the frozen sections, but in the 4th quadrant, I have to scroll to it to push the button.
Does anybody know a way around this? How do i get that button to be always visible on a large worksheet?
This has been a long-standing issue, unfortunately (and this behaviour remains in the new version of Sheets). If you are using the new version, you might want to look into sidebars.
Related
I am creating a dashboard with multiple sheets, they are of same size. Sheets are added one by one by floating.
Issue: Only to the top most sheet tooltip is getting shown. For all the below sheets, tooltip doesn't get shown.
This primarily happens when the sheet on the top has no data, however still acts as an empty container. Due to this, you can look through the transparent container and it seems that the second sheet is on the top.
However, you still have a top empty container on the top, and the sheet beneath it, visible but intangible.
I have stumbled upon this issue in the past, and this tutorial was really helpful in creating a visualization you plan to.
Basically, you can drag the Vertical layout container to the dashboard. Then, drag each sheet to the dashboard. this will put all the sheets, one atop other vertically.
Looking to keep Columns A-C stay still whole scrolling up and down. My worksheet has a lot of information on it and i need the first columns to stay still. I've tried freezing panes, but the columns only stay still when i scroll left and right, not up and down.
Can this be done?
To keep an area of a worksheet visible while you scroll to another area of the worksheet, you can lock specific rows or columns in one area by freezing or splitting panes.
When you freeze panes, you keep specific rows or columns visible when you scroll in the worksheet. For example, you might want to keep row and column labels visible as you scroll.
A solid line indicates that row 1 is frozen to keep column labels in place when you scroll.
When you split panes, you create separate worksheet areas that you can scroll within, while rows or columns in the non-scrolled area remain visible.
https://support.office.com/en-ca/article/Freeze-or-lock-rows-and-columns-3439cfe6-010c-4d2d-a3c9-d0e8ba62d724
I've created a spreadsheet in Google Spreadsheet. The spreadsheet contains merged cells and I've placed a border around the merged cells.
When I choose download to Excel and open it in Excel it looses the border for all the merged cells except the first cell in the merged range.
Is there a solution to be found or a bug? If I select to download as ods format it keeps the border around the merged cells but loose background fill instead..
/Magnus
I almost put a huge bounty on this question, but I figured it out (worked for me at least).
Select all the cells in the Google spreadsheet (ctrl + A)
Clear formatting: Format > Clear formatting
This solution works!
You need to select the table (or the cell where the border is missing) and right click and choose Table Formatting options. Then select colors and set the table border as 0.5 points (pt).
It appears that for some reason the table border width becomes 0 pt and is not visible for merged cells. Setting the border width to something but zero, makes it visible again.
I've got a UICollectionView that is formatted as a single, horizontally scrollable row across the screen. It represents the next-up entries in a queue, so whenever items are added and deleted, it always happens at Index 0 (the far left of the View) and then the whole thing moves forward or back by one space. It's super-simple in the code, just:
[_collectionviewNextUp insertItemsAtIndexPaths:[NSArray arrayWithObject:[NSIndexPath indexPathForRow:0 inSection:0]]];
and
[_collectionviewNextUp deleteItemsAtIndexPaths:[NSArray arrayWithObject:[NSIndexPath indexPathForRow:0 inSection:0]]];
Everything is working properly, except the animations for insertItemsAtIndexPaths: and deleteItemsAtIndexPaths:, specifically when the CollectionView items extend beyond the edge of the screen. As long as there are only 6 items in the queue (the number that can be seen at once), it animates perfectly; but 7 items or more and the animation gets weird. Delete an item (from the left) and it also animates one being added to the right; add an item (on the left) and it also animates one being deleted from the right. Even if the queue is 50 items long, it always animates item #6 (the last visible one onscreen) disappearing and reappearing. There are no errors or warnings or anything, and I'm left with the correct number of items in the View after the animation is over, it just animates a cell being added/deleted at the edge of the screen.
My theory is that the reusable cells are being animated. Does that sound like it could be a thing? Scrolling left and right works perfectly, but inserting and deleting seems to only animate in pairs, and they always "fly in" and "fly out" in the same direction, as though one is taking the other's place. It looks (to my inexperienced eye) like the cell on the end is being flown over and added to the front, or the one on the front is being moved over to the end.
I've tried to do research on this but all I can find are animation problems that throw errors and exceptions, which mine doesn't do. Has anyone else experienced this? And can anyone offer a fix, wherein the Index 0 item gets animated and the rest just smoothly slide onto and off of the screen?
I assume you're using flow layout. Flow layout is very buggy animating items across the layoutAttributesForElementsInRect: boundary (i.e. items moving in and out of view). In my experience, you can fix some of these issues by overriding the 'initialLayoutAttributesForAppearingItem' & finalLayoutAttributesForDisappearingItemAtIndexPath: methods and correcting the frames when the super class returns incorrect values. Here is a successful answer to a very similar issue.
I open sourced a simple uniform grid layout VCollectionViewGridLayout that greatly improves animations over what UICollectionViewFlowLayout provides. However, it currently only does vertical scrolling. But if you went in there and transposed all of the horizontal and vertical calculations, I'm sure it would solve your issue.
Delphi 2007.
I have a TGrid with more rows than will fit on the screen, and the height of the grid is such that there is a partially drawn row at the bottom.
When I click on this partial row, it jumps up to be fully visible (via a procedure called 'ClampInView' in Grids.pas). But it doesn't stop. Since the mouse is now over a new partially drawn row, that jumps up too.
The net effect is that clicking on the partially drawn row starts selecting cells in a vertical column, spinning all the way to the bottom (or until you release the mouse).
I have replicated this on a fresh winforms project with just a single grid with 100 rows, and no code, so I'm pretty sure it's not something I'm doing in code wrong.
It is bad for me because the form I have in real code has drag and drop type behaviour, so clicking and releasing ~0.1 seconds later on the partial row will pick up the item in the cell and drop it about 50 rows lower. This is definitely not what you expect to happen when you click on a cell.
Any suggestions how to fix/work around this?
This is what I have always done because I think it is tacky to have partially visible rows. I adjust the size of the grid so its client area is an even multiple of row height. You can do that at design time, or it is easy to do via code as well. The kicker would be if you have re-sizable rows. If that is the case then just put the code to resize the grid in the event handler for the row resize event (I believe it has one).
Not only does this prevent the behavior you are trying to fix, but it also (in my opinion) makes your UI look a lot cleaner!
You can try override MouseDown in your grid and do not call inherited MouseDown, if user clicks in "bad" places.