Project

General

Profile

Actions

Emulator Issues #12246

open

Dolphin -d doesn't properly remember hiding the Code view

Added by ryanebola16 over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

What's the problem? Describe what went wrong.

This problem didn't appear until using a fresh build of Dolphin -d so old settings may affect it. Use a fresh build of Dolphin -d to test this issue.

In 5.0-12426, hiding the code view is not remembered when restarting Dolphin -d.

In 5.0-7062, where QT was made the default backend, hiding the code view then restarting Dolphin -d hid the code view properly but the "View" menu item was still checked. Although this was better, it means the Code view was probably implemented incorrectly from the beginning.

What steps will reproduce the problem?

  1. Run a fresh build of Dolphin -d. I used a portable instance for convenience.
  2. Disable the code view.
  3. Restart Dolphin -d.
  4. Observe variations of the code view not being disabled or the View menu item still being checked.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-12426

Is the issue present in the latest stable version?

Present on 5.0-7062, where QT was made the default backend, so probably not a regression.

What are your PC specifications? (CPU, GPU, Operating System, more)

Win 10 Pro x64
Intel Core i7-4702MQ CPU @2.20GHz
GeForce GT 750M
2x 8GB Hynix 1600MHz
GeForce Game Ready Driver 425.31

Actions #1

Updated by JosJuice over 3 years ago

Can't reproduce. Are you letting Dolphin exit cleanly?

Actions #2

Updated by ryanebola16 over 3 years ago

  • Status changed from New to Invalid

Interesting, now I can't reproduce it. I just did a few bisects so I'll assume something old was corrupting the config files. I'll reopen if I can reproduce this again.

Actions #3

Updated by ryanebola16 over 3 years ago

  • Status changed from Invalid to New

I reproduced it again. I don't know much about Qt.ini but the write to it that occurs at startup is writing showcode=true when it was showcode=false.

Actions

Also available in: Atom PDF