sqlitebrowser / sqlitebrowser/sqlitebrowser

[Bug]: appimage linux, initial "Wrap line" state is wrong

Open
#3,061 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browse data gui
Dominant language
C++
Stars
24.6k
Forks
2.4k
Avg merge
3d 49m
Merged PRs (30d)
3

Description

What did you do?
  • Run DB4S appimage build (2022-05-20 download)
  • "Preferences > SQL > Wrap lines" left to default value "NEVER".
  • Open a database with long text lines.
  • "Browser Data" > open a table with long text lines.
  • Mouse click a cell with long text lines.
  • File menu > View > Edit Database Cell
  • Now, the default "Wrap lines on word boundaries" button in toggled on.
What did you expect to see?

The "Wrap lines on word boundaries" button indicate actual wrap state, which is UNWRAPPED (OFF) by "Preferences > SQL > Wrap lines" value.

What did you see instead?

Long lines in database cell is displayed in unwrapped state. Though the "Wrap lines on word boundaries" button indicate WRAPPED (ON) state, which is not the act.

According to post,
https://github.com/sqlitebrowser/sqlitebrowser/issues/1796
the workaround is set "Preferences > SQL > Wrap lines" to other values apart from default "Never".

The focus of this report is that the initial state of "Wrap lines on word boundaries" is wrong.

DB4S Version

3.12.99 (nightly)

What OS are you seeing the problem on?

Linux

OS version

Debian 10 x64, latest update

Relevant log output

No response

Prevention against duplicate issues
  • I have searched for similar issues

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Reproduce the issue in the Linux AppImage by leaving Preferences > SQL > Wrap lines at NEVER, opening a long-text cell, and choosing File > View > Edit Database Cell; trace the cell editor's initial wrap-state handling. Done means the button indicates the actual unwrapped state.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, sqlite
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.