Visually distinguish old log output from new

[goddard@…]

The following bug report has been submitted:
Platform:        Darwin-19.4.0-x86_64-i386-64bit
ChimeraX Version: 1.0rc202005292300 (2020-05-29 23:00:06 UTC)
Description
When viewing the previous log after restoring a session by clicking the disclosure triangle on the line "Log from Thu Jun 4"  there is no visual indication of where that log ends.  I was trying to show Mike Schmid how to use this because he wanted to see what commands he had used, but there were hundreds of command from the saved session previous log and hundreds of commands in the current session and we could not find the boundary between the two.

Two ideas come to mind -- color the background of the previous log slightly dimmer.  Or put a horizontal line maybe with a message --- End of log from Thu June 4 -----.


Log:
UCSF ChimeraX version: 1.0rc202005292300 (2020-05-29)  
© 2016-2020 Regents of the University of California. All rights reserved.  

> open /Users/goddard/Desktop/test2.cxs format session

Log from Thu Jun 4 10:41:36 2020UCSF ChimeraX version: 1.1.dev202006011833
(2020-06-01)  
© 2016-2020 Regents of the University of California. All rights reserved.  

> open /Users/goddard/Desktop/test.cxs format session

Log from Thu Jun 4 10:39:28 2020UCSF ChimeraX version: 1.1.dev202006011833
(2020-06-01)  
© 2016-2020 Regents of the University of California. All rights reserved.  
How to cite UCSF ChimeraX  

> open 1a0m format mmcif fromDatabase pdb

1a0m title:  
1.1 angstrom crystal structure of A-conotoxin [TYR15]-epi [more info...]  
  
Chain information for 1a0m #1  
---  
Chain | Description  
A B | α-conotoxin [TYR15]-epi  
  
Non-standard residues in 1a0m #1  
---  
NH2 — amino group  
  

> select up

Nothing selected  

> select up

Nothing selected  

> close

> open 1a0m format ccp4 fromDatabase eds

Opened 1a0m.ccp4, grid size 97,101,88, pixel 0.37,0.37,0.367, shown at level
2.28, step 1, values float32  

> surface dust #1 size 10

> surface dust #1 size 5

> surface dust #1 size 1

> save test.cxs

opened ChimeraX session  

> save test2.cxs

opened ChimeraX session  

> turn y 20




OpenGL version: 4.1 ATI-3.8.24
OpenGL renderer: AMD Radeon Pro Vega 20 OpenGL Engine
OpenGL vendor: ATI Technologies Inc.Hardware:

    Hardware Overview:

      Model Name: MacBook Pro
      Model Identifier: MacBookPro15,3
      Processor Name: 8-Core Intel Core i9
      Processor Speed: 2.4 GHz
      Number of Processors: 1
      Total Number of Cores: 8
      L2 Cache (per Core): 256 KB
      L3 Cache: 16 MB
      Hyper-Threading Technology: Enabled
      Memory: 32 GB
      Boot ROM Version: 1037.100.362.0.0 (iBridge: 17.16.14281.0.0,0)

Software:

    System Software Overview:

      System Version: macOS 10.15.4 (19E287)
      Kernel Version: Darwin 19.4.0
      Time since boot: 26 days 22:22

Graphics/Displays:

    Intel UHD Graphics 630:

      Chipset Model: Intel UHD Graphics 630
      Type: GPU
      Bus: Built-In
      VRAM (Dynamic, Max): 1536 MB
      Vendor: Intel
      Device ID: 0x3e9b
      Revision ID: 0x0002
      Automatic Graphics Switching: Supported
      gMux Version: 5.0.0
      Metal: Supported, feature set macOS GPUFamily2 v1

    Radeon Pro Vega 20:

      Chipset Model: Radeon Pro Vega 20
      Type: GPU
      Bus: PCIe
      PCIe Lane Width: x8
      VRAM (Total): 4 GB
      Vendor: AMD (0x1002)
      Device ID: 0x69af
      Revision ID: 0x00c0
      ROM Revision: 113-D2060I-087
      VBIOS Version: 113-D20601MA0T-016
      Option ROM Version: 113-D20601MA0T-016
      EFI Driver Version: 01.01.087
      Automatic Graphics Switching: Supported
      gMux Version: 5.0.0
      Metal: Supported, feature set macOS GPUFamily2 v1
      Displays:
        Color LCD:
          Display Type: Built-In Retina LCD
          Resolution: 2880 x 1800 Retina
          Framebuffer Depth: 24-Bit Color (ARGB8888)
          Main Display: Yes
          Mirror: Off
          Online: Yes
          Automatically Adjust Brightness: No
          Connection Type: Internal

PyQt version: 5.12.3
Compiled Qt version: 5.12.4
Runtime Qt version: 5.12.8

[Tom Goddard]

I added a line at the end of embedded logs "=== End of log from <date> ===" so that it is possible to figure out which commands belong to which nested logs in bug reports. Being unable to see when an embedded log ended defeated me in bug report #3782.

Still would like a better visual indication like different background color when viewing the log in the Log panel.

[pett]

Removed the textual indicator of the end of the embedded log and switched to a different background color. The textual indicator could be added back if there was some reason for it as well.

[goddard@…]

Yes please add back in the textual indicator.  My reason for adding it is that bug reports containing log messages are hard to figure out when you cannot see where one session ends and another begins.  The background color is lost in converting to plain text for bug reports.

[pett]

Okay, restored the textual indicator, tweaked slightly for improved esthetics.