I have noticed some strange and unusual behavior in SLXEditor_2.9.2 (and also 2.8.9b) when loading (either directly or via NeoLemmix CE 1.0.1) the gaps_V2.nxvl level (or gaps.nxlv for that matter) from saba.

With the saba level loaded in the aforementioned editor, if you select, for example, terrain pieces located at 102/191, -5/93, or 324/260 and apply the various ROTATE, INVERT, or FLIP functions to them, we observe that the behavior of these pieces when the chosen function is applied is not at all what is expected and that, in addition, the normal fluidity of general movement of pieces in the editor is significantly reduced.

However, this bug (functions and fluidity) does not exist if you load the gaps_V2.nxlv level in SLXEditor_2.8.8!

Problem with SLXEditor 2.9.2? With this specific level? A combination of both?

NeoLemmix CE 1.0.1
The following is based on three game files with a Time Limit of 2 seconds, available as attachments
test_1.94_.nxlv
test_2.00_.nxlv
test_2.06_.nxlv   
     
If a Time Limit is assigned to a level, and the assigned value is exceeded, an alert lasting approximately 2 seconds is heard, similar to the sound of an alarm clock.

Except that...

If we run test_1.94_.nxlv: no alarm clock sound and the message "Superb! You rescued every Lemming..."  "Your time taken is 0.01. 94" is displayed.
It makes sense.

If we run test_2.06_.nxlv: alarm clock sound for about 2 seconds and no display "
It makes sense.

If we run test_2.00_.nxlv:
The result is: "Superb! You rescued every Lemming..."  "Your time taken is 0.02. 00"
and we hear the alarm clock sound for about 2 seconds, indicating that the Time Limit has been exceeded, which contradicts the result displayed.
It doesn't make sense; we should not hear the alarm clock sound in this specific case.

Can this be fixed?

OK! Thanks to all for your informations, comments and clarifications.
For me, this was more of a need-to-know question than a disturbing problem.

I've created - as a training exercise - a small elementary level which resolves perfectly in exactly 9.00 s (0:09. 00), with a Spawn Rate locked at 99, a Time Limit legitimately set at 9 s and 6 lemmings out of 6 saved successfully.

When I validate this level created in SLXEditor 2.8.8 (File/Validate Level), I get the following message: "Not enough time: Only 9seconds available".
If I set the Time Limit to 10 s, when I validate this level, I get the following message: "No issues found".

There seems to be a minimum duration (10 s) for the Time Limit below which you can't go without getting the error message indicated, although the level has been successfully solved.

Is this by design? If so, why? Or is it a bug?

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à!

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

Hi Will,
Steps to reproduce:

Launch SLXEditor 2.8.8
Tools
tick 'Snap to Grid'
(tick 'Snap to Grid' <=> 'Snap-to-Grid amount in pixels' ticked)
Settings
Snap Pieces to Grid
GridSize  '1'
Choose grid color 'Blue'  (Blue for example, any color except invisible)
Save And Close
File/Exit

When exiting and relaunching SLXEditor, 'Snap to Grid' in unticked and GridSize returns to its default value of '8' (note that this does not happen if GridSize is different from '1', any GridSize value other than '1' is maintained as well as the grid color and 'Snap to Grid' is always ticked).

This can be annoying if you're working with a full background (blue, for example) because you have to redefine GridSize each time you work.

When activating 'Snap to Grid' AND 'Snap-to-Grid amount in pixels' with GridSize '1', is there a solution so that when SLXEditor is exited, the Gridsize '1' setting with 'Snap to Grid' ticked are maintained when SLXEditor is restarted?

QuoteIncreased the maximum zoom level from 7 to 10 in commit 7c4e1ec

I've increased the size of the font to 12pt

OK Thanks Will

In SLXEditor 2.8.8, the X/Y coordinates of a selected piece are displayed in the bottom right-hand frame in white on a grey background, which is not very visible. Is it possible to make these X/Y coordinates more visible?
In addition, when you zoom in to the maximum on a selected piece, X/Y almost completely disappears and becomes very difficult to read. Can X/Y be placed elsewhere so that its visibility is not affected when zoomed in? I can see that this is not the case in Level Arranger Window: X/Y is stable and fully visible in the bottom right-hand frame, whatever the zoom level.

Unless I'm mistaken, I've noticed - for example for the same selected piece - that the maximum possible zoom level is lower in SLXEditor 2.8.8 than in Neolemmix CE 1.0.1.
Would it be possible to increase the maximum zoom value in SLXEditor as this may make it easier to work at the pixel level?

Quote from: WillLem on January 29, 2025, 11:17:32 AMOK, try the same method again but in step 5 choose to scale by System or System (Enhanced).

By changing the screen resolution on my 17.3" laptop to 1920x1080 and the scaling factor to 140%, everything is now OK for SLXQuickMod's display.
I was previously at 1366x768 and 100%.
Thank you for the information and for solving the problem

Quote from: WillLem on January 28, 2025, 09:30:43 PMAh, I see the problem now.

thanks Will for the feedback
the indicated method doesn't work
the problem is still present
(laptop running Win10 Home (22H2) and NVIDIA GeForce GTX 1060)

Yes Will Yes but...

Hi Will,
What is this?

Hi Will,

My comment concerns SLXEditor_2.8.3 in a NeoLemmix or SuperLemmix environment

The Hotkey Configuration window (<F11>) has a defect (the bottom of the window is cut off along its entire length) in certain screen resolutions on my laptop as shown in the image.



To give just a few examples:
In 1920x1080, 1600x1024, 1440x810 resolutions, the window is normal
In  1366x768 1024x768, 1280x720 resolutions, the bottom of the window is cut off

Is this linked to my laptop (NVIDIA GeForce GTX 1060) or to SLXEditor 2.8.3?