Yes I know that channel:peek() is just channel:pop() but without changing the queue. But I want to make sure I don't receive any messages from myself. Or is that already taken care of by LÖVE? I thought channel:pop() did modify some internal state, the queue.

That's strange... I thought channel:pop() was describable as: Or am I missing something here? In my code it doesn't work...

EDIT: So, the wiki was wrong, thanks for editing!

I know the usage of the channel functions. I had already tried it, of course, because it seems so unlogical. When I try to receive a flat table with channel:peek(), it just doesn't receive it. It really doesn't work.

Something related: Why do all the channel functions accept flat tables, but the channel.peek() function doesn't?

EDIT: Bitser may be really helpful if I get stuck on this problem

raidho36 wrote:Why wouldn't it be?

Code: Select all

local a = { }
local b = { }
a.b = b
b.a = a

Okay, that's simple indeed, now I get it.

bartbes wrote:Serialization code that only supports tables without cyclic references can be much simpler and faster than code that does have to support those, for instance.

What are cyclic references? A table referencing itself? Is that even possible in lua?

Maybe this is a stupid question, but why aren't we able to send nested tables over channels? Is it impossible or very hard to make? Is there a solution to send nested tables over channels? Serializing? Repeated channel sends? EDIT: I want to send something like this: local t = { { type = "foo&q...

So, the easyest (and maybe the best) option is to set the window to borderless and make my own title bar I think.
Thanks for all the reactions BTW!

Hello, I was playing around with graphics, and I have just installed windows 10 with its fancy graphics, so I was thinking: Is it possible to get the RGB value of the window color, to set it as a background? (Or maybe even setting it to another color?) That would be nice to have. I want to make some...