Bug 485320 - Wishlist: remember scanning resolution between invocation
Summary: Wishlist: remember scanning resolution between invocation
Status: CONFIRMED
Alias: None
Product: libksane
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 24.02.1
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kåre Särs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-10 12:19 UTC by Sergio
Modified: 2024-04-11 12:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sergio 2024-04-10 12:19:01 UTC
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

SUMMARY

Every time you start skanlite, the scan resolution gets reset to a default value that is typically inappropriate. For instance, with my HP scanner, every time you start skanlite the resolution is set at 75dpi, which is not something you generally want to use.

STEPS TO REPRODUCE
1. Start skanlite
2. Set resolution to 300dpi, work
3. Exit
4. Start skanlite

OBSERVED RESULT

Resolution is not what you had previously set

EXPECTED RESULT

Skanlite should preserve, across invokations and on a pre-scanner basis, some common settings such as the resolution and possibly the scan area. 

SOFTWARE/OS VERSIONS

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.6.25-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4750HQ CPU @ 2.00GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Pro Graphics P5200
Manufacturer: Notebook
Product Name: W740SU
System Version: Not Applicable

ADDITIONAL INFORMATION

N/A
Comment 1 Kåre Särs 2024-04-11 12:51:24 UTC
Thanks for the report!

This is most probably an issue with the order of the scanner options.

When we save the options, we write them back in that same order that we get them. if the resolution is set before the scan source or mode, the resolution is probably reset when the scan-source or mode is set....

There would be a need to make it possible to apply the saved options in the right order.... I wonder if some crashes with some backends might be because of this order too...