Presently, 'Number Recognition' (.uno:TableNumberRecognition) is only available in the context menu, when the cursor is inside of a table. It would be best if this selectable feature would be always accessible inside the menu and removed from the context menu.
Hi Jay, you write it as if it is a problem that the entry is only available with the cursor in a table? Do you have ideas on all the settings related to number recognition (see Tools > Options > Writer > Table (iirc) ?
Hi Cor, The main point here is that it is given a major importance when it is in the context menu and that it shouldnt be in the context menu when it effects all tables and not just the table you are right-clicking on.
Hi Jay, (In reply to Jay Philips from comment #2) > The main point here is that it is given a major importance when it is in the > context menu Why do you think it's given major importance here? And isn't it a function of major importance? > ... and that it shouldnt be in the context menu when it effects all > tables and not just the table you are right-clicking on. Number recognition is directly linked with numbering notation, and a function influencing the very cell at the cursor..
Hi Cor, > Why do you think it's given major importance here? > And isn't it a function of major importance? As the context menu is to give easy access to frequently used features of context, this isnt the case for number recognition. Unfortunately this function isnt of major importance as its an on/off button that is switched on by users who want its functionality and left on, so even for users who use it, them seeing in the context menu of every table isnt of benefit. > Number recognition is directly linked with numbering notation, and a > function influencing the very cell at the cursor.. Number recognition affects all cells and not just the cell you are currently in. Number format affects the cell that you are currently in. I've setup a bug for the reorganization of all the context menu table related entries, so i'm closing this as a duplicate of that. Please read through bug 86619 comment 3, for the full scope of the change. *** This bug has been marked as a duplicate of bug 86619 ***