Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about window size #54

Closed
susobaco opened this issue Feb 8, 2018 · 3 comments
Closed

Question about window size #54

susobaco opened this issue Feb 8, 2018 · 3 comments

Comments

@susobaco
Copy link
Contributor

susobaco commented Feb 8, 2018

Hi, congratulations on your show. I have a question. In a dual monitor presentation, it is possible to start the fulscreen presentation, but it is possible that the other window, the control window, will not start full screen? I'd like a small window. I've tried it with the openbox configuration, but the output of "xprop | grep class" is the same for both windows, so I can't define the size for a single window.
I am using the latest version of pympres on lxde in Tisquel 8 (ubuntu 16.04). Thank you for your work.

@Cimbali
Copy link
Owner

Cimbali commented Feb 8, 2018

HI @susobaco you should look at the "Startup configuration" menu and tick "Content fullscreen" and untick "Presenter fullscreen". The presenter (or control as you say) window will probably still start maximized but not fullscreen.

Also I don't know much about openbox configurations, but from what I see in xprop:

  • the presenter window allows the maximized actions but the content window doesn't, so you could try applying it to both and seeing what happens.
  • the windows have the same class but different names "pympress presenter" and "pympress content" so maybe you could filter by that.

@susobaco
Copy link
Contributor Author

susobaco commented Feb 9, 2018

Hello, the result is the same following your instructions.
The xprop outputs:

_OB_APP_TYPE(UTF8_STRING) = "normal"
_OB_APP_TITLE(UTF8_STRING) = "pympress presenter"
_OB_APP_GROUP_CLASS(UTF8_STRING) =
_OB_APP_GROUP_NAME(UTF8_STRING) = "pympress"
_OB_APP_CLASS(UTF8_STRING) = "Pympress"
_OB_APP_NAME(UTF8_STRING) = "pympress"
_OB_APP_ROLE(UTF8_STRING) =
_NET_WM_VISIBLE_ICON_NAME(UTF8_STRING) = "pympress presenter"
_NET_WM_VISIBLE_NAME(UTF8_STRING) = "pympress presenter"

_OB_APP_TYPE(UTF8_STRING) = "normal"
_OB_APP_TITLE(UTF8_STRING) = "Pympress Content"
_OB_APP_GROUP_CLASS(UTF8_STRING) =
_OB_APP_GROUP_NAME(UTF8_STRING) = "pympress"
_OB_APP_CLASS(UTF8_STRING) = "Pympress"
_OB_APP_NAME(UTF8_STRING) = "pympress"
_OB_APP_ROLE(UTF8_STRING) =
_NET_WM_VISIBLE_ICON_NAME(UTF8_STRING) = "Pympress Content"
_NET_WM_VISIBLE_NAME(UTF8_STRING) = "Pympress Content"

The name is different, but in order for the openbox configuration to work, the "class" or "role" must be different.

@Cimbali Cimbali closed this as completed in 68da13c Feb 9, 2018
@Cimbali
Copy link
Owner

Cimbali commented Feb 9, 2018

There you go, now the windows have different roles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants