Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
Custom Watch Script Pluggins
yop:
We are talking about a major improvement here. Game_Ender it is an excellent idea. The scripting support proves to be very powerfull indeed. And I was wondering what it could do...
rickg22:
Hey, if we're onto scripting for debugging, how about changing the watches depending on the context? I hate it when i exit a function and i have 3864* watches that suddenly go undefined.
* Value may vary.
sethjackson:
--- Quote from: rickg22 on January 24, 2006, 01:10:32 am ---I hate it when i exit a function and i have 3864* watches that suddenly go undefined.
* Value may vary.
--- End quote ---
:lol:
duncanka:
I'd like to add to this suggestion that there should be a way of configuring each variable type to display a certain data member as the value, as is possible in Visual C++. It's a bit annoying to have to travel down several layers of tree just to look at a simple std::string's content. (Or was that obvious? :) )
By the way, will any of this affect saved watch files? Are those going to be script-ified also? I guess that would kind of be what Rick is talking about - having predefined watch files or something to be activated at different lines/breakpoints/whatevers.
EDIT - OK, apparently I can't read. Sorry for stating the glaringly obvious :oops:...
Game_Ender:
--- Quote from: duncanka on January 24, 2006, 04:52:45 am ---I'd like to add to this suggestion that there should be a way of configuring each variable type to display a certain data member as the value, as is possible in Visual C++. It's a bit annoying to have to travel down several layers of tree just to look at a simple std::string's content. (Or was that obvious? :) )
--- End quote ---
Yeah that was way obvious because that is exactly what I said. The Debugger pluggin asks the script to register the its custom variable, in this case a string. Then when ever that variable is encountered the script is called and either returns the needed debugger print commands or is allowed to call them on the debugger itself. For a string this would be something like "print myStringVar._M_impl_.m_Stuff._MObscureLayers._content_". That result would be shown in the watch wind as "myStringVar = content".
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version