Using the last release of RadSpreadsheet, I get an exception when the first row is hidden when scrolling with the mousewheel. Attached is a demo.
The UI behaivor of drag selection shows inconsistent behavior between WinForm vs WPF/Excel.
When you drag some cells for selection and keep dragging to the right (getting the out scope), the control scrolls to the right.
This behavior is common in Winform/WPF/Excel.
When you drag backward (to the left), WPF controls scroll back and so is Excel, while Winform controls does not scroll
Same thing for top and bottom scroll. Winform Spreadsheet control does not scroll. It may scrolls only to the right.
Another Caveat I see meanwhile is that when you scroll backwards until the row area, the pointer become row-resize pointer, or so
If you keep mouse moving around, it sometimes makes a horizontal line (possibly a guide for row resize?)
The issue in this case is that, it does not remove itself. the horizontal line stays there. It is not very annoying (as it is thin horizontal line) but is still a bug.
create a empty Winform app, with the RadSpreadsheet Control, and Run
Drag from row C3 and to the right (around the scrollbar) the control scrolls to the right (this is not quite smooth though..)
Scroll right to AZ3 say, and drag backward back to C3, this now does not scroll back.
Same for top and bottom.
Do the same for WPF, it now works as expected
Do the same for MS Excel, it now works as expected.
please try set the WorkBook to RadSpreadsheet.
I have implemented the ListDataValidationRule code to add a dropdownlist to the spreadsheet. Based on the code I can find and the searching I have conducted, it seems to be correct, however the dropdown does not appear in the control.
The dropdown list does appear in Excel when I export the file.
Dim Context As ListDataValidationRuleContext = New ListDataValidationRuleContext(CurrentWorksheet, CurrentCellIndex)
Add a RadSpreadsheet on the form and try resizing it at design time. You will notice that the control is resized after a considerable delay.
If you Dock the control to Fill and try resizing the form at run you will notice that the layout is incorrect. The attached gif file illustrates the obtained behavior.
Workaround: update the layout after resizing:public RadForm1()
When you set the AutoSize property to true, the control becomes enormous - Size (5002, 5002).
There is no specific logic for auto-sizing the control. We should either remove the AutoSize property or size the control according to the rows/columns it uses.
Please follow the steps:
1. Run the attached sample project.
2. Move the form to a monitor with 125% DPI scaling.
3. Resize the form to make the spreadsheet bigger. You will notice that the column/row headers are missing for the last column/row headers.
Add support for creating Tables and applying tables styles (predefined ones or custom).
I have loaded an excel file into the spreadsheet control from our document database. When a user makes changes and clicks the save button I would like to handle a save process back to our document database of the file.
If a save function can be raised I can save to the document database
If a SavAs fucntion can be raised I can prompt the user to create a new version
Can the control have these two features added please?
If a worksheet spans more than one page, you can print row and column headings or labels (also called print titles) on every page to ensure that the data is properly labeled.
So here's what happens. I create a workbook and a worksheet in that wb which I assign as the workbook of a RadSpreadSheet by RadSpreadSheet..Workbook = wb
The first time I assign a name to the first (and only sheet) created in the creation of the wb, the name does appear on that sheet.
Then some code takes this workbook ByVal, creates a new Sheet, makes that sheet the wb's ActiveWorksheet and then changes the ws's name.
You can see in the debugging that the worksheet does have the new name i put there ("2018-05"), but visually this 2nd worksheet has the default name "sheet 2".
Then that wb which is returned by the function is assigned as the RadSpreadSheet's workbook
If I run the code again, so a 3rd sheet is created, then the 3rd sheet will visually have the default name "sheet 3", however in the debugger it says "2018-06" as its name; but most importantly, now sheet 2 has magically changed to what I was seeing its name to be in the debugger ("2018-05").
I'm assuming that If I'm changing the sheet names at runtime, I need to call some method on the Workbook element or something like that in order to update the names. I just couldn't find which method to call.
I have a RadRibbonForm with a normal ribbon with no items and a spreadsheet control.
I iterate over a datatable and fill the spreadsheet's cell values with the datatable's values
we're talking about a very small size, like 33 rows x 35 columns, and not even all the values are filled in.
Unfortunately, there's a very noticeable delay in the spreadsheet, from moving the scrollbars to selecting to changing sheets.. the whole thing feels laggy.
Is this just how it is, or am I experiencing a possible bug?
Could it have anything to do with https://feedback.telerik.com/winforms/1380948-exception-at-runtime-trial-bug ?
If that is just how it is, is there anything I can do to make it feel snappier? Disable a theme? Disable some behaviour?
So, I'm testing the Telerik suite, part of which is the RadSpreadSheet. I'm currently using the 30 days trial.
So, when I'm debugging it and I'm instantiating a new form that contains the RadSpreadSheet, the programme will about 50% of the time create an exception of object reference not set to an instance of an object
Now, I've only noticed this with forms that contain a radspreadsheet but it could have nothing to do with it.
What always happens before I get the exception is that the reminder to buy a Telerik License appears (the programme halts until I choose an option) and when the dialogue disappears, the exception happens.
Please note that if I just push "F5" again in VS, without changing anything anywhere, so after the crash immediately debug (F5) again, the exception will not occur.