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

fullscreen is blank using [gemcocoawindow] OSX 10.12 #151

Open
megrimm opened this Issue Aug 25, 2017 · 20 comments

Comments

Projects
None yet
4 participants
@megrimm
Contributor

megrimm commented Aug 25, 2017

so going to fullscreen the window just goes white/blank. see attached screen shots.
screen shot 2017-08-25 at 11 51 01 am
screen shot 2017-08-25 at 11 51 18 am

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Aug 25, 2017

Owner

what's those red lines in the background?

Owner

umlaeute commented Aug 25, 2017

what's those red lines in the background?

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Aug 25, 2017

Contributor

i should have mention that...
those are if gem window already made because i was banging [create, 1( a bunch of times:
[gemcocoawindow]: window already made!

BUT (not in that screenshot) im also getting:
[gemcocoawindow]: unable to switch to current window (do you have one?), cannot render!

although it does render... im trying to figure this out but it seems to occur when i send a [0,destroy( to [gemwin] whether the window is open or not
screen shot 2017-08-25 at 1 00 50 pm

Contributor

megrimm commented Aug 25, 2017

i should have mention that...
those are if gem window already made because i was banging [create, 1( a bunch of times:
[gemcocoawindow]: window already made!

BUT (not in that screenshot) im also getting:
[gemcocoawindow]: unable to switch to current window (do you have one?), cannot render!

although it does render... im trying to figure this out but it seems to occur when i send a [0,destroy( to [gemwin] whether the window is open or not
screen shot 2017-08-25 at 1 00 50 pm

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Aug 28, 2017

Owner

also

  • does the [gemhead] emit messages if nothing is rendered?
  • if you set a background colour for the gemwin, does that get rendered?
Owner

umlaeute commented Aug 28, 2017

also

  • does the [gemhead] emit messages if nothing is rendered?
  • if you set a background colour for the gemwin, does that get rendered?
@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Aug 29, 2017

Contributor

yeah still sends messages in fullscreen although nothing is visable:

print: gem_state 0
print: gem_state 1
print: gem_state (pointer) (pointer)

and nope... no color.

you want screen grabs of any of this?

Contributor

megrimm commented Aug 29, 2017

yeah still sends messages in fullscreen although nothing is visable:

print: gem_state 0
print: gem_state 1
print: gem_state (pointer) (pointer)

and nope... no color.

you want screen grabs of any of this?

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Aug 31, 2017

Contributor

so removing line 368 in gemcocoawindow.mm seems to do the trick. I get fullscreen rendering...

though with [menubar 0, fullscreen 1, create, 1( i still get osx menubar....

screen shot 2017-08-31 at 6 51 37 pm

Contributor

megrimm commented Aug 31, 2017

so removing line 368 in gemcocoawindow.mm seems to do the trick. I get fullscreen rendering...

though with [menubar 0, fullscreen 1, create, 1( i still get osx menubar....

screen shot 2017-08-31 at 6 51 37 pm

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 1, 2017

Owner

afaict, gemcocoawindow.mm:368 disables fullscreen rendering (that line is supposed to enable FS on "renderers that support it").

So, to make sure I understand:

  • with this line, you get a full-screen line without the menubar (but unfortunately without rendering)
  • without this line, you still get full-screen, but with the menubar
  • you are using a software renderer on your system (that's what i gather from here)
  • can other openGL applications successfully do full-screen (without menubar)?
Owner

umlaeute commented Sep 1, 2017

afaict, gemcocoawindow.mm:368 disables fullscreen rendering (that line is supposed to enable FS on "renderers that support it").

So, to make sure I understand:

  • with this line, you get a full-screen line without the menubar (but unfortunately without rendering)
  • without this line, you still get full-screen, but with the menubar
  • you are using a software renderer on your system (that's what i gather from here)
  • can other openGL applications successfully do full-screen (without menubar)?
@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 1, 2017

Contributor
Contributor

megrimm commented Sep 1, 2017

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 1, 2017

Contributor
Contributor

megrimm commented Sep 1, 2017

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 2, 2017

Contributor

fyi i created a PR here that hopefully begins fixing things...

Contributor

megrimm commented Sep 2, 2017

fyi i created a PR here that hopefully begins fixing things...

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 15, 2017

Owner

i'm tempted to include the "remove gemcocoawindow.mm:368" fix (until the PRs are sorted out).
does that sound ok?

Owner

umlaeute commented Sep 15, 2017

i'm tempted to include the "remove gemcocoawindow.mm:368" fix (until the PRs are sorted out).
does that sound ok?

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 15, 2017

Contributor
Contributor

megrimm commented Sep 15, 2017

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 15, 2017

Owner

re-learn what? mostly just take your current code, put it into a separate file with all the names changed and do a new PR, based on the current master (of this repo).

no idea about the name.

Owner

umlaeute commented Sep 15, 2017

re-learn what? mostly just take your current code, put it into a separate file with all the names changed and do a new PR, based on the current master (of this repo).

no idea about the name.

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 15, 2017

Contributor
Contributor

megrimm commented Sep 15, 2017

@Ant1r

This comment has been minimized.

Show comment
Hide comment
@Ant1r

Ant1r Sep 16, 2017

Contributor

[gemosxwindow] ?

Contributor

Ant1r commented Sep 16, 2017

[gemosxwindow] ?

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 16, 2017

Owner
Owner

umlaeute commented Sep 16, 2017

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Sep 16, 2017

Contributor
Contributor

megrimm commented Sep 16, 2017

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Sep 19, 2017

Owner

probably [gemmacoswindow] is the only name in that list that can be remembered by humans.

Owner

umlaeute commented Sep 19, 2017

probably [gemmacoswindow] is the only name in that list that can be remembered by humans.

@umlaeute umlaeute added the bug label Nov 16, 2017

@umlaeute

This comment has been minimized.

Show comment
Hide comment
@umlaeute

umlaeute Dec 5, 2017

Owner

any news?

Owner

umlaeute commented Dec 5, 2017

any news?

@megrimm

This comment has been minimized.

Show comment
Hide comment
@megrimm

megrimm Dec 11, 2017

Contributor

[gemmacoswindow] sounds good... i just never did this and ran out of time to work on it and at moment have actually forgotten where it was left. might have time in a couple weeks to have another go at it.

Contributor

megrimm commented Dec 11, 2017

[gemmacoswindow] sounds good... i just never did this and ran out of time to work on it and at moment have actually forgotten where it was left. might have time in a couple weeks to have another go at it.

@virusys

This comment has been minimized.

Show comment
Hide comment
@virusys

virusys Apr 28, 2018

Hi Everyone, I recently compiled Gem for macOS 10.13.3, and I'm getting this error with the [gemmacoswindow]:

screen shot 2018-04-28 at 8 03 12 am

The red lines appear as soon as I try to create the window. So far I've only been able to get the [gemglutwindow] object to work, but I'm getting some problems with that as well.

Any suggestions? If you need more info let me know as well.

virusys commented Apr 28, 2018

Hi Everyone, I recently compiled Gem for macOS 10.13.3, and I'm getting this error with the [gemmacoswindow]:

screen shot 2018-04-28 at 8 03 12 am

The red lines appear as soon as I try to create the window. So far I've only been able to get the [gemglutwindow] object to work, but I'm getting some problems with that as well.

Any suggestions? If you need more info let me know as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment