Profiling in the Webclient?

ID:2154535
 
Oct 2 2016, 2:53 am
Problem description:

The 509 changelog says the following about profiling in the webclient:
Profiling options have been improved for the webclient. The classic browser interface can be used in a popup browser:

byond://?debug=profile;window=mypopup

Or, mostly unformatted output can be sent to a control, paving the way for a dedicated profiler control:

byond://?debug=profile;output=mycontrol
byond://?debug=profile;switch=off;output=mycontrol

Which is great, except it is either broken or doesn't really explain how to actually access the profiler. For example:

src << link("?debug=profile;window=profiler")


If I'm reading it right, the above code should open up some kind of profiler. However, it doesn't do anything. Is there something I'm missing, or should I post a bug report?
Oct 5 2016, 9:02 pm
Bumping, still need help w/ this!
Oct 6 2016, 5:38 am
Did you try with the pre-pended BYOND protocol?

src << link("byond://?debug=profile;window=profiler")


Or just clicking on the URL:

"byond://?debug=profile;window=profiler" from within your webclient instance?
Oct 6 2016, 9:10 am
Tried both of those, yep. No effect.
Oct 6 2016, 9:24 am
Do you actually have a window/control named "profiler"?
Oct 6 2016, 9:26 am
wait wait wait
do you have debug privs on your server?

you know a cfg/admin.txt file
with doohl role=admin
Oct 6 2016, 9:28 am
In response to Super Saiyan X
Ah, shit. I forgot about that. I'll try it.
Oct 6 2016, 9:32 am
EDIT: Nope, doesn't work. I suspect the issue may be that I don't have a control called "profiler."
Oct 6 2016, 4:09 pm
do you have client/authenticate set to 0?
Oct 6 2016, 4:13 pm
In response to Super Saiyan X
No.
Oct 6 2016, 4:56 pm
This has been solved with SSX's help. The solution can be found in id:2156448