Bug 245333 - KPresenter window size is too large to use
Summary: KPresenter window size is too large to use
Status: RESOLVED WORKSFORME
Alias: None
Product: calligrastage
Classification: Applications
Component: usability (other bugs)
Version First Reported In: 2.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: T Zachmann
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-21 17:46 UTC by 白川間瀬流
Modified: 2023-02-12 03:49 UTC (History)
1 user (show)

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


Attachments
Screenshot (106.31 KB, image/jpeg)
2010-07-21 17:46 UTC, 白川間瀬流
Details

Note You need to log in before you can comment on or make changes to this bug.
Description 白川間瀬流 2010-07-21 17:46:04 UTC
Created attachment 49366 [details]
Screenshot

Version:           2.1 (using KDE 4.4.4) 
OS:                Linux

At my Resolution of 1280x800 im completely unable to use KPresenter. The Window is to large so a lot of important stuff is hidden. If i try to click something the windows jumps and jumps to try to fit into the screen.

Reproducible: Always

Steps to Reproduce:
Start KPresenter in 1280x800

Actual Results:  
Jump and jump and jump and ...

Expected Results:  
No Jumps^^
Comment 1 beojan 2013-03-14 17:49:39 UTC
This bug continues to appear in calligra 2.7 pre-alpha (resolution is 1366x768), in most applications (especially Words and Krita) when the default docker setup causes the window to be larger than the screen. Unfortunately, setting the dockers on both sides of the screen in Words such that they fit on the screen leaves insufficient room for the document itself.
Comment 2 Andrew Crouthamel 2018-11-10 03:22:08 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-11-21 04:47:29 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2023-01-13 01:36:05 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-28 05:07:50 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2023-02-12 03:49:59 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!