Visio Guy
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
Home
Help
Search
Login
Register
Visio Guy
»
Visio Discussions
»
Programming & Code
»
What does in mean when code runs in debug but not in operation?
« previous
next »
Print
Pages: [
1
]
Go Down
Author
Topic: What does in mean when code runs in debug but not in operation? (Read 472 times)
0 Members and 1 Guest are viewing this topic.
paulv45
Jr. Member
Posts: 51
What does in mean when code runs in debug but not in operation?
«
on:
May 07, 2022, 08:49:40 PM »
I am manipulating shape text.
When I do:
objChar.CharProps(visCharacterSize) = 8#
Code runs fine when in debugger using <f8> to step through.
When run normally it exhibits bad behavior.
Is there anything in general this implies?
If I precede the line with a MsgBox to force user interaction, also runs fine.
I've tried update false/true and timer.
Any thoughts?
Logged
Yacine
Hero Member
Posts: 2950
Re: What does in mean when code runs in debug but not in operation?
«
Reply #1 on:
May 08, 2022, 04:36:48 AM »
I know Wapperdude tried it already, but can you too try putting a doevents, once before and once after the assignment?
Logged
Yacine
1 Like
Surrogate
likes this.
paulv45
Jr. Member
Posts: 51
Re: What does in mean when code runs in debug but not in operation?
«
Reply #2 on:
May 09, 2022, 09:02:38 PM »
I did the DoEvents before and after and that fixes the problem.
Tried just before and that also works.
Tried just after and that, not surprisingly to me, fails.
I think we have a fix.
Thanks so much, Yacine. Nice work.
Logged
Print
Pages: [
1
]
Go Up
« previous
next »
Visio Guy
»
Visio Discussions
»
Programming & Code
»
What does in mean when code runs in debug but not in operation?