| Time |
Nick |
Message |
| 03:00 |
|
saschaheylik joined #minetest-dev |
| 05:37 |
|
GTRsdk joined #minetest-dev |
| 05:54 |
|
saschaheylik_ joined #minetest-dev |
| 06:08 |
|
workflow joined #minetest-dev |
| 06:42 |
|
saschaheylik joined #minetest-dev |
| 08:25 |
|
Calinou joined #minetest-dev |
| 11:39 |
|
Calinou joined #minetest-dev |
| 12:45 |
|
jordach joined #minetest-dev |
| 13:29 |
darkrose |
celeron55: nodetimers implemented: https://github.com/darkrose/minetest/commit/e4f316e3f2a9b1bfd3d6b03c87c52dadb2113aa4 |
| 13:39 |
celeron55 |
oh dog |
| 13:39 |
celeron55 |
do they work now? |
| 13:40 |
darkrose |
did when I tested, just noticed there is actually a spec for them which isn't the same as what I implemented them as though |
| 13:41 |
celeron55 |
if you make a node timer of 1 minute, stop the game after 30 seconds of placing such a node on in the world and start the game again, does it trigger after 30 seconds? |
| 13:41 |
celeron55 |
that is the point of node timers |
| 13:42 |
celeron55 |
or, well, one of the few points |
| 13:46 |
celeron55 |
the second point is the higher resolution |
| 13:46 |
celeron55 |
and the third point is that they are per-node |
| 13:47 |
darkrose |
yeah the higher resolution works, tested one at 0.2 seconds.... just checkif they work right between shutdowns |
| 13:47 |
darkrose |
... which they do |
| 13:47 |
darkrose |
and they are per-node |
| 14:17 |
|
Calinou joined #minetest-dev |
| 16:50 |
darkrose |
somewhat cleaner nodetimer API: https://github.com/darkrose/minetest/commit/8e6eb3d7e3f410fe0e9e7c8a431845205ae8303f |
| 16:53 |
celeron55 |
should "duration" be called "interval" |
| 16:53 |
MiJyn |
depends @c55 |
| 16:53 |
MiJyn |
interval means time in-between both |
| 16:53 |
darkrose |
interval make it sound like it will callback more than once |
| 16:54 |
MiJyn |
duration means the time it takes |
| 16:55 |
celeron55 |
hmm, true |
| 16:55 |
celeron55 |
altough |
| 16:55 |
darkrose |
could be delay or timeout, maybe |
| 16:55 |
celeron55 |
duration sounds like something that is on for the... duration of something |
| 16:55 |
MiJyn |
yes |
| 16:55 |
celeron55 |
as a random example, QTimer in Qt calls that timeout |
| 16:56 |
celeron55 |
let's see what other libraries call it |
| 16:57 |
celeron55 |
in wxWidgets, it is called interval, and there is an additional "oneShot" flag |
| 16:58 |
darkrose |
javascript calls it timeout, interval is for 'trigger every interval seconds' ongoing timers |
| 17:01 |
celeron55 |
in glib, it is called timeout, in the parameter of g_timeout_add(), and if the callback returns false, it is removed, otherwise it recurs |
| 17:03 |
celeron55 |
how on earth can anyone decide what way to use? 8) it's really just up to consistency of the API... and there isn't any occurrece of this kind of thing in it i guess |
| 17:04 |
celeron55 |
i'd say do it like glib does |
| 17:05 |
darkrose |
that's what I was thinking, would make for cleaner lua code for recurring timers too |
| 17:06 |
darkrose |
default to call once like glib does? only stop the cycle if on_timer returns false? |
| 17:07 |
celeron55 |
a true boolean value of the return value continues it, so it stops if nil is returned |
| 17:07 |
darkrose |
ok |
| 17:09 |
celeron55 |
07:46:37 <VanessaE> My Unified Dyes mod is starting to gain a following; remember the limit on the number of defined nodes/items? It's becoming a problem now. May I suggest going for overkill and just expanding the related field you talked about by an additional byte instead of just those unused bits? |
| 17:10 |
celeron55 |
if you have extra time, you could look into that now that you've messed with the map serialization |
| 17:10 |
celeron55 |
that is, 16-bit content ids - there is a half-commented out, half-not-done implementation of them in there |
| 17:12 |
celeron55 |
i really don't want to start anything new to cope with dyes or stuff like that, better just extend existing stuff and hope it can cope up with itself |
| 17:12 |
|
jordach joined #minetest-dev |
| 17:12 |
darkrose |
ok, I'll have a look at it |
| 17:13 |
celeron55 |
it means making param0 16 bits, and removing the usage of the top 4 bits of param2 for the part of the content id |
| 17:14 |
celeron55 |
...with backwards compatibility |
| 17:14 |
celeron55 |
for data on disk |
| 17:14 |
jordach |
hmm |
| 17:22 |
Calinou |
hi jordach |
| 17:22 |
jordach |
celeron55, what would be the simplest way to add nodes in 0.2? |
| 17:22 |
Calinou |
modify_the_source_code |
| 17:22 |
jordach |
we have |
| 17:23 |
celeron55 |
0.2? |
| 17:23 |
jordach |
before 0.3-dev |
| 17:23 |
celeron55 |
gimme git hash |
| 17:23 |
celeron55 |
or tag |
| 17:24 |
Calinou |
celeron55, why did you create a new channel btw? two were enough |
| 17:24 |
jordach |
20110922_3 |
| 17:24 |
|
Calinou was kicked by celeron55: for this |
| 17:24 |
|
Calinou joined #minetest-dev |
| 17:24 |
Calinou |
\o/ a kick |
| 17:24 |
|
Calinou was kicked by celeron55: Calinou |
| 17:25 |
celeron55 |
[celeron55 nk minetest]$ git checkout 20110922_3 |
| 17:25 |
celeron55 |
error: pathspec '20110922_3' did not match any file(s) known to git. |
| 17:26 |
celeron55 |
oh, i guess those aren't even in git even if they had tags |
| 17:26 |
celeron55 |
because they had tags only in the mercurial repo 8) |
| 17:26 |
jordach |
my bad: 0.2.20110922_3 |
| 17:27 |
jordach |
or : https://github.com/celeron55/minetest/tree/stable-0.2.20110922 |
| 17:28 |
celeron55 |
0.2.20110922_1 is in git, _2 and _3 are just repackagings of the same thing |
| 17:28 |
jordach |
oh |
| 17:28 |
jordach |
i have took the latest, and started my work on adding commonly found nodes in 0.4 |
| 17:30 |
celeron55 |
oh, _2 exists too in the branch |
| 17:30 |
celeron55 |
i was searching in master 8) |
| 17:30 |
celeron55 |
well anyway |
| 17:30 |
celeron55 |
you want to add new IDs to content_mapnode.h and then add them to content_mapnode_init() in content_mapnode.cpp |
| 17:30 |
celeron55 |
and that is it |
| 17:31 |
celeron55 |
you could remove the conversion table because nobody has that old maps anymore anyway |
| 17:31 |
jordach |
ah, thanks, quick pick of your brains, texturing? |
| 17:31 |
celeron55 |
? |
| 17:31 |
jordach |
adding a texture to mapnodes |
| 17:31 |
jordach |
ill probably find this out myself |
| 17:32 |
celeron55 |
...if you had just glanced at the files, you wouldn't have asked that |
| 17:32 |
jordach |
silly me |
| 17:33 |
MiJyn |
jordach, you talking about tile.cpp? |
| 17:33 |
jordach |
there we go |
| 17:34 |
jordach |
over the school holidays, im expected to practice c++ - good way to start: minetest src, thanks for the help celeron |
| 17:34 |
jordach |
and im leaving it there |
| 17:37 |
jordach |
is 0x820 legal? |
| 17:37 |
MiJyn |
I don't think so |
| 17:37 |
MiJyn |
unless you are talking about UTF16 |
| 17:38 |
jordach |
more like the node defs in content_mapnode.h |
| 17:38 |
MiJyn |
like 0x820 as in the character? |
| 17:38 |
jordach |
yes |
| 17:39 |
MiJyn |
well, UTF-8-wise, no |
| 17:39 |
MiJyn |
because 8 bits can only go up to 256 |
| 17:39 |
jordach |
like hexidecimal, or octidecimal |
| 17:39 |
MiJyn |
and 820 > 256 (fyi) |
| 17:39 |
MiJyn |
I'm not sure |
| 17:39 |
jordach |
well: 0x814 //29 |
| 17:40 |
jordach |
and 16 nodes shant hurt, right? |
| 17:41 |
darkrose |
celeron55: nodetimers, duration -> timeout, and restart when return true: https://github.com/darkrose/minetest/commit/426c8187a85ae2de0114e1054ac103536bac7608 |
| 17:43 |
MiJyn |
darkrose, just wondering, is your username hooked up to a CIA bot? |
| 17:43 |
MiJyn |
or are you just typing out commits that interest you? |
| 17:44 |
darkrose |
entering them, as I commit them |
| 17:44 |
MiJyn |
ah cool! |
| 17:44 |
MiJyn |
manually? |
| 17:44 |
darkrose |
yes, now stfu :p |
| 17:44 |
MiJyn |
ah ok |
| 17:44 |
MiJyn |
I was just wondering |
| 17:45 |
celeron55 |
wtf? |
| 17:45 |
MiJyn |
wha? |
| 17:46 |
celeron55 |
i don't understand anything you said |
| 17:46 |
MiJyn |
oh |
| 17:46 |
celeron55 |
i am guessing it was some very stupid joke |
| 17:46 |
MiJyn |
no |
| 17:46 |
MiJyn |
I was seriously wondering |
| 17:46 |
celeron55 |
i am left to wonder what is this thing you wonder |
| 17:47 |
MiJyn |
just because he kept on giving them in a sot of an almost automatic manner |
| 17:47 |
MiJyn |
the commits |
| 17:47 |
MiJyn |
you know what a CIA bot is, right? |
| 17:47 |
celeron55 |
no i don't |
| 17:47 |
MiJyn |
oh |
| 17:48 |
MiJyn |
http://cia.vc/ |
| 17:48 |
MiJyn |
CIA can send an IRC bot to your channel to instantly report the progress made by you and your peers: |
| 17:48 |
MiJyn |
so it more or less shows each commit that is made |
| 17:58 |
|
VanessaE joined #minetest-dev |
| 18:02 |
jordach |
celeron55, are we using base64 for node space addressing? |
| 18:17 |
celeron55 |
wat? |
| 18:17 |
jordach |
base64.cpp has a usage? |
| 18:17 |
celeron55 |
... |
| 18:17 |
celeron55 |
use grep |
| 18:17 |
jordach |
point |
| 18:17 |
celeron55 |
i'll kick you of the next stupid question |
| 18:18 |
jordach |
alright] |
| 18:18 |
celeron55 |
this channel is intended to be such that i don't feel like grep |
| 18:18 |
jordach |
ok |
| 18:18 |
celeron55 |
grep has no other business than grepping code |
| 18:18 |
celeron55 |
i have |
| 18:18 |
celeron55 |
if you want to ask random stupid questions, a) don't ask them from me, b) dont ask them here |
| 18:19 |
celeron55 |
as long as you could not have found an answer with grep or google, i will happily answer |
| 18:19 |
jordach |
ok, thanks |
| 18:45 |
|
cisoun joined #minetest-dev |
| 18:46 |
jordach |
celeron55, is it even possible to attempt endless maps? |
| 18:47 |
celeron55 |
probably not |
| 18:47 |
jordach |
i grepped for the coordinates |
| 18:47 |
jordach |
and MAP_GENERATION_LIMIT |
| 18:47 |
celeron55 |
you'll have huge problems with rendering |
| 18:48 |
celeron55 |
because of single-precision floating point |
| 18:48 |
jordach |
ah |
| 18:48 |
jordach |
now, thinking about it, i could probably get to 65535 blocks then a exception |
| 19:06 |
VanessaE |
not a stupid question: is it possible to use patterns in the recipe section of a register_craft call? |
| 19:13 |
MiJyn |
I don't think so |
| 19:13 |
MiJyn |
but could you elaborate what you mean on "patterns"? |
| 19:14 |
MiJyn |
like *wood*? |
| 19:14 |
MiJyn |
or (.*?) |
| 19:14 |
MiJyn |
? |
| 19:14 |
celeron55 |
lol, a regexp replace could make interesting results 8) |
| 19:14 |
MiJyn |
xD |
| 19:14 |
celeron55 |
but no |
| 19:14 |
MiJyn |
yeah |
| 19:14 |
MiJyn |
(.*?)\1 |
| 19:14 |
celeron55 |
the mechanism at hand is supplying groups to it |
| 19:14 |
MiJyn |
:P |
| 19:15 |
MiJyn |
what do you mean? |
| 19:15 |
MiJyn |
like *mymod*:mynode (section surrounded by *) |
| 19:15 |
MiJyn |
? |
| 19:16 |
VanessaE |
oh sorry, got sidetracked. |
| 19:16 |
VanessaE |
no, more like: |
| 19:16 |
VanessaE |
recipe { |
| 19:17 |
MiJyn |
vanessae, uh...? |
| 19:17 |
VanessaE |
{ "mymod:material_*", "mymod:material_*", } |
| 19:17 |
VanessaE |
...etc |
| 19:17 |
celeron55 |
you set a group in those nodes and then use "group:thatgroup" |
| 19:17 |
VanessaE |
ahhhhh |
| 19:17 |
VanessaE |
I'll do that then |
| 19:18 |
MiJyn |
c55, wait, you implemented a new group API? |
| 19:18 |
celeron55 |
https://github.com/celeron55/minetest/blob/master/doc/lua_api.txt#L424 |
| 19:19 |
darkrose |
celeron55: this should fix VanessaE's problem, just waiting for her to test it: https://github.com/darkrose/minetest/commit/1860a9ef211f046f49829fb54fa435e35dac566f |
| 19:19 |
VanessaE |
darkrose: I'm getting to it, slowly :-) |
| 19:19 |
MiJyn |
c55, oh, I thought it was planned, but not implemented. Sorry! |
| 19:20 |
celeron55 |
it was planned at some point, and at some point it was implemented |
| 19:20 |
VanessaE |
celeron55: OH, I get it now. I never understood that section before. |
| 19:20 |
MiJyn |
celeron55, ah |
| 19:20 |
VanessaE |
thanks for the tip :-) |
| 19:20 |
VanessaE |
bbiab |
| 19:21 |
MiJyn |
whats bbiab? |
| 19:21 |
celeron55 |
https://www.google.com/search?q=bbiab |
| 19:22 |
MiJyn |
OH |
| 19:29 |
celeron55 |
darkrose: you didn't take into account that param2 can have a full byte worth of information if param0<=0x7f |
| 19:29 |
celeron55 |
in the old format |
| 19:30 |
celeron55 |
the thing is a minefield of potential bugs |
| 19:31 |
celeron55 |
you'll likely cause an another one while fixing that 8) |
| 19:31 |
celeron55 |
+to |
| 19:31 |
darkrose |
awesome :) |
| 19:31 |
celeron55 |
-to |
| 19:32 |
celeron55 |
this is awesome 8) http://c.learncodethehardway.org/ http://c.learncodethehardway.org/book/ |
| 19:42 |
darkrose |
why the hell would I read that? |
| 19:43 |
celeron55 |
maybe not you, but someone |
| 19:43 |
celeron55 |
i did read some of the start and some hand-picked later parts |
| 19:44 |
celeron55 |
always refreshing to read someone's rationales for doing things in a certain way in C |
| 19:51 |
celeron55 |
(anyway, everybody of course feel free to not even glance at it, excuse the spam) |
| 19:51 |
darkrose |
had a look at it a while ago when I was teaching someone C |
| 19:52 |
celeron55 |
i am always interested in how people go at teaching a programming language |
| 19:53 |
VanessaE |
"the hard way". oh boy. |
| 19:54 |
celeron55 |
"with the right attitude and not for babies" = the only way it should be done |
| 19:54 |
celeron55 |
the author has made this 8) http://programming-motherfucker.com/ |
| 19:56 |
VanessaE |
I afraid to click.... ;) |
| 19:56 |
VanessaE |
I think I've seen this before |
| 20:05 |
|
celeron55 joined #minetest-dev |
| 20:08 |
darkrose |
bah! I'll look at it after some sleep |
| 22:59 |
|
VanessaE joined #minetest-dev |
| 23:34 |
VanessaE |
darkrose: sorry I disappeared - internet tech had to work on our line. did you mean you'll re-read the changes you had me try? |
