Messages

1

General discussions / Project setup with cmake and git submodules

« on: January 01, 2021, 09:25:24 pm »

Hey all. To start the new year off right I have been assessing c++ package managers and, well, I have already given up. So I made doc for myself how to setup with cmake and git submodules. I use SFML as an example so I thought perhaps it may help someone here to get setup as well. Let me know if you have any troubles with it.

The doc is a github gist...

https://gist.github.com/mtvee/f41caba1ab080639fe6eec31828f34ff

cheers and happy new year!

2

System / Re: We got a keyboard without any keys (1) (OSX Big Sur)

« on: November 25, 2020, 04:41:16 pm »

I don't know why it happened. I wiped and reinstalled everything and it magically went away. Old libs, link one lib, use another at runtime? Sometimes cmake does weird things with caches and such too. Also using Clion and these IDEs are handy but sometimes you're never really sure what they are doing back there. Who knows? Sorry for noise. I should have just wiped it from the start.

3

System / We got a keyboard without any keys (1) (OSX Big Sur)

« on: November 20, 2020, 01:53:23 pm »

I get this error "We got a keyboard without any keys (1)" all of a sudden after upgrade to Big Sur. I was going to put up a report on github but thought i would post here first incase I am doing something dumb or this is a known thing.

This happens with my code and the SFML example code as well so I didn't bother making a minimal example

System is:

macOS Big Sur 11.0.1
MacBook Air

SFML 2.5.1 built from source with cmake and default install

edit: here's a gist with minimal example https://gist.github.com/mtvee/e82ef146e7f1ef6c816e27d7a16a7a79

edit: if anyone can verify this one way or the other i would be grateful so I know where to dig. thanks!


edit: i think i got this pegged as some cruft from the Big Sur upgrade and not SFML. Apologies for the noise.

4

SFML projects / yet another GUI (aka nanosfml)

« on: September 29, 2017, 06:11:34 pm »

Hi folks. I've been fooling around with https://github.com/wjakob/nanogui and ended up porting a large chunk of it to SFML, that is, the underlying drawing routines (replacing nanovg). I am posting because I don't know if I should clean this up and make it available on github, as in, would there be any interest in this from you guys?

If you don't know nanogui (https://github.com/wjakob/nanogui) I suggest going and checking it out. I find it's nice and light and easy to deal with so it made some sense for me to replace the guts with SFML for the stuff I do. I have no idea how you folks would feel about that. I've tried somewhat to keep the gui creation process the same as nano. I have not ported every widget as some of them I have no use for but at this point it wouldn't be too hard to port the last few over. Currently the widgets are: windows, layouts, text input, slider, checkbox, labels, buttons, messagedialog and a textview for readonly text blobs. I have also added a way to theme it from json which I find handy.

All that said, the project is a bit messy at this point because it's just me messing around, and a few things don't work they way the should. Text input being the thorn in my side at the moment. So I have two questions for you and "you're nuts" is totally a valid answer

• Would you be interested in this for your projects?
  
• Would you be willing to contribute some ports/widgets/fixes?
  

Thanks for reading!
 

5

Audio / Re: open AL unexpected message

« on: March 24, 2017, 07:06:03 pm »

Are the SoundBuffers initialized in a global scope?

No, they are contained in a ResourceManager class which is basically a std::unordered_map[key] = SoundBuffer. I have several maps for various asset types.

6

Audio / Re: open AL unexpected message

« on: March 24, 2017, 02:12:01 pm »

You get this when you do what exactly?

I load a couple of ogg files into SoundBuffers. I'm not even playing them or even create an sf::Sound. Just load two buffers.

7

Audio / Re: open AL unexpected message

« on: March 23, 2017, 08:07:35 pm »

I'm getting this too, win 10, audio card is fine, using openal.dll that ships with sfml. The following is from the console.

An internal OpenAL call failed in SoundBuffer.cpp(46).
Expression:
   alGenBuffers(1, &m_buffer)
Error description:
   AL_INVALID_OPERATION
   The specified operation is not allowed in the current state.

AL lib: (EE) MMDevApiMsgProc: Unexpected message: 49281
An internal OpenAL call failed in SoundBuffer.cpp(265).
Expression:
   alBufferData(m_buffer, format, &m_samples[0], size, sampleRate)
Error description:
   AL_INVALID_OPERATION
   The specified operation is not allowed in the current state.

An internal OpenAL call failed in SoundBuffer.cpp(46).
Expression:
   alGenBuffers(1, &m_buffer)
Error description:
   AL_INVALID_OPERATION
   The specified operation is not allowed in the current state.

An internal OpenAL call failed in SoundBuffer.cpp(265).
Expression:
   alBufferData(m_buffer, format, &m_samples[0], size, sampleRate)
Error description:
   AL_INVALID_OPERATION
   The specified operation is not allowed in the current state.