Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email
?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News:
*NEW*
Current Version on
STEAM
:
16.026
Logfile:
EN
,
DE
Webchat:
Visit the chat
Home
Help
Search
Login
Register
GLBasic forum
»
Main forum
»
Bug Reports
»
Debugger becomes un-usably slow when using large-ish arrays
« previous
next »
Print
Pages: [
1
]
Go Down
Author
Topic: Debugger becomes un-usably slow when using large-ish arrays (Read 3127 times)
AndyH
Dr. Type
Posts: 383
Debugger becomes un-usably slow when using large-ish arrays
«
on:
2008-Jan-24 »
I'm finding that when using arrays the debugger becomes unusable because it is so slow.
For exaggeration purposes, here is a large array:
DIM t[160][160]
Was thinking of using it to store a level 160 tiles across, 160 down - a lot of array elements. The debugger upon pressing F10 to go to the next line will refresh the Variables panel in the editor each time and I guess is having to update each element in this array. It can take a few seconds.
Can you optimise this?
Maybe only update the parts of the arrays that are expanded so you don't have to rebuild such large structures? When the user clicks the + to expand a node in the array you could fetch the part required for that to help speed things up?
Jamagic's debugger (a long dead programming language) allowed an option in the project settings to force the debugger to show NO variables unless you placed some special debugger commands in your source to tell it to add a specific variable to the debugger watch list. Maybe you could do something similar?
Logged
Andy H
ovine by design
Kitty Hello
code monkey
Administrator
Prof. Inline
Posts: 10851
here on my island the sea says 'hello'
Debugger becomes un-usably slow when using large-ish arrays
«
Reply #1 on:
2008-Jan-24 »
Excellent idea. I have a project options variable, where you can specify maximum array size in debugger. Very clever.
Logged
AndyH
Dr. Type
Posts: 383
Debugger becomes un-usably slow when using large-ish arrays
«
Reply #2 on:
2008-Jan-24 »
That works much better. The good thing is, like types, I can just dump out contents of an array to the output window if needed, but you can still set it to show the first n number of elements too.
Thanks Gernot!
Logged
Andy H
ovine by design
Print
Pages: [
1
]
Go Up
« previous
next »
GLBasic forum
»
Main forum
»
Bug Reports
»
Debugger becomes un-usably slow when using large-ish arrays