Got an idea for enhancing PureBasic? New command(s) you'd like to see?
-
blueznl
- PureBasic Expert

- Posts: 6166
- Joined: Sat May 17, 2003 11:31 am
-
Contact:
Post
by blueznl »
an additional field in the debugger output window, that shows the unprocessed line behind the debug statement...
example:
Code: Select all
b = 1
c = 2
debug b
debug b+1
debug abs(c)
output:
Code: Select all
debug eval
-------- --------
b 1
b+1 2
abs(c) 2
this could really help out finding bugs, as one doesn't have to correlate debugger output with input (varnames etc.)
( PB6.00 LTS Win11 x64 Asrock AB350 Pro4 Ryzen 5 3600 32GB GTX1060 6GB)
( The path to enlightenment and the PureBasic Survival Guide
right here... )
-
Dare2
- Moderator

- Posts: 3321
- Joined: Sat Dec 27, 2003 3:55 am
- Location: Great Southern Land
Post
by Dare2 »
If so, maybe on another line?
Otherwise something like
Code: Select all
debug OpenWindow(0, 100, 200, 195, 260, #PB_Window_SystemMenu | #PB_Window_MinimizeGadget | #PB_Window_MaximizeGadget, "PureBasic Window")
Disappears into the neverland on the right.
@}--`--,-- A rose by any other name ..
-
blueznl
- PureBasic Expert

- Posts: 6166
- Joined: Sat May 17, 2003 11:31 am
-
Contact:
Post
by blueznl »
i was indeed thinking about two colums, so overlong texts in the left column (what generates the output in the right) is hidden from view
( PB6.00 LTS Win11 x64 Asrock AB350 Pro4 Ryzen 5 3600 32GB GTX1060 6GB)
( The path to enlightenment and the PureBasic Survival Guide
right here... )