[Tool] GPC2 Combos to Macro File

[PoshLemur]

Tonight I release my mostly complete (fully functional) GPC2 script to GMK (macro file) converter.
I had plans to make it more robust but I haven't gone about sprucing it up or fixing the known issues,
and don't know if I will.

You can pass it a GPC2 script and it will extract each combo in the script, converting them into a GMK macro files.

So I release it as is:
https://github.com/PoshLemur/GPC2Macro

Please let me know what you think!
Be sure to read the readme on github, as there are some rather important assumptions!

[antithesis]

Thanks for your contributions of late. This will help to push the Macro development along

[Scachi]

Great work !

I miss the word "combo" in the description a bit.
When I read the title I was wondering how a script should be able to be converted into a macro file.

[PoshLemur]

Thanks!

Oh you're right! I really did fail to specify combos anywhere.

[Sillyasskid]

Might have wanted to comment out the printf("Hello!"); in the testcombo3.gpc

[PoshLemur]

Might have wanted to comment out the printf("Hello!"); in the testcombo3.gpc

The converter is supposed to loudly abort a combo's conversion if invalid commands are present.
The test scripts are just that, they're there to automatically test that the converter is functioning properly.

On that note though. The printf commands are located within a function and the main loop, both of which are completely ignored by the converter because neither are in a combo. The idea being that you can convert a full fledged script's combos into macros with minimum effort; assuming that is that they are well formed. I had plans to implement some dictionaries for console identifiers PS4_, XBX_, etc. Just haven't gotten around to it yet.

[Sillyasskid]

I see. that makes more sense.

[antithesis]

I had plans to implement some dictionaries for console identifiers PS4_, XBX_, etc. Just haven't gotten around to it yet.

Is that necessary? Index values / button IDs would be simpler as that's what the compiler will use.

[Sillyasskid]

Also if the users does not actually include a header with different defined button alias like xb1.gph or ps4.gph then the compiler won't compile with the XB1_ or PS4_ alias's.

Aside from the #define method to create the button aliases, the user also can also manually declare a uint8 variable to represent a button, and use that variable freely within their script.

Your program should work with this

Code: Select all

#define FIRE BUTTON_5

But not with this

Code: Select all

uint8 FIRE = BUTTON_5;