I have included the file extend/explorer.inc under SILK runtime. When I try to run the test, I am seeing following error
htmlpage.inc(378) - Too Many arguments to function Click
htmlpage.inc(399) - Too Many arguments to function Click
explorer.inc(361) - Too Many arguments to function Click
explorer.inc(371) - Too Many arguments to function Click
how do I resolve this? What is causing this error.
it would help greatly if you could post the code line of your test where this error happens, so we could see with which parameters you are calling the Click method.
Are you by any chance using 4Test's reflection like mechanism (the '#' operator) to call the click function with more than four arguments?
Related
I have created a demo app that applies multiple filters to an image (it is inside the project) and shows buttons in a UIScrollView with that images set as a background image. So, all the logic happens in a method that is called right from viewDidLoad. I'm not using any threading mechanism, so all the work is happening on the main thread.
I'm using Instruments, specifically Time Profiler to find out why the app launches so slow (it is obvious, but I would like to see it in Time Profiler).
When I run it I get the following result in the detail panel (in the root):
And when I press the arrow to see the actual code I get the following:
And this is for every filter operation.
Shouldn't the panel show the actual method inside of which I do filtering?
The main function is not the cause of your app being slow. In your screenshot the listing for main says you spent 0 seconds in main.
The Time Profiler instrument records the call stack 1000 times per second. The main function is the starting point for your app. That means main is going to be on the call stack most of the time your app is running, even though your app is not in main most of that time. The main function being on the call stack is the reason for the 649 ms and 95.5% listings in your screenshot.
Do not worry about the listing for the main function. You have no control over main.
If you want to find your functions in the call tree, select the Invert Call Tree and Hide System Libraries checkboxes. Selecting those checkboxes makes it easier to find your code in the call tree.
I'm trying to see if I can query all execution mitigation policies for a process in one call to GetProcessMitigationPolicy() function (or similarly set them via a call to SetProcessMitigationPolicy() function) instead of doing them individually, one-by-one.
The MSDN page suggests using ProcessMitigationOptionsMask parameter for that, but I'm not really sure how to use it, or what mask are they referring to?
Can someone show an example?
Background:
In Lightning mode, when the Lightning console App is displayed, and based on a specicific message received from my 3rd-party app, I invoke sforce.opencti.setSoftphonePanelVisibility(true), the softphone is first hidden (shortly), then shown again.
As I debugged my code, I could verify, that invoking
sforce.opencti.setSoftphonePanelVisibility(true) led to this behavior.
So, I decided to first invoke
sforce.opencti.isSoftphonePanelVisible(), then depending on the response in its callback, I decide to invoke
sforce.opencti.setSoftphonePanelVisibility(true) or not.
The problem is, when I do this, sforce.opencti.setSoftphonePanelVisibility(true) has then no effect, allthough the OpenCTI call is responded correctly (response.success=true and response.errors=undefined): The softphone is still minimized.
Thanks in advance.
just to share how I solved (workaround) this issue.
A good functional workaround I had implemented was to first of all invoke sforce.opencti.setSoftphonePanelVisibility({visible:true}); in your initialization phase of the softphone. I then check the content of the GUI to be displayed. If there are calls to be display, the softphone has to remain visible. Otherwise, it will be hidden using sforce.opencti.setSoftphonePanelVisibility({visible:false});.
All subsequent calls of sforce.opencti.isSoftphonePanelVisible(); followed by sforce.opencti.setSoftphonePanelVisibility({visible:true}); will be functional to 100%.
It seems that OpenCTI expects that sforce.opencti.setSoftphonePanelVisibility({visible:true}); is invoked first before sforce.opencti.isSoftphonePanelVisible();.
Within a Codename1 app, I'm getting a CrashReport: java.lang.NullPointException: Attempt to invoke virtual method 'void android.graphics.Point.setAntiAlias(boolean)' on a null object reference. This seems to occur after I invoke a "show()" on the main form of my application.
Note that the code runs fine in the simulator, but consistently gets this error prior to doing the "show()" on Android.
Interestingly, if I put a Dialog like this:
Dialog.show("Wait a sec", "Showing interrupt point", "OK", null);
before the .show(), and then click "OK", then everything runs well with no exceptions at all.
But a sleep(5000) instead of the Dialog does not help - still get the exception. So it at least seems like its not a race condition.
I have try-catches wrapped around all of the potentially offending code, and have NOT been able to isolate this. It always gets caught by the CrashReport, and only when running on the Android device.
Any ideas?
The symptoms to this one are pretty strange (i.e. workaround with a Dialog), and it would be interesting to have an explanation. However, since deprecated cn1 (Map) code has seemingly been implicated, I'm going to let this one go and replace this code with the latest Google native maps code. If it recurs, I will post another question then.
I have a $http.put function that updates my database, this happens on a button click. After I update the database once, and stay on the page, with no interaction at all the update function gets called and will update the database with the last information that was inputted.
I've triple checked my code, there is only one occurrence of my update function being called. And the $http.put is inside $scope.update that is an anonymous function that calls the $http.put.
If I update information and then leave the page, and then come back the function does not fire on it's own.
Here is my Github for the project. I will pull out any specific code that you want to see, but I'm not sure what to show because there are 4 files involved. Those files are
(client/scripts/app.js)
(routes/products.js)
(public/views/routes/adminIndex.html)
(public/views/routes/modProduct.html)
Code is Here
Add a console.trace() just before the $http call to see what is calling it.
You can also use the developper console of your browser and add a breakpoint that will stop the code execution and let you inspect everything (stack trace, current context, etc). Chrome is particularly good at that.