Bug 139462 - R1C1 vs A1 mode not fully implemented
Summary: R1C1 vs A1 mode not fully implemented
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.2.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Dev-related
  Show dependency tree / graph
 
Reported: 2021-01-07 09:43 UTC by ffs
Modified: 2025-05-19 03:10 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ffs 2021-01-07 09:43:05 UTC 

    


    


      



        
          Comment 1
        

        
          ffs

        

        
        

        
          2021-01-07 09:47:20 UTC
        

      






In R1C1 mode the column labelling is by number and the cell referencing is by R1C1 syntax _but_ the sort menu remains in A1 mode.

I don't know about you but I find converting base 26 to base 10 in my head mildy challenging.

It would be very nice if all the menus etc reflected the current mode.

It would be very nice if it was easy to switch between modes (eg an R1C1 option box in the status bar) as they have their own merits.

    


    


      



        
          Comment 2
        

        
          ffs

        

        
        

        
          2021-01-07 09:49:07 UTC
        

      






I forgot to add - what would be very nice is a dual mode allowing both to be mixed and matched...

    


    


      



        
          Comment 3
        

        
          m_a_riosv

        

        
        

        
          2021-01-07 15:27:25 UTC
        

      






Repro
Version: 7.2.0.0.alpha0+ (x64)
Build ID: 4e3ce9dd6ace0b22f7b3f45cf2338b201f4dc305
CPU threads: 4; OS: Windows 10.0 Build 20180; UI render: default; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL

    


    


      



        
          Comment 4
        

        
          QA Administrators

        

        
        

        
          2025-05-19 03:10:47 UTC
        

      






Dear ffs,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug