Release Mouse Buddy v3.0.2#1553
Conversation
…0.9.3 requirement Let me know if I did any of this wrong. I'm pretty much a novice here. Builds and tested.
|
Hi @cfillion, please review the changes and let me know if good. I'm a relative novice here. And to answer an earlier question: yes, ChatGPT helped with portions of the script. There's some hand-rolled code from ToursitKiller that is the basis of this script and I built upon with ChatGPT to help with scripting additional features on top of that and ReaImGui code. This is noted in the comments. |
|
The indentation of the metadata header got messed up and there are 30 Blindly AI-generated scripts and code not submitted by the original author are generally not allowed here. Did Touristkiller give permission or a license for their part of the code to be used this way? |
|
Tourist Killer gave the ok in the Mouse Buddy thread in the forum, post
here:
Cockos Incorporated Forums - View Single Post - Script: "Mouse Buddy" Mouse
Modifier Context Hints - Thanks TK! Now at Version 3!
<https://forum.cockos.com/showpost.php?p=2843391&postcount=19>
I'm totally fine not having the script on ReaPack. I only even tried
because multiple users in that thread kept requesting it. I'm just as happy
to say "sorry, I tried but ReaScript doesn't allow ChatGPT generated
ReaScripts".
…On Thu, May 1, 2025 at 2:28 PM Christian Fillion ***@***.***> wrote:
*cfillion* left a comment (ReaTeam/ReaScripts#1553)
<#1553 (comment)>
The indentation of the metadata header got messed up and there are 30
r.ImGui_* remaining (ignoring the first two which are OK)...
Blindly AI-generated scripts and code not submitted by the original author
are generally not allowed
<https://github.com/ReaTeam/ReaScripts/wiki/Guidelines> here. Did
Touristkiller give permission or a license for their part code to be used
this way?
—
Reply to this email directly, view it on GitHub
<#1553 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMPCJQWZ54FJFTUKVIF4MVD24JRUDAVCNFSM6AAAAAB36Y54AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBVGQZTIMBRGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
To clarify, it's only when the AI's often subtly incorrect output is blindly trusted that it becomes a problem (just testing the script "it seems to work" is not enough: human reasoning on the code is required). With proper understanding of the code and the AI artifacts cleaned up, a good AI-assisted ReaScript can be indistinguishable quality-wise from a 100% human one. Those are fine. Keyword being AI-assisted, not AI-generated. (Current AI tech is unable to reason. It only predicts the most likely "next word" over and over.) You'd be welcome to manually fix the AI's blunders and submit the correction.
|
|
Thanks for the input.
I can read the scripts insofar as being able to follow along with the comments and logic, but the coding/syntax is lost on me beyond "does it work".
Appreciate your guidance!
Regarding the upper-case string thing...I vaguely recall that being intentional to help make the matching easier to the .HTML headers. If I'm not remember wrong (this was months ago now), I think we (me and the machine) were getting errors trying match lower-case (from the API) to sentence-case (in the .HTML file), so some level of conversion was needed.
But I'm just a monkey at a typewriter with this stuff. Then again, I've gotten worse results with human developers at my dayjob! ;)
Anyway, thanks again!
…On Thu, May 1, 2025 at 3:23 PM Christian Fillion ***@***.***> wrote:
*cfillion* left a comment (ReaTeam/ReaScripts#1553)
<#1553 (comment)>
To clarify, it's only when the AI's often subtly incorrect output is
blindly trusted that it becomes a problem (just testing the script "it
seems to work" is not enough: human reasoning on the code is required).
With proper understanding of the code and the AI artifacts cleaned up, a
good AI-assisted ReaScript can be indistinguishable quality-wise from a
100% human one. Those are fine. Keyword being AI-assisted, not AI-generated.
You'd be welcome to *manually* fix the AI's blunders and submit the
correction.
get_mouse_context for example contains some pretty suspicious code... (
BR_GetMouseCursorContext always returns lowercase strings, yet the code
checks in case it might not be strings then converts to uppercase with
string.upper, only to re-convert to lowercase immediately after but this
time exhaustively using hard-coded values... except in the second
native_ctx branch where it uses string.lower to do the same thing. Except
for `segment = "TRACK" which stays upper-cased unless window is "tcp".)
—
Reply to this email directly, view it on GitHub
<#1553 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMPCJQXU2KEQ2E5HXGLB3LD24JYC7AVCNFSM6AAAAAB36Y54AWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQNBVGU3DMMBTGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
2 participants
No description provided.