Debugging granularity

[dgets]

For full beta development, as well as the next issue that I'm going to create that will allow more testing to take place by more individuals, it will be necessary to implement much more granular debugging. IE: debugging of just xpress messaging functionality, or message base (or even down to just posting), or navigation features, etc.

[dgets]

Potential is there now; just not fully implemented yet. As of this point, any level greater than 0 in the stand-alone file turns on debugging; in the future, different integer values or bitfields will turn on different settings to debug. Thinking very much of throwing this into the user's JSON object implementation that I'm creating an issue about in a second here.

[dgets]

Here's where we be standing with things after this morning's foggy debugging and outside assistance:

[dgets]

See also: code location of most of this, mentioned in issue #42. I do believe this is just a matter of user Ddoctest not having a JSON record defined yet; we'll have to catch that and take it to the settings area, if such is the case. Obviously the control flow for that is not working properly if that's what's up.

[dgets]

It appears that I've finally debugged the debugging. Heh. Glad to have this done with. Back to the mHdr issue, now.

[dgets]

Ugh.

Looking for Ddoctest
Skipping line in ddocdbgr
Got: 0 in the first iteration through.
Skipping line in ddocdbgr
Iteration #: 1 got: 0
This appears to be okay JSON.
Iteration #: 2 got: [object Object]
This appears to be okay JSON.
Iteration #: 3 got: [object Object]
Skipping line in ddocdbgr
Iteration #: 4 got: 0
In getNTestLine():
Error trying to read/parse tmpLine: line is null        #: undefined    Error: TypeError
In initDdoc:
Error: userData is undefined    #: undefined    Name: TypeError
Oont nao vhe vhill set Ddoctest's debugging options.

[dgets]

NOTE: This was working on the revisions of 9 days ago. Check out what was different there.

This revision can be found at: commit ID #: abf2e95

[dgets]

Finally got this fixed again (though not with all of the error catching that I want at this point-- but good enough for now) as of the following commit ID#: 24093c1