| Time |
Nick |
Message |
| 04:00 |
|
MTDiscord joined #minetest-dev |
| 05:14 |
|
fluxionary joined #minetest-dev |
| 05:42 |
|
TheCoffeMaker joined #minetest-dev |
| 07:43 |
|
basxto joined #minetest-dev |
| 14:36 |
|
SFENCE joined #minetest-dev |
| 15:30 |
|
SFENCE joined #minetest-dev |
| 15:40 |
|
Thomas-S joined #minetest-dev |
| 15:40 |
|
Thomas-S joined #minetest-dev |
| 15:47 |
|
imi joined #minetest-dev |
| 16:38 |
|
SFENCE joined #minetest-dev |
| 16:39 |
|
MTDiscord joined #minetest-dev |
| 17:09 |
|
fluxionary joined #minetest-dev |
| 17:14 |
|
SFENCE joined #minetest-dev |
| 17:39 |
|
SFENCE joined #minetest-dev |
| 17:43 |
MTDiscord |
<bastrabun> According to https://github.com/minetest/minetest/blob/master/doc/lua_api.md?plain=1#L293 there is a node naming convention, which is "enforced by the mod loader". Allowed are modname:[a-zA-Z0-9_]. |
| 17:43 |
MTDiscord |
<bastrabun> However minetest.register_node(":\n", {}) works and is placeable as a node. Is that a bug or is that intended? Here are more examples: https://gitea.your-land.de/your-land/bugtracker/issues/6947 |
| 17:45 |
MTDiscord |
<bastrabun> I did not yet dare to try minetest.register_node(":DROP TABLES students", {}) or minetest.register_node(":sudo rm -rf /", {}) |
| 17:46 |
|
grorp joined #minetest-dev |
| 17:48 |
grorp |
in #14542, I'm adding the new bool field "Simulated" to the "MouseInput" union member of "SEvent" |
| 17:48 |
ShadowBot |
https://github.com/minetest/minetest/issues/14542 -- [no squash] Auto-toggle TouchScreenGUI in-game when receiving touch/mouse input by grorp |
| 17:48 |
grorp |
now I obviously need that field to be false if the event isn't simulated |
| 17:49 |
grorp |
but to achieve that, I'd unfortunately have to add an `event.MouseInput.Simulated = false;` line everywhere a mouse event is created |
| 17:51 |
grorp |
I avoided this by adding a memset with 0 to the SEvent constructor, but there should be a better way. does someone have an idea? |
| 17:59 |
|
SFENCE joined #minetest-dev |
| 18:06 |
grorp |
well, I've switched to setting it manually now, but I'd still appreciate a better aproach |
| 18:22 |
|
SFENCE joined #minetest-dev |
| 18:24 |
|
grorp joined #minetest-dev |
| 18:27 |
|
grorp left #minetest-dev |
| 18:48 |
rubenwardy |
bastrabun: the `:` character disables item name conventions |
| 18:48 |
rubenwardy |
so it's behaving as intended |
| 18:58 |
|
SFENCE joined #minetest-dev |
| 18:59 |
sfan5 |
rubenwardy: |
| 18:59 |
sfan5 |
it should only disable the validation of the "modname:" part |
| 19:00 |
rubenwardy |
yeah I agree |
| 19:00 |
rubenwardy |
that would be more useful |
| 19:00 |
sfan5 |
a newline or spaces would definitely break the inventory serialization |
| 19:02 |
[MTMatrix] |
<Zughy> there is just one feature left: can we enter feature freeze and also get that feature merged in the meanwhile? https://github.com/minetest/minetest/milestone/23 |
| 19:04 |
sfan5 |
sure |
| 19:12 |
MTDiscord |
<luatic> fwiw gltf is code-wise ready |
| 19:13 |
MTDiscord |
<luatic> both static and animated, though the animated part hasn't been reviewed at all yet. both are tested and work as expected. |
| 19:17 |
|
SFENCE joined #minetest-dev |
| 19:18 |
[MTMatrix] |
<Zughy> I fear that such feature might delay the release even more |
| 19:19 |
MTDiscord |
<exe_virus> Agreed, just clean out 5.9 feature+ bugs already listed and move on to 5.10 |
| 19:20 |
[MTMatrix] |
<grorp> I'd support a feature freeze right now (with only the stuff that's already on the milestone being exempt) |
| 19:20 |
[MTMatrix] |
<grorp> I also have a feature PR I'd really like to get in (#14542), but you have to release at some point |
| 19:21 |
ShadowBot |
https://github.com/minetest/minetest/issues/14542 -- [no squash] Auto-toggle TouchScreenGUI in-game when receiving touch/mouse input by grorp |
| 19:22 |
[MTMatrix] |
<grorp> The time has come. |
| 19:22 |
MTDiscord |
<josiah_wi> I have no complaints against waiting for 5.10 for the gltf PR. That way we might be able to land both the static and animated parts in the same release. |
| 19:25 |
MTDiscord |
<luatic> okay suggestion |
| 19:25 |
MTDiscord |
<luatic> once we have gltf we just release 5.10 |
| 19:27 |
MTDiscord |
<luatic> (assuming the release procedure is feasibly short; i'll see whether this assumption holds when we release 5.9...) |
| 19:30 |
[MTMatrix] |
<Zughy> we could also try releasing every 4 months instead of 6 (which are never 6) |
| 19:30 |
MTDiscord |
<luatic> nvm disregard my suggestion, it wasn't well thought out. but perhaps we could try to target more frequent releases. |
| 19:30 |
[MTMatrix] |
<Zughy> 3 if we want to be super crazy |
| 19:30 |
MTDiscord |
<luatic> Zughy: yeah, i was thinking 3 months maybe even |
| 19:30 |
MTDiscord |
<luatic> damn Zughy is reading my brain today |
| 19:30 |
[MTMatrix] |
<grorp> luatic: so what is your opinion on a feature freeze right now? |
| 19:30 |
[MTMatrix] |
<Zughy> <3 |
| 19:31 |
MTDiscord |
<luatic> we can go ahead and freeze |
| 19:31 |
MTDiscord |
<luatic> we've got many regressions to tackle |
| 19:31 |
MTDiscord |
<luatic> luckily we also have PRs for most of them |
| 19:32 |
MTDiscord |
<luatic> @rubenwardy looking at the release checklist, do we still have a twitter / X account and if so, do we still want to post there? lol |
| 19:32 |
rubenwardy |
it's just mastodon now |
| 20:00 |
MTDiscord |
<exe_virus> Gosh we have a long release process lol. That seems like it could be a bit more automated, but not much more |
| 20:00 |
MTDiscord |
<exe_virus> Also: I thought we couldn't use mingw anymore because it's buggy or something? Or was it just the mingw-gcc was the issue and we instead use clang as the front end? |
| 20:08 |
sfan5 |
indeed |
| 22:32 |
|
panwolfram joined #minetest-dev |
| 23:08 |
|
vampirefrog joined #minetest-dev |
