Log is not creating Journal entries

[garycmartin]

Log (testing on v34) is no longer saving Journal entries when it is started. This raises a couple of issues:

1. With no journal state ever created, the home favourite view always shows the Journal as an 'unused' activity in grey.
2. With no Journal entry, there is no way to add metadata to the session descriptions/tags about what issues you found when running Log (I often in past builds pasted tracebacks into the description so I had a record of the issues).

It might be a nice feature at some point for Log to allow staring of logs you wanted to keep for future reference and plain text Journal searching of past issues.

[tonyforster]

A third issue:
For me at least, I am in the habit of launching from the home view under the assumption that I will either revert to a running instance if there is one or launching an instance if none is running. This is how other Activities work. That means I have found myself running multiple instances of Log.

[garycmartin]

Replying to tonyforster:

A third issue:
For me at least, I am in the habit of launching from the home view under the assumption that I will either revert to a running instance if there is one or launching an instance if none is running. This is how other Activities work. That means I have found myself running multiple instances of Log.

Yep, same here. I often unintentionally end up with two instances of Log running while testing.

[godiard]

Probably we can go back and save the entry. The issue we tried to solve was have many unuseful Log entries in the Journal.

[walter]

FWIW:
4. This is the only Sugar activity that behaves this way (although some pseudo-activities -- not fully Sugarized -- have some similar behavior)

5. Given that the default behavior is launch most recent, the Journal spam argument is not relevant.

Yes. Please revert back to the old behavior.

[godiard]

Fixed in Log 28