←2021-11 2021-12 2022-01→ ↑2021 ↑all
2021-12-01
00:00:31 <zzo38> Another idea is to name it by a recursive acronym like GNU and other projects has, but now we already have the name, anyways.
2021-12-02
06:19:02 -!- zzo38 has quit (Ping timeout: 240 seconds).
07:20:45 -!- zzo38 has joined.
2021-12-05
10:16:57 <zzo38> I had recently added a few features into the picture editor.
2021-12-06
04:22:55 <zzo38> Do you have ideas about the table of contents menu working? I thought to make it available SQL table with both standard and custom columns.
04:23:48 <zzo38> Standard columns would include at least the level ID number, level order number, whether or not a solution is available, and whether or not it is marked as the current user having solved it.
05:26:29 -!- zzo38 has quit (*.net *.split).
05:27:11 -!- zzo38 has joined.
05:37:33 -!- riv has quit (*.net *.split).
05:38:31 -!- riv has joined.
2021-12-09
21:21:11 -!- river has joined.
22:24:10 -!- infra_red[m] has joined.
22:46:55 -!- infra_red[m] has quit (Quit: Client limit exceeded: 20000).
2021-12-10
00:11:00 <zzo38> The feature added today is the (Control) block, which defines a global control object which is not in the playfield.
00:13:48 <zzo38> Such an object can never be created, destroyed, moved, or displayed on the screen, but can still receive broadcast messages, etc. This means that it is possible to have global keyboard functions or turn-based actions regardless of what other objects might or might not have.
00:15:11 <zzo38> I think I had found all of the places where these condition might be violated and where it already assumes X and Y coordinates are greater than zero, in order to avoid out of bound access or segfaults or other problems, but maybe I might have missed some.
2021-12-12
15:49:47 -!- zzo38 has quit (Ping timeout: 252 seconds).
19:32:51 -!- zzo38 has joined.
20:53:39 -!- zzo38 has quit (Remote host closed the connection).
20:53:59 -!- zzo38 has joined.
2021-12-13
02:47:23 <zzo38> Perhaps the format of the USERSTATE data for the .LVL lumps should be changed, to support other features in future. Currently, it consists of the move list, followed by three 16-bit numbers, being the mark position, level version number (minus one if you have not solved it), and the length of the move list.
02:49:17 <zzo38> One thing I want to include support for (in this and other files; there are many places where it would likely need adjusted) is multi-byte moves, which may be needed to support coordinate input (I cannot think of any other reason why multibyte moves may be needed, though).
02:50:14 <zzo38> So, the proposal is that each record has a one byte record type, two bytes giving the data length of the record, and then the data.
02:52:30 <zzo38> Also, the USERSTATE data for the LEVEL.IDX lump could store a bitmap of solved levels for quick access when displaying a list of solved/unsolved levels and when otherwise using that information in a SQL query.
2021-12-14
06:56:17 <zzo38> Now I have started the implementation of the LEVELS table. With the default key bindings, you can push ALT and the number pad - or + to skip to the previous or next unsolved level.
19:26:39 -!- zzo38 has quit (Ping timeout: 252 seconds).
19:38:26 -!- zzo38 has joined.
2021-12-16
00:00:04 -!- riv has quit (*.net *.split).
00:06:25 -!- riv has joined.
11:04:36 <river> good
2021-12-17
15:51:49 -!- river has quit (Ping timeout: 240 seconds).
2021-12-24
10:13:24 <zzo38> Recently I had been working on the level table implementation, and now have working (not committed yet) of some of the changes needed to customize the level table.
2021-12-26
00:03:47 -!- riv has quit (Ping timeout: 250 seconds).
2021-12-28
10:55:23 -!- TsVignesh[m] has joined.
10:56:00 <TsVignesh[m]> Hi Zzo38,
10:56:33 <TsVignesh[m]> I recently compiled free hero mesh on linux and tried to use MESH games in it
10:56:48 <TsVignesh[m]> so far I see only Hero Hearts is supported
10:57:14 <TsVignesh[m]> Though there are many more tiles using the same engine
10:57:19 <TsVignesh[m]> wondering what could be wrong
18:22:59 <zzo38> Did you aread the FAQ section at the bottom of the README file?
18:23:00 -!- infra_red[m] has joined.
18:23:20 <zzo38> Also, what error messages did you get, if any?
18:24:04 <zzo38> Most of the puzzle sets are working for me (once a few minor changes are made, as described in the FAQ)
18:26:07 <zzo38> TsVignesh[m]: These recent message are reply to your questions
2021-12-29
00:17:55 <zzo38> If something doesn't work, I would like to know what happened when you tried it, so that I can fix it and/or know what to tell to you, please.
06:41:06 <TsVignesh[m]> Sure, I'll provide error log when I run again
06:42:54 <zzo38> OK
07:09:34 <zzo38> (If you are willing to say, what time zone are you in? I am in UTC-8 time zone)
07:30:18 <TsVignesh[m]> I am from India (in IST time)
07:31:03 <TsVignesh[m]> and I usually play games after office hours late night before sleep
07:32:23 <zzo38> OK
07:43:15 <zzo38> Are you using files from the 32-bit version of the MESH engine? If so, I do not know the compatibility; the 32-bit version of the MESH engine does not run on my computer so I cannot test it. I also have not checked if the file format is compatible. If you (or anyone else) know about this, then I can add information into the documentation about this.
2021-12-31
23:17:29 -!- zzo38 has quit (*.net *.split).
23:36:30 -!- zzo38 has joined.
←2021-11 2021-12 2022-01→ ↑2021 ↑all