Hi,
I encounted the problem mentioned here, which is tricky: sometimes the problem will appear, sometimes not. I want to know whether there are more advanced methods for users to dubug the wingide itself.
If so, I can dig deeply into the issue by myself and then give the feedback.
Regards
There is some added logging that can be turned on and off for different sub-systems with the internal-*-logging-start/stop commands, and this goes into the ide.log file in the user settings directory. You can see the logging commands by doing Edit > Command by Name and then typing 'internal'. The available commands are shown in the completer.
They are also listed in https://wingware.com/doc/commands/top... (search for 'internal-').
However, this is probably best done on request of Wingware support staff, since the output may be difficult to interpret and/or not relevant to the problem at hand.
You can actually also get the source code under NDA and debug Wing with itself. But things like the analysis system are hugely complex asynchronous code so it may not be that much fun to try to track things down on your own. :-)
By saying NDA, do you mean:
https://wingware.com/pub/wingide/supp...
And can it be signed electronically?
Regards
Yes that's it and can be sent in by email. Sorry for the slow reply but apparently we are not getting notifications of every comment anymore for some reason (a but in the forum no doubt).
Comments