Home
Help
Search
Login
Register
SlickEdit Community
»
SlickEdit Product Discussion
»
SlickEdit®
»
Debugging in SlickEdit
« previous
next »
Print
Pages:
1
[
2
]
Go Down
Author
Topic: Debugging in SlickEdit (Read 855 times)
Clark
SlickEdit Team Member
Senior Community Member
Posts: 7032
Hero Points: 534
Re: Debugging in SlickEdit
«
Reply #15 on:
February 17, 2025, 01:35:00 PM »
If Project>Close Workspace is enabled, you have a workspace open that can be closed. Maybe I misunderstood your post "I did this and the Build menu options seem to be the ones referring to a Python project, not a single-file one."
Logged
gkl
Community Member
Posts: 23
Hero Points: 0
Re: Debugging in SlickEdit
«
Reply #16 on:
February 18, 2025, 08:51:12 PM »
There is no such option though, it is greyed out (as in attached image).
Logged
Clark
SlickEdit Team Member
Senior Community Member
Posts: 7032
Hero Points: 534
Re: Debugging in SlickEdit
«
Reply #17 on:
February 18, 2025, 09:58:09 PM »
That means the Build menu items should be for a single file project. What Build menu items do you see when a python file is active?
I see:
Execute
Python Options
Add New Build Tool...
Execute works for me. Does it work for you?
I can also use Debug>Step Into or set a break point and use Debug>Start
Logged
Print
Pages:
1
[
2
]
Go Up
« previous
next »
SlickEdit Community
»
SlickEdit Product Discussion
»
SlickEdit®
»
Debugging in SlickEdit