why does SAVE TASK clear breakpoints?

[philkryder]

when testing,
I often set many breakpoints in debug mode.

but,
I am required to SAVE the task before running a test.

The Save Task
clears all the breakpoints.

then I have to go in and re-add the breakpoints.

?is there a way to stop clearing the breakpoints between each test run?

[TylerMitton]

good question! this has been bugging me for a long time. it's silly to have to re-add them any time you make a change!!!

also, a task that is really long and complex cannot be run in debug mode... it crashes AA for me. perhaps this has been fixed in version 6.

[philkryder]

Originally Posted by TylerMitton

good question! this has been bugging me for a long time. it's silly to have to re-add them any time you make a change!!!

also, a task that is really long and complex cannot be run in debug mode... it crashes AA for me. perhaps this has been fixed in version 6.

what do you mean by "long and complex?"

100 statements
500?

1000?

would you download the ATMn that I uploaded in my thread on SLOW editting and see how fast you can make a change in it?

thanks much!
Phil

[forumsupport]

Hello,

The breakpoints are not stored, so when you close the editor window all of the breakpoint information will be lost. It is an enhancement and we have forwarded it to product development team to address it in future release.

Thank you for your suggestion.

[philkryder]

Originally Posted by forumsupport

Hello,

The breakpoints are not stored, so when you close the editor window all of the breakpoint information will be lost. It is an enhancement and we have forwarded it to product development team to address it in future release.

Thank you for your suggestion.

but,
I don't close the editor window.

I simply edit one statement (after have learned I need to make a change from the debugging run)

and then
I SAVE the ATMN before running it.
If I don't save it,
I can't run it to debug it.

I don't close the edit window.

I am looking at the code with breakpoints, and then I click save or CTL+S
the save occurs
and the breakpoints DISAPPEAR?!?@#

Phil

[TylerMitton]

haha... ya i guess "long and complex" is pretty vague. My tasks are usually less than 200 lines... maybe 180. I think the issue may be more related to the number of commands that are run... so while my task may be only 200 lines long, it will go through a csv file that is 20,000 records... so it can be running over 100,000 commands... depending on how many commands are within the loop. If I get a chance I'll have a look at your task this afternoon.

I wonder if AA secretly closes and opens tasks every time you save them... which makes no sense at all... but it would not surprise me.

Look forward to seeing supports comments on your last post.

[forumsupport]

Hello Phil,

Try this,

. Set breakpoints.
. Amend the task as per your requirement.
. Directly click on 'Run' or 'Step Over' button.
. It will prompt you to save the task, click on 'Yes' and save.
. It wont remove the breakpoints.

Hope that helps.

[philkryder]

Originally Posted by forumsupport

Hello Phil,

Try this,

. Set breakpoints.
. Amend the task as per your requirement.
. Directly click on 'Run' or 'Step Over' button.
. It will prompt you to save the task, click on 'Yes' and save.
. It wont remove the breakpoints.

Hope that helps.

interesting - so the first time I tried that - it didn't work - but then, I made another edit and it DID retain the breakpoint -

But,
WHY does CTL+S or SAVE destroy them??

Isn't the ATMN saved in both cases?

again, this sort of thing is so counter-intuitive that it cries out for a STICKY OF KNOW RESTRICTIONS AND BUGS...

Who would think that one type of save would destroy breakpoints, but another would retain them?