Best wishes for the health of Cookie.

Unfortunately, our kitty "Cookie" has fallen ill. She hasn't been eating, doing much of anything, and is lethargic all of the time now. Being 16 years old, I should have expected this to happen. So, I'll be taking a sort of "leave of absence" for a while. Until when, I have no idea. I'll be announcing this on Discord at some point. Also, I won't be working on level packs until I know what's going on with Cookie. I'll eventually message collab developers regarding this as well. Thank you in advance for understanding.

Ah yes, if the idea is to get a solid background colour, that's the way to do it

EDIT: This topic has now been marked as resolved.

No Will, I don't need anything... for the moment.
All the features are available in the excellent editor that I'm learning to use by trial and error.

And precisely in error mode, I was simply using the Gridsize 1 in workaround to get a solid background different from the standard black (invisible) background when practicing with the editor, but this is not the right solution because the background chosen this way is not saved when you save the created level.

So, as an exercise, I created a chroda_background style folder with a backgrounds subfolder in which I placed several 32x32 pixel images in colors such as blue, gray, midnight, and yellow. This way, when I select this style and a background image, the chosen background is saved when I restart the level created with this background and so everything is OK.

Voilà!

I'm not sure I understand exactly what you're after here @chroda, and therefore also don't understand how Proxima's suggested solution helps.

Could you perhaps elaborate on what's needed? It may be something we can work into the Editor's functionality if it's (a) not too obscure, (b) would prevent the need for a workaround, and (c) would help others with the same use case.

With a 7 to 3 vote, from now on the result of the vote will only be visible after the timer has run out. 

I will apply the voted on changes in the next contest!

I recall there being code to intercept certain keyboard or mouse inputs (I'm fuzzy on the exact details) and not pass them on to further handlers under certain circumstances. My hunch is this relates to the code for treating MMB / RMB as "just another keyboard hotkey" though I'm far from certian on this (eg. it might also have been to do with the minimap or skill panel). This might be worth looking at here.

Before that though: I'd test if Lemmix and/or very old versions of NL (before hotkeys were customizable) also has this issue. If it does, it's very likely something relating to Delphi's input handling rather than NL-specific code. (This does not mean there won't be a workaround of some kind, of course. It just helps figure out where to focus efforts.)

QuoteYou can already do that

For me, size 1 grid allowed me to have a uniform background (without grid) of a color other than invisible (black), and that was what mattered to me rather than the grid itself. It wasn't the right way to proceed, but it allowed WillLem to make a correction that will be included in the next version.

Yeah, of course your suggestion is the right solution to use and it works perfectly.
Thanks Proxima

You can already do that; create a background image that's a single colour, and place it in the "backgrounds" folder inside the style folder. See the ones in proxima_tile for examples. For good performance, it's better for the image to be relatively large, not 1x1.

Quoteprocess more than 1 keypress per physics update.

Hmm. Do you really mean 1 per physics update, and not 1 per graphics frame, or 1 per program loop? Surely we can pause and select several skills during that (rather: between these same two) physics updates?

Quotehow often does this come up, and is it a major issue?

I habitually rewind (number 2 key in the number row) and scroll (right mouse button) at the same time, and it's niggling every time my input overlaps. It's never hugely annoying, but it's nagging a couple times every session. It's annoying enough that I'm willing to inspect the code with you. Every time I had tried to provoke it conciously, it had a 50 % chance to ignore input, and a higher chance to ignore on huge levels.

I'm busy this weekend, but we can find an evening in August/September. Focus on other bugs first. I'll play more CE when the contest levels release in September/October.

The better the software is, the more people will use it, and the more bugs they will file.

-- Simon