the option to add single lines is also available in the context menu on the row label
As a workaround, you can select several columns or rows so it inserts the same number of columns or rows.
UX, do you think a solution via (context) menu is doable and desirable? It could make the feature more accessible and discoverable. Should be implemented along with a fix for bug 141315.
I couldn't find a duplicate.
I personally never felt the need for such a feature. But maybe some users want to insert exactly f.i. 125 lines above/below and then this request might be valid. In summary, this feature would be interesting when the number of rows to be created is large enough, so that the workaround in Comment #1 is impractical.
The main problem is how/where to add this new command? Currently the poppup menu is very crowded with 15 commands.
Should we the 16th? It could be called "Insert Rows..." and would open a simple dialog allowing the user to insert the number of rows to insert and select whether they'll be inserted "Above" or "Below".
If we implement this, then we should create the same command for columns as well.
I don't buy the use case to insert exactly 125 rows. What scenario requires this and why should we bother not only development but also users with another function? Question to OP/Maximums...
Thank you, stragu.
That workaround is great. It is a hidden gem!
Inserting 10, 20, or 30 rows is cumbersome for a lazy typist.
I didn't think of it but I could have just copied and pasted empty rows/columns.
I don't use the product so much. When Excel came out inserting multiple columns/rows was an option.
Thank you for all your attention. I'm sure you have many real "bugs" to address.
Thank you for a great alternative produce.
[Automated Action] NeedInfo-To-Unconfirmed
Another option is to utilize the Edit > "Repeat" function (shift+ctrl+V), which just repeats the last command.
Resolving WF the request to show a dialog how many rows/cols to insert.
Yes, I didn't know about that. That's useful.
Let's mark as a duplicate of bug 80390, as it's essentially the same ask.
*** This bug has been marked as a duplicate of bug 80390 ***