You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here's the update with the issues I could find from the built types.
I assume that functions with repeatedly the same problem are due to logic issues in the docs enginee and that one-offs are just a data-input issue.
All of these can be seen from the website (I hope - I checked as many of them as I could…).
Sorry if I'm giving you the function definitions from my lua types, instead of from your docs directly.
I hope this helps, keep me posted if you need any help with anything.
Uneven position of argument «optional» in pattern
Lots the functions will have <optional> <type> <identifier> whilst others will have <type> <optional> <identifier>. This shouldn't be a priority issue, though - it's going to be fairly easy for me to address this with logic in the lua types.
---@returntakename functionreaper.GetTakeName(take) end
Functions with typos in params (typically, adding quotes around the param name)
functiongfx.init("name", width, height, dockstate, xpos, ypos) end
Functions that have first retval optional and not the second
---@returnMediaTrack|nil tr, string infofunctionreaper.GetThingFromPoint(screen_x, screen_y) end
Functions that have two identifiers as return values (typically: Lua: number startTime retval, number endTime = reaper.BR_GetArrangeView(ReaProject proj)). The expectation for parsing the docs is that there would be only one identifier per value.
---@returnnumber|nil retval, number outputLatencyfunctionreaper.GetInputOutputLatency() end---@returninteger|nil retval, integer regionidxfunctionreaper.GetLastMarkerAndCurRegion(proj, time) end---@returnnumber|nil retval, number endTimefunctionreaper.BR_GetArrangeView(proj) end
Hello,
Here's the update with the issues I could find from the built types.
I assume that functions with repeatedly the same problem are due to logic issues in the docs enginee and that one-offs are just a data-input issue.
All of these can be seen from the website (I hope - I checked as many of them as I could…).
Sorry if I'm giving you the function definitions from my lua types, instead of from your docs directly.
I hope this helps, keep me posted if you need any help with anything.
Uneven position of argument «optional» in pattern
Lots the functions will have
<optional> <type> <identifier>
whilst others will have<type> <optional> <identifier>
. This shouldn't be a priority issue, though - it's going to be fairly easy for me to address this with logic in the lua types.Functions with untyped params
Functions that list
identifier
as a data typeThere's hundreds of these. A little sample:
Untyped return values
Functions with typos in params (typically, adding quotes around the param name)
Functions that have first retval optional and not the second
Functions that have two identifiers as return values (typically:
Lua: number startTime retval, number endTime = reaper.BR_GetArrangeView(ReaProject proj))
. The expectation for parsing the docs is that there would be only one identifier per value.Functions that have
identifier
as a return typeThe text was updated successfully, but these errors were encountered: