Why row number still on the left in spite of the sheet being right-to-left?

Hello ALL,
Right now, my LO version is 7.6.3.1, I facing a weird situation, where the row number stucks on the left side even when changing sheet direction from Sheet → Right-to-Left but the column letter moves to the right side as expected.
I am positive that in the past when changing the direction, both row and column moved to the right side.
I don’t quite remember if I played and messed up the options. If there is someone who can help me correct this, I would be highly grateful.
TIA
Mustafa

Please clarify:

  • Is the tabs bar below the sheet visible? If not enable
    >Tools>Options>LibreOffice Calc>View>>Window>>>Sheet tabs .
  • Did you set Sheet right to left in the context menue of that tabs bar?
    If both your answres are “yes” and the row headers are still at the left (and the column headers start with A at the left) I can only suspect user profile corruption.

Just installed 7.6.3.1 on Windows 11.

The row number stucks on the left as @safi2266 describes. The same applies to the sheet tabs.
Not observable in 7.6.2.1

I have no idea whether it is a bug or a feature.

1 Like

An interesting discussion in tdf#157961
(“Sheet tab selection area UI direction flipped based on sheet direction”)

Oh my! Sorry. I didn’t take the version number seriously because a 7.6.3 release is not yet available, and even the RC2 is only announced for next week. The release shall follow after week 2023W47.

I can’t test currently with RC1.
If this is actually a regression bug, it should be reported immediately. Probably this can still avoid a buggy release then.

Hi @Lupp
Both answers are “Yes”, but column letter
goes to right side when changing direction
I guess this is a bug, I not alone in this.
BTW how to do downgrade LO

I’m sure it’s tdf#157784, which was incorrectly fixed … and which is reopened ATM.

Please consider looking at it, and think how can you help describing what should the logic there be, because it seems to me that Andreas (who tries to fix it) doesn’t clearly understand how it must behave.

@EyalRozenberg Please consider that ^, too. I’m sure you can help improve the situation there.

I don’t believe it was fixed incorrectly; but let us discuss this on the bug page.

1 Like