~theclapp


#22 Problems running go-life on Windows 10 native 3 days ago

Comment by ~theclapp on ~eliasnaur/gio

I got the VB image downloaded. Without even starting it, I looked at its display settings. It had both 3D and 2D acceleration disabled! So I went to my own VM, disabled both, and then go-life worked!

I re-enabled 2D acceleration and it still worked.

So looks like something is wrong with their 3D acceleration? I dunno.

Anyway I think we can close this ticket. Since some code did change as a result of it, I'm marking it FIXED.

Thank you for your help!

REPORTED RESOLVED FIXED

#22 Problems running go-life on Windows 10 native 3 days ago

Comment by ~theclapp on ~eliasnaur/gio

I won't have access to the Fedora 30 I tried Windows on, sorry.

No worries.

I can tell you that I didn't change anything - I imported the image from the link above and accepted the defaults VirtualBox presented.

Cool. I'm downloading the VB image now.

#22 Problems running go-life on Windows 10 native 3 days ago

Comment by ~theclapp on ~eliasnaur/gio

Well, maybe we can just figure out the VB settings or version of Windows I need.

What version of Windows is the image running? What are your Virtual Box settings? In particular, what's the VB Display -> Graphics Controller? Inside Windows, what's the display adapter? And anything else that seems appropriate.

As mentioned above, I'm running VBoxVGA with 2D & 3D acceleration enabled. The VMSVGA (which I've since learned is a VMWare driver? or emulation of their driver?) does run Gio, but has some drawbacks (like it won't resize the VM window to arbitrary sizes). The VBoxSVGA driver doesn't run Gio.

So, what's a config (feel free to just point me to relevant docs) and what could I try on my end?

#18 Add menubar interaction 4 days ago

Comment by ~theclapp on ~eliasnaur/gio

In macOS, the ability to not show up in ⌘-TAB or on the menu-bar would also be useful.

For example, if you're simulating multiple top-level windows by running multiple instances of your app, each with its own top-level window, you'd only want one of them to show up in the ⌘-TAB list, or on the menubar. Windows and Linux would have similar wants.

You'd probably also need this if you want to write a gadget that draws on the macOS menu-bar, a-la iStat Menus (https://bjango.com/mac/istatmenus/). (This is a very different kind of menubar interaction and may deserve its own ticket.)

#22 Problems running go-life on Windows 10 native 4 days ago

Comment by ~theclapp on ~eliasnaur/gio

It does, thanks!

Re: the specific error: If I understand correctly (which I might not), we get back EGL_BAD_CONFIG. I don't really understand the GL config thing. Does that mean we asked for a particular config, or set of configs, and the GL library said basically nothing I have matched what you're asking for?

And if so ... is there any chance we can ask for something else, that would work?

#22 Problems running go-life on Windows 10 native 4 days ago

Comment by ~theclapp on ~eliasnaur/gio

I guess I was suggesting that, yeah, but when you put it that way, never mind. :) That seems sufficient.

It does seem a little weird that it gets far enough to pop up a window and then dies. (At least I think that's what it did; I'm away from that computer right now.) But we'll probably just have to live with that.

#22 Problems running go-life on Windows 10 native 4 days ago

Comment by ~theclapp on ~eliasnaur/gio

Yeah, the virtual machine substrate / hardware are important. I'm running Virtual Box. So I think it comes down to hardware / driver support. So I don't think Gio is doing anything wrong or bad.

That said, it would be nice if Gio could detect the lack of support for what it needs, so devs like me and users like my friend on Slack know that it'll just never work. Did you try the Virtual Box image, or something else? I know it's a lot of trouble, but maybe try to find one that doesn't work and then you can troubleshoot the capability checking Gio needs to do?

#22 Problems running go-life on Windows 10 native 5 days ago

Comment by ~theclapp on ~eliasnaur/gio

On Mon, Aug 12, 2019 at 8:34 AM ~eliasnaur outgoing@sr.ht wrote:

Did your friend's Windows run go-life if he puts the ANGLE dlls in the dll search path (or current directory)?

He has not reported back. If I don't hear from him I'll ping him tomorrow.

If so, this issue should be renamed to something about virtual Windows.

That's a good point.

This was in the Gophers showandtell channel, btw. See https://gophers.slack.com/archives/C02A3DRK6/p1565482138087000.

(I also created a #gioui channel (https://gophers.slack.com/archives/CM87SNCGM/p1565385539002600). I know you're not a fan of Slack (and I mentioned this in the channel), but I'm fine with it. :)

-- L

#22 Problems running go-life on Windows 10 native 5 days ago

Comment by ~theclapp on ~eliasnaur/gio

According to a random Stack Overflow message, VirtualBox doesn't use the GPU, which seems like that could be problematic? I haven't been able to verify that, though.

https://askubuntu.com/questions/943110/how-to-assign-more-than-256mb-of-video-memory-in-virtualbox

-- L

#22 Problems running go-life on Windows 10 native 5 days ago

Comment by ~theclapp on ~eliasnaur/gio

On Sun, Aug 11, 2019 at 10:19:30PM -0400, Larry Clapp wrote:

I'll try some other VBox Graphics Controllers.

I tried the one called VMSVGA and go-life worked in that one. (Weirdly, scroll events only report in the Y axis; the X axis is all 0.)

A nice feature of the other graphics controller broke, though: It can no longer resize the vm resolution to match the host window size, which is a bit of a pain.

-- L