Fix startup crash due to invalid CustomTkinter arguments #90
Conversation
- Remove unsupported 'pady' argument from CTkFrame constructor. - Fix 'text' CTkTextbox initialization by adding missing 'root' master. - Change 'borderwidth' to 'border_width' in CTkTextbox constructor. - Remove unsupported 'highlightthickness' argument from CTkTextbox constructor. These changes prevent ValueErrors during module-level initialization of UI components.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This PR fixes a startup crash in RuneScript caused by passing unsupported keyword arguments to CustomTkinter widgets.
Key changes:
src/views/tk_utils.py, removedpady=2from thetoolbarCTkFrameconstructor. In CustomTkinter,padymust be applied via geometry managers, not in the constructor.textCTkTextboxinitialization by providing therootmaster widget and fixing argument names (e.g.,borderwidthtoborder_width).highlightthickness=0fromCTkTextboxas it is not a supported argument.These fixes ensure the application can start without raising
ValueErrorduring the import of UI utilities.PR created automatically by Jules for task 6566033497973238560 started by @ixegod