-
Notifications
You must be signed in to change notification settings - Fork 23
_WD_FrameList - <frame..> support + refactoring #434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@mlipok Apologies if we've discussed this previously, but can you explain the need for the
Why does the debug level need to be tracked / modified in |
You mean this part: Lines 772 to 778 in bf98ff5
Becuase I want to get log to the console Line 940 in bf98ff5
But I want to get them only once (when exiting main document) thus all this processing is needed. Lines 935 to 941 in bf98ff5
And for this reason knowing outher value Line 936 in bf98ff5
|
We can get all error messages, maybe it will be better. Thus I can move maintaining |
ALL >> I mean one log per each |
OIC
Yes... as long as it isn't required in _WD_FrameList.
Is that what you want? |
Working on |
I changed concept. but still prevnting redundant logs (most of logs)
the current commits only allow one outer log comming from this:: Line 769 in aa03f90
and on finall log: Lines 821 to 823 in aa03f90
Which can occurs onces per each _WD_FrameList() call. All others are internall and will be prevented from redundant logging
I rethink my approach (about internall processing). Lines 938 to 940 in aa03f90
Please take a look on this: $_WD_DEBUG_Saved usage moved to internall |
I like the direction this is headed towards as the code is much easier to follow IMO. I do have questions about this -- Lines 850 to 852 in aa03f90
and Lines 930 to 931 in aa03f90
I'm having difficulty wrapping my head around how this will work. Won't |
Using this new commit: better $sMessage's In time when
that's what I was thinking when I wrote:
|
still WIP |
Check current chnages from this: usage of $_WD_DEBUG_Saved / $sMessage btw. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO, a function doesn't belong in the related section simply because it is called internally by the UDF being documented. And this information gets used to generate links in the help file, and it doesn't make sense to me to have links to many of these functions from _WD_FrameList. I think that we should evaluate if this is the proper method of documenting these error codes.
Please propose solution by adding new commit. |
Pull request
Proposed changes
Refactoring for better getting more data
Checklist
Types of changes
Please check
x
the type of change your PR introduces:What is the current behavior?
getting the list of frames can stop on specific frames and do not process rest of them
What is the new behavior?
continue processing frames even if one of them fires any kind of issue.
Additional context
#397 (comment)
#433 (comment)
System under test
not related
tested with: