Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#1486799 closed Bugs (duplicate)

Column Ordering Reset, Read/Unread Flag position

Reported by: noc4 Owned by:
Priority: 2 Milestone: 0.4-stable
Component: Core functionality Version: 0.4-beta
Severity: normal Keywords: column order
Cc:

Description

Since 0.4-beta the Read/Unread? flag is always displayed to left of the subject line and not placed with the other flags.

even with

$rcmail_config['list_cols'] = array('flag','attachment','from','subject','date','size');

the Read/Unread? flag appears next to the subject line.

Enabling or Disabling any columns in the mailbox view causes the column order to be reset and

$rcmail_config['list_cols']

to be ignored.

Attachments (1)

read-flag.png (40.3 KB) - added by noc4 3 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 follow-up: Changed 3 years ago by alec

  • Milestone changed from later to 0.4-stable
  • Resolution set to worksforme
  • Status changed from new to closed

THis has been fixed in svn-trunk.

Changed 3 years ago by noc4

comment:2 in reply to: ↑ 1 Changed 3 years ago by noc4

  • Resolution worksforme deleted
  • Status changed from closed to reopened

Replying to alec:

THis has been fixed in svn-trunk.

in [306f15db] the column ordering is now preserved when enabling/disabling columns great! :)

the position of read/unread flag still seems to be an issue though, its still tied to the left of the subject rather than with the rest of the flags! see attached png

comment:3 follow-up: Changed 3 years ago by alec

  • Resolution set to duplicate
  • Status changed from reopened to closed

This is intended behaviour, but feature request already exists, #1486665

comment:4 in reply to: ↑ 3 Changed 3 years ago by noc4

Replying to alec:

This is intended behaviour, but feature request already exists, #1486665

Seems a strange thing to do, was there some underlying reason for changing this between versions ?

comment:5 follow-up: Changed 3 years ago by alec

Yes, this looks better with enabled threads.

comment:6 in reply to: ↑ 5 Changed 3 years ago by noc4

Replying to alec:

Yes, this looks better with enabled threads.

Oh yes, I was just looking wondering why, then the threads issue occurred to me! so it does!, perhaps in this case we could choose in the config which column to attach read/unread status to, In our case having it attached to the Sender/From? column. I could have look at making a small patch for this

comment:7 Changed 3 years ago by noc4

Hmm actually that doesn't work so well for longer threads - to much indenting on the Sender/From? column!

Note: See TracTickets for help on using tickets.