| Author |
|
Viper
Groupie
Joined: January 14 2007
Location: United States
Online Status: Offline
Posts: 88
|
| Posted: January 31 2015 at 07:29 | IP Logged
|
|
|
Dave,
I wasn't quite sure how to search for this before I posted, so please forgive me if it is a known problem.
In Triggers, if one field, say the Action field, causes the row to expand vertically, it appears that the Trigger ID field is going past the end of the Trigger ID variable and grabbing extra data. Not a problem unless it hits the end of a segment which might cause an exception.
Tom
|
| Back to Top |
|
| |
gg102
Senior Member
Joined: January 29 2013
Location: United States
Online Status: Offline
Posts: 246
|
| Posted: January 31 2015 at 11:08 | IP Logged
|
|
|
Be advised, this also happens in Macro Detail:
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: January 31 2015 at 11:27 | IP Logged
|
|
|
Tom,
Nothing to worry about  . That data is always there
and is just normally hidden by the size of the row.
Its just internal values used within PowerHome
relevant to proper operation.
I'd like to figure out a way to "hide" them as they do
kind of detract when the row autoexpands (it wasnt a
problem in earlier versions when autoexpansion wasnt
there).
I'll take a peek and see what I can do about hiding it
but in the meantime, its normal and won't affect
operation.
Dave.
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome Bug Reports
Topic: Variable Overrun
