Skip to content

Q: Developer options from Reader - Guidance #11276

Description

@mergen3107

Many (many) times I've seen people stumble upon this situation:

  1. A user opens a brand new KOReader - it opens User Guide in Reader.
  2. Finds a bug soon, then go to create a new bug report ticket on GH.
  3. It says, enable Verbose logs from top menu - developer options, do the bug again and bring the crash.log here.
  4. User gets stuck, because Developer options menu entry is only available from FM. The come here to ask - making useful debugging times to be postponed by hours/days.

Now that we have this (phenomenal!) feature called Menu search - Walk me there, I suggest the following:

  1. In the Reader's Top menu - Tools - More Tools: create another menu entry that says Developer Options (walk me there).
  2. Once pressed, the button would close the top menu, exit to FM, then use the same code path as if the user searched for "developer" in the Menu search and hit the Walk me there button.

This will, I think/hope, tremendously improve the quality of bug reports.

Alternatively, just making a passive grayed out button that says Developer options (open from File Manager).

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions