Issue #262 on github

mobius discovered that (for an older Lix version) on Win when in fullscreen Lix remains on the screen (like a background screen image) when tabbing out and you cannot get to other windows.

My observations concerning v. 0.9.7 (I really hope they are accurate since it really behaves odd and particular):
- Hardware fullscreen seems to behave as expected, i.e. doesn't have this issue, i.e. lets you switch to other windows and minimizes.
- Software fullscreen:
a) If you press Win key you get the task bar but cannot switch to other tabs by clicking on them and Lix remains on the screen in the background. You can though open program windows with the popping up Start menu but only in its activation via Win key but not if you click on the Start menu button (Win 7). If you opened such another window you can actually switch by clicking on tabs until you focus Lix again.
b) If you press Alt+Tab you can get to other open windows and can change to other windows but Lix remains on the screen in the background unless you explicitly choose desktop and clicking on any other window then seems to bring Lix in the background again.

I had a crash while playing with the main message:

core.exception.AssertError@src\lix\skill\basher.d(101): Assertion failure

I have used my own (debug) build (of 0.9.6), so maybe I messed something up with it. I moved furthermore the folder to another place after the build but the error message still shows the path of the build place.

Edit: Debug build seems to crash consistently, release build from the same data doesn't. Debug build crashes consistently when basher finishes tunnel. That didn't happen with the test builds you provided. Did you do something with the basher code in the meantime? Or do I do something utterly wrong? At least release build doesn't crash.

Following the full message from log.txt:
(I have censored parts of the file paths but the important bits should be still there):

Lix version:  0.9.6
Session date: 2017-12-28 01:48:14
  1028.02 src\lix\skill\basher.d:101:
  1028.07 Assertion failure
  1028.28 0x005334DF in _d_assertp
0x00509085 in void lix.skill.basher.Basher.stopIfMovedDownTooFar() at C:\...\LixD-master0_9_6\LixD-master\src\lix\skill\basher.d(100)
0x00508D72 in void lix.skill.basher.Basher.perform() at C:\...\LixD-master0_9_6\LixD-master\src\lix\skill\basher.d(38)
0x00507E4B in void lix.perform.performUseGadgets(lix.lixxie.LixxieImpl*) at C:\...\LixD-master0_9_6\LixD-master\src\lix\perform.d(19)
0x0050796A in void lix.lixxie.LixxieImpl.perform(lix.fields.OutsideWorld*)
0x004CBB8E in D4game5modelQg9GameModel13updateLixxiesMFZ15performUnmarkedMFE3net2ac9PhyuOrderZ9__lambda2MFCQDF961ACA6FFECAD39D41547C51BB029FD at C:\...\LixD-master0_9_6\LixD-master\src\game\model\model.d(254)
0x004CB892 in void game.model.model.GameModel.updateLixxies().foreachLix(void delegate(game.tribe.Tribe, const(int), lix.lixxie.LixxieImpl*)) at C:\...\LixD-master0_9_6\LixD-master\src\game\model\model.d(216)
0x004CBB03 in void game.model.model.GameModel.updateLixxies().performUnmarked(net.ac.PhyuOrder) at C:\...\LixD-master0_9_6\LixD-master\src\game\model\model.d(250)
0x004CB7C3 in void game.model.model.GameModel.updateLixxies() at C:\...\LixD-master0_9_6\LixD-master\src\game\model\model.d(265)
0x004CB040 in void game.model.model.GameModel.advance() at C:\...\LixD-master0_9_6\LixD-master\src\game\model\model.d(94)
0x004CCD03 in void game.model.nurse.Nurse.updateOnce() at C:\...\LixD-master0_9_6\LixD-master\src\game\model\nurse.d(221)
0x004CC5E0 in void game.model.nurse.Nurse.updateTo(const(net.phyu.Phyu), const(game.model.cache.DuringTurbo)) at C:\...\LixD-master0_9_6\LixD-master\src\game\model\nurse.d(138)
0x004C4A55 in void game.core.speed.updatePhysicsAccordingToSpeedButtons(game.core.game.Game).upd(const(int), const(game.model.cache.DuringTurbo)) at C:\...\LixD-master0_9_6\LixD-master\src\game\core\speed.d(27)
0x004C49AF in void game.core.speed.updatePhysicsAccordingToSpeedButtons(game.core.game.Game) at C:\...\LixD-master0_9_6\LixD-master\src\game\core\speed.d(72)
0x004C1199 in void game.core.calc.implGameCalc(game.core.game.Game).noninputCalc() at C:\...\LixD-master0_9_6\LixD-master\src\game\core\calc.d(27)
0x004C10D8 in void game.core.calc.implGameCalc(game.core.game.Game) at C:\...\LixD-master0_9_6\LixD-master\src\game\core\calc.d(39)
0x004C3415 in void game.core.game.Game.calc() at C:\...\LixD-master0_9_6\LixD-master\src\game\core\game.d(195)
0x0042B383 in void basics.mainloop.MainLoop.calc() at C:\...\LixD-master0_9_6\LixD-master\src\basics\mainloop.d(265)
0x0042AC4F in void basics.mainloop.MainLoop.mainLoop() at C:\...\LixD-master0_9_6\LixD-master\src\basics\mainloop.d(103)
0x0050DD04 in int main.main(immutable(char)[][]).__lambda2() at C:\...\LixD-master0_9_6\LixD-master\src\main.d(39)
0x0053194F in extern (C) int allegro5.system.al_run_allegro(scope int delegate()).main_runner(int, char**) at C:\...\LixD-master\..\..\AppData\Roaming\dub\packages\allegro-4.0.1_5.2.0\allegro\allegro5\system.d(45)
0x00531933 in int allegro5.system.al_run_allegro(scope int delegate()) at C:\...\LixD-master\..\..\AppData\Roaming\dub\packages\allegro-4.0.1_5.2.0\allegro\allegro5\system.d(62)
0x0050DCB7 in _Dmain at C:\...\LixD-master0_9_6\LixD-master\src\main.d(35)
0x0053EDFB in void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).runAll().__lambda1()
0x0053EDBF in void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).runAll()
0x0053ECC0 in _d_run_main
0x0050DD30 in main at C:\...\LixD-master0_9_6\LixD-master\src\verify\counter.d(7)
0x0057D8F9 in mainCRTStartup
0x76AB337A in BaseThreadInitThunk
0x77519882 in RtlInitializeExceptionChain
0x77519855 in RtlInitializeExceptionChain

