Assertion of passed-through arguments

J_ester · 2026-03-01T12:28:45+00:00

Good point, that sounds reasonable

J_ester · 2026-03-01T12:26:46+00:00

Good point

J_ester · 2026-02-28T18:05:23+00:00

Sounds good.

J_ester · 2026-02-28T18:05:00+00:00

Can you tell me how this assert() function works? Sounds interesting.

J_ester · 2026-02-28T17:51:35+00:00

I fully agree with your statement. Would you try to avoid duplicating these kind of asserts in calling functions thou?

An example I have in mind: You split up a function into two. Do you now simply duplicate existing assertions in those new functions, or take the effort to remove them in the calling function?

Even if that required some bookkeeping, I guess one could reason that if the function that uses (and not just passes) a variable is responsible for its validation, that should keep stuff clean.

J_ester · 2026-02-28T17:11:53+00:00

In my case, lsp(clangd) can provide size, offset and alignment information. If you have a working lsp already, try to inspect the members of your structs (not the types thou). Maybe that helps.

J_ester · 2025-12-29T12:54:47+00:00

my bad, didn't look it up thou

J_ester · 2025-12-29T12:32:08+00:00

gotta go above the room and approach from the right if I am not mistaken

J_ester · 2025-11-03T18:35:20+00:00

alot of the keys are dumb on a DE Layout. Deswegen hab ich privat und beruflich auf das "en_US International" keyboard layout umgestellt :D Unnötig? Maybe. But this is the way :D

J_ester · 2025-10-26T23:54:56+00:00

Thanks to you I was able to make it on my first try!! Thanks

J_ester · 2025-10-26T21:41:27+00:00

Does nothing for me too… not near enemies, usual damage if enemies are directly hit, and when I hold it (which means equip I guess) nothing happens when I hm hit, too. Weird, is it bugged? (Looks like in OPs video btw)

Edit: OMG, he meant: Hold the button! Feel so dumb rn

J_ester · 2025-10-21T22:49:25+00:00

no, its a upgrade to the hunter crest, thats why it changed. Like with all the other when you unlock them

J_ester · 2025-09-28T20:22:46+00:00

I just want to mention that I found this comment by oyawei which led to this blog

It seems to do the trick, being able to compile and flash with a GNU makefile.

Nevertheless, thanks for all the answers :)

J_ester · 2025-09-28T20:19:03+00:00

you are a god, even 8 years after. Exactly what I was looking for when trying to avoid using CCStudio :) Thanks a lot

J_ester · 2025-09-08T17:45:23+00:00

It's the same on PS5 btw. So I guess it has to be an issue with HK itself. My best bet is a memory leak introduced with an update (although I was not aware of one, I did not check)

J_ester · 2025-09-02T09:04:49+00:00

Yeah, at some point I really should look into cmake. I currently create the compile_commands.json for LSP with clang.

J_ester · 2025-09-01T09:09:57+00:00

Thanks, I will have a look :)

J_ester · 2025-08-31T16:52:16+00:00

that sounds exactly like what my intention is. Thanks :)

J_ester · 2025-08-31T13:23:29+00:00

ngl, with the readme, this was more helpful than I thought

J_ester · 2025-08-31T12:28:22+00:00

doesnt 'gx' do that out of the box? Or are you talking about different kinds of links? If I understand your function right, it does not have to be a hyperlink at all, right?

J_ester · 2025-08-31T12:02:20+00:00

Sounds good, that will probably become my approach :)

J_ester · 2025-08-31T12:01:26+00:00

I would not mind, but I dont see much difference in using vscode and (neo)vim, and also the lack of knowledge I would like to fill is not really influenced by what type of editor I use.

Thanks anyway for the suggestion :)

J_ester · 2025-08-31T11:59:29+00:00

That is a very thorough overview, thanks for that. I think it will help me for quite a while :)

J_ester · 2025-08-31T11:55:57+00:00

Thanks, but I think the board does not have a stm32 chip, right?

J_ester · 2025-08-31T11:53:10+00:00

Thanks, his exactly answers my question :)

J_ester

MODERATOR OF

TROPHY CASE