Closed zxtwonder closed 6 years ago
After a further look, it seems that the function argument naming is different between .h and .cpp file - .h uses the original argument name specified in XML and .cpp prefixes them with "arg". This seems to be the root cause of the issue. (I haven't looked at the history around when "arg" prefix is added/removed though.)
But I think this inconsistency caused that the template function generated in header files cannot use the same naming schema as other function bodies generated in cpp files. As a result, should I just rename arg_name to name and value_param to value in the example above?
Hi @zxtwonder! Thanks for you bug report, indeed it looks like the generated files are wrong; it's a bit strange that we didn't catch this bug before.
Yes, it looks like a silly naming issue, and your suggestion should work.
Mistakenly closed from my fork. Reopened.
First of all, thank you so much for providing this great utility. There seems to be trivial issue with the generated template function.
Input method schema:
Generated proxy template function (indent as generated):
Comparing the generated template function and other functions, it seems that the function argument naming and the variantValue reference are inconsistent. Is it correct that the template function should be generated as the following?
Related code: https://github.com/Pelagicore/gdbus-codegen-glibmm/blob/35bef0fab90efa2635c037fd6804eddb13063852/codegen_glibmm/codegen.py#L149