Bug 134840 - Allow to select screen for presentation with multi-monitors configuration
Summary: Allow to select screen for presentation with multi-monitors configuration
Status: REPORTED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-Presentation (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
: 373730 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-09-29 12:48 UTC by Elmar Stellnberger (AT/K)
Modified: 2016-12-22 14:37 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger (AT/K) 2006-09-29 12:48:03 UTC 
Version:           0.8.2 (using KDE 3.5.1 Level "a" , SUSE 10.1)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.21-0.25-default

I am using xinerama mode and can not controlle whether the dia show will start on my small notebook or my vast external screen. In some cases it may even make sense to show photos on the smaller screen (bigger TV with lower resolution).
  Perhaps this whis should better be posted in the context of a screen saver showing my photos automatically.
  Generally I would prefer working in dual head mode, but it does not allow applications once started on screen A to be switched to screen B. 
  Actually it does make much more sense to switch the content of the physical monitors A and B independently by kickers virtual desktop selector, which is provided by dual head mode, only !! Applications running on my left and my right screen are most times hardly related.
Comment 1 Elmar Stellnberger (AT/K) 2007-08-10 12:39:29 UTC 
Shows up on screen #2 by now, which actually is what I have wanted (thx). Nevertheless it may vary from case to case on which screen the presentation should take place (see Bug 148708).
Comment 2 caulier.gilles 2016-12-22 14:37:53 UTC 
*** Bug 373730 has been marked as a duplicate of this bug. ***