Opened 13 years ago

Closed 12 years ago

#71 closed defect (duplicate)

FM/2 forgets Details setup/Show subjects setting

Reported by: jbs Owned by:
Priority: minor Milestone:
Component: fm/2 base Version:
Keywords: Cc:

Description

I use Details view most of the time and I prefer to have "Show Subjects" turned on.

Occasionally this setting gets deselected/disabled by FM/2. (I am the only user of FM/2 and I do not turn off this setting.)

Change History (10)

comment:1 follow-up: Changed 13 years ago by gyoung

  • Owner changed from StevenHL to gyoung

Does subjects show anything? I just turned it on in a directory will lots of subjects and don't see any. (note to self most if not all are max length check the string length allowed)I also experienced the subject being turned off the first time I exited and reopened. Let me know if you figure out away to reproduce this.

comment:2 follow-up: Changed 13 years ago by gyoung

If I set this using the container menu it doesn't set it in the settings notebook but if I set it in the setting notebook and then turn it off using the menu it gets turned off in the notebook.

comment:3 Changed 13 years ago by stevenhl

  • Milestone set to Release_3.05_beta8

comment:4 in reply to: ↑ 2 Changed 13 years ago by jbs

Replying to gyoung:

If I set this using the container menu it doesn't set it in the settings notebook but if I set it in the setting notebook and then turn it off using the menu it gets turned off in the notebook.

I had not noticed this discrepancy.

At this point in time, my Subjects are being displayed, the setting is "on" in the Container menu but "off" in the settings Notebook.

comment:5 in reply to: ↑ 1 Changed 13 years ago by jbs

Replying to gyoung:

Does subjects show anything? I just turned it on in a directory will lots of subjects and don't see any. (note to self most if not all are max length check the string length allowed)I also experienced the subject being turned off the first time I exited and reopened. Let me know if you figure out away to reproduce this.

Having the Details view show Subjects does work for me.

I have many files with subjects and when FM/2 remembers my setting to include Subjects in Details view, it works as it should.

If a subject exceeds the limit set by FM/2, then the displayed subject is truncated to this limit.

comment:6 Changed 13 years ago by gyoung

  • Milestone Release_3.05_beta8 deleted

comment:7 Changed 13 years ago by gyoung

I want to make sure of the intent of the settings. I think that if show subjects is set in the settings notebook then anytime a new directory cnr is opened in details view subjects should show. If the setting is change from the pull down menu on the cnr it should only apply to that cnr including any new directories opened in it (ie any addition container that are opened should show subjects).

This sounds reasonable, but see below.

The behavior I am seeing is if I use the menu to not show subjects any cnr opened after that with shift doesn't show subjects.

OK.

I know the behavior has to do with the fact that the detail view subject behavior is only stored in the ini on a per container basis with it being read from the ini in many of these cases but after rescan it is apperently read from the settings notebook. Before I muck with this I want to be sure we agree as to what is the appropriate behavior when using the cnr menu to over ride the settings notebook

Whichever way you change this, the operation should be intuitive. I agree that for existing containers, the current setting should presist. The question then becomes what's be the best behavior for new windows. Should the settings value be used or should the most recent container setting be used. I would tend to prefer the later. My thought is that if I toggled the setting on for some reason, this reason is likely remain in effect for the next few windows I open in the current session.

On startup the settings notebook value should probably take priority. This means that after any saved windows are restored, the "most recent container" setting" would need to revert to the settings notebook value.

I agree that it is a reasonably policy that the container setting never automatically update the notebook setting. However, it might be useful to have a context menu option to update the notebook settings to match the current container.

comment:8 Changed 13 years ago by gyoung

  • Version 3.05 beta deleted

comment:9 Changed 12 years ago by gyoung

  • Owner gyoung deleted

comment:10 Changed 12 years ago by jbs

  • Resolution set to duplicate
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.