Draw splat ruler even when it doesn't snap to anything.

Does this really improve useability? But if the others get better along with that I have to take it I guess.

Probably everybody knows this already or maybe there is even something implemented but I just wanted to share how I integrated the large bridge tiles (in fact made of 4 Simon bridge tiles) into the existing Clam levels as I converted the oriental ones.

1st Create a level file with the desired tile groups

This one is maybe obvious but you can build tile groups (connect them as tile groups) in the ingame editor and save. This creates a level file with the tile group data. The level will show missing hatches but you can edit it and so work with the tile groups (copying, deleting etc. them as you need). You so create a template that you could use if you want to build new levels with these tile groups.

2nd Copy the tile group data of the desired tile groups in the desired level file

But I wanted to integrate them in existing files.
So you can open your template level file with the tile group data and copy that data + (at least) one instance of that group in the desired existing file.

The structure of the tile group data is like that (example: one of the big bridge tiles):

$BEGIN_TILE_GROUP 0
:simon/oriental/bridge1: 0 22
:simon/oriental/bridge1: 44 0
:simon/oriental/bridge1: 0 65 rr
:simon/oriental/bridge1: 44 43 rr
$END_TILE_GROUP

You have a bracket of $BEGIN_TILE_GROUP 0 and $END_TILE_GROUP and inbetween the tile data of which the tile group is composed. (0 indicates which tile group it is.)
You have to integrate that and then one instance, which for example looks like that:

:Group-0: 112 132 rr

Group-0 is the name of the tile group, so if you want to integrate more than one tile group you have to look for the number. (The colon at the beginning seems to be some sort of separator, the numbers are the coordinates and rr seems to indicate that I turned it twice.)
And you need to give different numbers to different tile groups in the tile group data.

I have attached a template level of the big bridge tiles:
tile group 0 is the angled bridge tile group that is built roughly on the shape of the old tiles.
tile group 1 is the straight bridge tile group (built roughly on the shape of the old tiles).
tile group 2 is the angled bridge tile group that is built to fit to the straight ones.

You can look at this file to get an impression how it looks like with more than one tile group.

I have attached a pointless test level as well, where I integrated one of the big bridge tiles, which is another reference how to exactly integrate such tile groups.
The easiest way seems to be to just integrate it after the skill enumeration. (Make sure that everything concerning tile group data is in different lines.) (It will be probably reordered after you have saved in the ingame editor but that shouldn't be a problem.)

If you have integrated them you can copy, delete etc. them in the ingame editor as you wish and so work with them.

Just a side note in the end: Since I converted the levels I mainly text edited and used find and replace (all) to replace the old tiles with the new tile groups (and didn't need to integrate an (extra) instance of the tile groups). But I got as I side information how to integrate such tile groups, which could in turn be used for level building. 

I hope that explanation was not redundant and not too confusing.

I ask only out of curiosity; I'm no programmer and have no knowledge of D as language, so sorry if this question is out of place.

Issue #263 has as main error message:
core.exception.AssertError@src/game/tribe.d(210): Assertion failure

and issue #269 has:
core.exception.AssertError@src/game/tribe.d(211): Assertion failure

The numbers are different and one is reported to have happened at the beginning and the other at the end of a multiplayer game but there seem quite some similiarities apart from that both happened to geoo.

One side remark: It seems that Lix error windows appear in the background (at least for Windows XP, 7). That seems to make them (or even a crash) hard to spot. I don't know if there is something to do about it.

Sorry for bringing up another thing but that just occured to me:

I solved Rubix Sinister level "Holly Jingle?" (v.0.9.3) and the replay was automatically saved in solved/rubix/Sinister.
When I mass verify it then it shows fail whereas when I look at it it succeeds.

I've attached the replay.

verifier.txt shows only 5300 Phyus but it lasted 5457 Phyus.

(FAIL),replays/solved/rubix/Sinister/hollyjingle-Forestidia-2017-11-26-031453.txt,levels/single/rubix/Sinister/hollyjingle.txt,Forestidia,97,99,5,5300

Some things that occured to me when adjusting the Clam levels:

First of all I'm not experienced with the editor so if the feature is already there then understand my remarks as questions if they are there and how to apply them.

Is there something like an undo button? I always lost my non-saved progress if I made a missclick and moved the wrong tile (group). Since I was dealing with an existing level I couldn't guarantee to move it back to the original position.

Is there a possibility to show grid lines? That would have been helpful to see where exactly everything is situated.

Is there something like a blank space to manage tiles? I had an existing level before me and if that was quite full or had giant tile clusters then it was hard to manage new tiles. Managing means for example: put them together to tile groups, copying them etc.

I know I speak from a very particular viewpoint and that makes these things maybe not so important but I just wanted to bring that up since it occured to me.