[Bug 633581] commandline option "-f" or "--fullscreen" does nothing
0 views
Skip to first unread message
evince
Oct 5, 2012, 3:49:13 PM10/5/12
to tel.conn...@gmail.com
https://bugzilla.gnome.org/show_bug.cgi?id=633581
evince | win32 | 2.30.x
daedalusinfinity changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daedalus...@gmail.com
--- Comment #2 from daedalus...@gmail.com 2012-10-05 19:49:11 UTC ---
This is a problem for me when I don't specify a file name. However, when I do
specify a file name, it enters fullscreen correctly.
(Using Ubuntu 12.04 with version 3.4.0.)
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
evince | win32 | 2.30.x
daedalusinfinity changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daedalus...@gmail.com
--- Comment #2 from daedalus...@gmail.com 2012-10-05 19:49:11 UTC ---
This is a problem for me when I don't specify a file name. However, when I do
specify a file name, it enters fullscreen correctly.
(Using Ubuntu 12.04 with version 3.4.0.)
--
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
evince
Oct 5, 2012, 5:02:36 PM10/5/12
to tel.conn...@gmail.com
Germán Poo-Caamaño <gpoo> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |gp...@gnome.org
Resolution| |NOTABUG
--- Comment #3 from Germán Poo-Caamaño <gp...@gnome.org> 2012-10-05 21:02:29 UTC ---
If you do not have a document opened and switch to full screen, yo do not get
any access to the menu. So, to open a file you should switch to normal window,
open a file, switch to full screen.
The full screen mode does not make sense without a document opened.
I am closing it as 'not a bug'. If you have a clear use case for opening full
screen without a document, feel free to reopen it giving specific details.
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |gp...@gnome.org
Resolution| |NOTABUG
--- Comment #3 from Germán Poo-Caamaño <gp...@gnome.org> 2012-10-05 21:02:29 UTC ---
If you do not have a document opened and switch to full screen, yo do not get
any access to the menu. So, to open a file you should switch to normal window,
open a file, switch to full screen.
The full screen mode does not make sense without a document opened.
I am closing it as 'not a bug'. If you have a clear use case for opening full
screen without a document, feel free to reopen it giving specific details.
evince
Oct 5, 2012, 8:09:36 PM10/5/12
to tel.conn...@gmail.com
--- Comment #4 from daedalus...@gmail.com 2012-10-06 00:09:32 UTC ---
Personally, I prefer using CTRL+O to open up a file dialog (and I would imagine
most advanced users would also). In fact, I hardly ever use the menu bar.
Additionally, I think it would be good to change it because:
1. Consistency: having --fullscreen deviate from the usual behaviour in this
one case increases complexity.
2. User intention: If the user explicitly specified --fullscreen, then I think
we shouldn't make the decision for them to un-fullscreen it. (If they really
made a mistake, then they can disable fullscreen anyways.)
Personally, I prefer using CTRL+O to open up a file dialog (and I would imagine
most advanced users would also). In fact, I hardly ever use the menu bar.
Additionally, I think it would be good to change it because:
1. Consistency: having --fullscreen deviate from the usual behaviour in this
one case increases complexity.
2. User intention: If the user explicitly specified --fullscreen, then I think
we shouldn't make the decision for them to un-fullscreen it. (If they really
made a mistake, then they can disable fullscreen anyways.)
evince
Oct 5, 2012, 11:25:54 PM10/5/12
to tel.conn...@gmail.com
--- Comment #5 from daedalus...@gmail.com 2012-10-06 03:25:52 UTC ---
(In reply to comment #3)
permissions to do so. However, I'd be more than willing to send in a patch,
which involves changing all of 4 lines in "shell/main.c".
(In reply to comment #3)
> If you do not have a document opened and switch to full screen, yo do not get
> any access to the menu. So, to open a file you should switch to normal window,
> open a file, switch to full screen.
>
> The full screen mode does not make sense without a document opened.
>
> I am closing it as 'not a bug'. If you have a clear use case for opening full
> screen without a document, feel free to reopen it giving specific details.
I don't know how to reopen the bug; I presume that I probably don't have the
> any access to the menu. So, to open a file you should switch to normal window,
> open a file, switch to full screen.
>
> The full screen mode does not make sense without a document opened.
>
> I am closing it as 'not a bug'. If you have a clear use case for opening full
> screen without a document, feel free to reopen it giving specific details.
permissions to do so. However, I'd be more than willing to send in a patch,
which involves changing all of 4 lines in "shell/main.c".
evince
Oct 5, 2012, 11:50:20 PM10/5/12
to tel.conn...@gmail.com
--- Comment #6 from daedalus...@gmail.com 2012-10-06 03:50:16 UTC ---
(In reply to comment #5)
a patch nonetheless.
(In reply to comment #5)
> (In reply to comment #3)
> > If you do not have a document opened and switch to full screen, yo do not get
> > any access to the menu. So, to open a file you should switch to normal window,
> > open a file, switch to full screen.
> >
> > The full screen mode does not make sense without a document opened.
> >
> > I am closing it as 'not a bug'. If you have a clear use case for opening full
> > screen without a document, feel free to reopen it giving specific details.
>
> I don't know how to reopen the bug; I presume that I probably don't have the
> permissions to do so. However, I'd be more than willing to send in a patch,
> which involves changing all of 4 lines in "shell/main.c".
Actually, my mistake -- it takes more than 4 lines, but I'd be willing to write
> > If you do not have a document opened and switch to full screen, yo do not get
> > any access to the menu. So, to open a file you should switch to normal window,
> > open a file, switch to full screen.
> >
> > The full screen mode does not make sense without a document opened.
> >
> > I am closing it as 'not a bug'. If you have a clear use case for opening full
> > screen without a document, feel free to reopen it giving specific details.
>
> I don't know how to reopen the bug; I presume that I probably don't have the
> permissions to do so. However, I'd be more than willing to send in a patch,
> which involves changing all of 4 lines in "shell/main.c".
a patch nonetheless.
evince
Oct 6, 2012, 2:21:34 AM10/6/12
to tel.conn...@gmail.com
--- Comment #7 from Germán Poo-Caamaño <gp...@gnome.org> 2012-10-06 06:21:30 UTC ---
Whenever you open a document, evince launches a new window.
So, you would need to consider that situation.(In reply to comment #4)
if the current one does not a document.
> Additionally, I think it would be good to change it because:
> 1. Consistency: having --fullscreen deviate from the usual behaviour in this
> one case increases complexity.
A fix for that is to require an argument (filename) when using this option.
> 2. User intention: If the user explicitly specified --fullscreen, then I think
> we shouldn't make the decision for them to un-fullscreen it. (If they really
> made a mistake, then they can disable fullscreen anyways.)
If the user can explicitly launch in full screen, why the user does not provide
the file name at the same time?
Whenever you open a document, evince launches a new window.
So, you would need to consider that situation.(In reply to comment #4)
> Personally, I prefer using CTRL+O to open up a file dialog (and I would imagine
> most advanced users would also). In fact, I hardly ever use the menu bar.
Still, the evince behaviour is to open any new file in a new window, not matter
> most advanced users would also). In fact, I hardly ever use the menu bar.
if the current one does not a document.
> Additionally, I think it would be good to change it because:
> 1. Consistency: having --fullscreen deviate from the usual behaviour in this
> one case increases complexity.
> 2. User intention: If the user explicitly specified --fullscreen, then I think
> we shouldn't make the decision for them to un-fullscreen it. (If they really
> made a mistake, then they can disable fullscreen anyways.)
the file name at the same time?
evince
Oct 6, 2012, 3:21:59 AM10/6/12
to tel.conn...@gmail.com
--- Comment #8 from daedalus...@gmail.com 2012-10-06 07:21:52 UTC ---
(In reply to comment #7)
blank window), and then I open a file, the file appears in the 'same' window.
Furthermore, if the original (empty) window was fullscreen, then the window
with the new file is also fullscreen, so even if the underlying mechanism
actually does 'launch a new window', it still transfers a nontrivial amount of
the state from the 'old' window into the 'new' one.
Lastly, I don't see how this pertains to my point.
> > Additionally, I think it would be good to change it because:
> > 1. Consistency: having --fullscreen deviate from the usual behaviour in this
> > one case increases complexity.
>
> A fix for that is to require an argument (filename) when using this option.
This makes sense, assuming you also disable the option to fullscreen an empty
window once Evince is loaded. In essence, my point is:
1. Allowing presentation/fullscreen display if and only if a file is loaded is
consistent (provided you explicitly state this fact in the man page).
2. Alternatively, allowing presentation/fullscreen display at all times is
consistent.
3. Allowing fullscreen not from the command line without loading a file, but
allowing it from within the GUI without a file, and allowing it at all times
with a file loaded is unnecessarily complicated.
Alternatively, I feel like the two statements are equivalent:
1. There exists a use case for allowing fullscreening an empty window while the
application is loaded.
2. There exists a use case for allowing fullscreening from the command line
without a file.
> > 2. User intention: If the user explicitly specified --fullscreen, then I think
> > we shouldn't make the decision for them to un-fullscreen it. (If they really
> > made a mistake, then they can disable fullscreen anyways.)
>
> If the user can explicitly launch in full screen, why the user does not provide
> the file name at the same time?
I'm not interested in what the user 'can' do, but what the user did explicitly,
verbally, specify. (However, this issue can be resolved if we define launching
fullscreen without a file as invalid, and inform the user about this fact.)
(In reply to comment #7)
> Whenever you open a document, evince launches a new window.
>
> So, you would need to consider that situation.(In reply to comment #4)
> > Personally, I prefer using CTRL+O to open up a file dialog (and I would imagine
> > most advanced users would also). In fact, I hardly ever use the menu bar.
>
> Still, the evince behaviour is to open any new file in a new window, not matter
> if the current one does not a document.
What do you mean by a "new" window? If I start a new Evince session (with a
>
> So, you would need to consider that situation.(In reply to comment #4)
> > Personally, I prefer using CTRL+O to open up a file dialog (and I would imagine
> > most advanced users would also). In fact, I hardly ever use the menu bar.
>
> Still, the evince behaviour is to open any new file in a new window, not matter
> if the current one does not a document.
blank window), and then I open a file, the file appears in the 'same' window.
Furthermore, if the original (empty) window was fullscreen, then the window
with the new file is also fullscreen, so even if the underlying mechanism
actually does 'launch a new window', it still transfers a nontrivial amount of
the state from the 'old' window into the 'new' one.
Lastly, I don't see how this pertains to my point.
> > Additionally, I think it would be good to change it because:
> > 1. Consistency: having --fullscreen deviate from the usual behaviour in this
> > one case increases complexity.
>
> A fix for that is to require an argument (filename) when using this option.
window once Evince is loaded. In essence, my point is:
1. Allowing presentation/fullscreen display if and only if a file is loaded is
consistent (provided you explicitly state this fact in the man page).
2. Alternatively, allowing presentation/fullscreen display at all times is
consistent.
3. Allowing fullscreen not from the command line without loading a file, but
allowing it from within the GUI without a file, and allowing it at all times
with a file loaded is unnecessarily complicated.
Alternatively, I feel like the two statements are equivalent:
1. There exists a use case for allowing fullscreening an empty window while the
application is loaded.
2. There exists a use case for allowing fullscreening from the command line
without a file.
> > 2. User intention: If the user explicitly specified --fullscreen, then I think
> > we shouldn't make the decision for them to un-fullscreen it. (If they really
> > made a mistake, then they can disable fullscreen anyways.)
>
> If the user can explicitly launch in full screen, why the user does not provide
> the file name at the same time?
verbally, specify. (However, this issue can be resolved if we define launching
fullscreen without a file as invalid, and inform the user about this fact.)
Reply all
Reply to author
Forward
0 new messages