VSCode Salesforce evaluate function not working - debugging

After starting the apex replay debugger and when try to evaluate a field (right click then Debug: Evaluate), VS Code displays on the debug console the exact same text I highlighted for evaluation
e.g:
loan.LLC_BI__Product__c --> is showing up in the debug console instead of the value of LLC_BI__Product__c
can you please help - please see image attached
thanks

Related

input is displayed twice in the console of firefox developer edition

I downloaded Firefox Developer Edition latest version and opened its Dev Tools Tab to use its console . All is right and good except that when I write , in the left side a JavaScript and click on the run button , the script is displayed again along with the result like in the following photo:
I do not want the script or input to be displayed twice . I would like to see only the result in the right side . I read the documentation in this web page :
https://developer.mozilla.org/en-US/docs/Tools
and looked in this webpage :
https://discourse.mozilla.org/c/devtools/213?utm_source=devtools/213&utm_medium=tabbar-menu
along with the similar questions section in
stackoverflow.com
However , I could not find a solution to my problem .
The output window outputs the following:
An echo of the script
Messages
Errors
Warnings
Logs
Info
Debug
Unchecking any of the Message types in the task pane will not remove the echo of the script since technically it is not an output message. The same goes for filtering, since filtering is only applied to messages in the output.
This functionality looks like it is by-design and I am sure there might be a reason why it was built in this way, but if it is an issue for you I think you can raise it in their community forums:
https://discourse.mozilla.org/

Show message when print done odoo

I am facing a problem while printing from wizard, all is good that the report is printed but it does not give any popup saying that report is printed only the wizard is closed.
I want to show a popup message when the printing process is done. so i thought to have a warning but then the wizard does not closes by itself.
My code is as below:
try:
return self.env['report'].print_report(active_ids,report_name)
finally:
raise except_orm(('Information!'), ('Sent to Printer ') + str(printer.system_name))
it does popup the information but the original wizard does not closes by itself.
Please help.
When you print report at that time odoo will return report for print in URL, that's why Wizard will not close.
You can see odoo default report, system will print report but wizard will not close automatically.

VS2008 won't show Trace output

I'm using Visual Studio 2008. The Trace output is no longer being shown in the Immediate Window any of my forms except the primary form. When it executes code from within another form (called from that primary form) the Trace output doesn't show up. It used to be fine, and one day it just stopped working. I think this is a setting in VS2008. Anyone have any idea what setting this would be under?
It's got a TraceListener in the code, and that hasn't been touched.
Can you do a quick check and see if the second project is compiling in Release or Debug? If it's Release there's a chance Trace won't be defined and Trace output hence won't show up.
Check that you're referencing System.Diagnostics.Trace, and not the Page.Trace TraceContext object. If you're just doing Trace.Write it might be resolving to the wrong place, depending on your using directives.
There's an item under Options - Debugging - General: "Redirect all Output Window text to the Immediate Window". That should do the trick.
Patrick

Interactive pyDev console at breakpoint

I'm using Aptana Studio with Pydev 1.5.3 to debug my Django applications. I use PyDev's remote debugger and some code in manage.py and for most of the time this setup is working successfully- I can set breakpoints, inspect variables and step/continue through my code.
However, I'd like to execute arbitrary code at the breakpoint- the thing I really miss after switching from pdb to Eclipse debugging. There is an interactive console available in debug perspective but it is inactive for me.
So my question- is it possible to set up an interactive console in PyDev with remote debugger which could "inject" code at breakpoint?
strange, i am using pydev 1.5.6 for remote debugging and I can use the interactive console - i type the cmmand, hit enter, after a while get results back; check your firewall is not blocking anything (if you are sure, the interactive console works in local mode). there is even settings in pydev source code to set how much of stdout should be returned back to client (in chars), it should work
After some digging I discovered that I can use Expressions view to access variables properties and view results of class methods, but that still isn't a complete console at breakpoint though.
With PyDev 1.5.5 it should be possible:
In "Variables" view, you can right-click on a name, then select "change value".
The console is working as well, albeit a bit tricky.
It is only for inspection and in a very strange way: you have to input the text in the "Debug server" console, and you will get the output in the "filename" console.
Note also that you need to press enter twice, leaving an empty line.
While the "empty line" trick is documented, the issue about two different console for input and output is not, and I think it may be a bug.
On my development stack running Apache + mod_wsgi entering commands into the console had their output routed to the site's error logs. To resolve this you have set the stdoutToServer=True and sterrToServer=True to route capture all output to the PyDev remote debugger:
from pydevsrc import pydevd;pydevd.settrace('192.168.2.8', stdoutToServer=True, stderrToServer=True) #clone and put on python path: https://github.com/tenXer/PyDevSrc

Avoid asm__dyld__dyld_start on run when in debug window

Whenever I start my app and I have my view setup to see the code and the console in the debug view (in a all-in-one setup) my source view get switched to asm code for asm__dyld__dyld_start.
Try changing the setting in Run->Debugger Display to "Source Only" instead of "Dissasembly Only".

Resources