I'm trying to get to grips with the relatively new help system fronted by Microsoft Help Viewer 1.0.
I've found the SDK (at http://www.microsoft.com/en-us/download/details.aspx?id=14923) and have started working through it. I've used Help Library Manager to add the modified help file in step 9 of the "Walkthrough: Branding Package and Content" tutorial, but step 10 tells me to view help by typing a command into a command prompt that starts "ms-xhelp:///". The command prompt responds with a generic unrecognised command response. Pasting the whole thing into Chrome just does a Google search, so obviously that's not recognising it, and pasting it into Internet Explorer attempts to start doing something but then pops a message up "There was a problem sending the command to the program".
Remarkably, this appears to be the first post on here containing "ms-xhelp", and no tags seem directly relevant.
I do have VS2010 installed and it runs help correctly. If I modify the tail end of the URL the web browser opens in, I can get at the newly installed help file, but piggybacking on something that knows what it's doing is unsatisfactory and doesn't show me where things are going wrong. Does anyone know why the "ms-xhelp" approach isn't working?
Related
Please forgive my ignorance, Any advice/directional assistance would be greatly appreciated.
I have a small app that reads data from an API with json requests.
One of the actions the app needs to do is to download a given PDF and open it either in the app, or in the OS default viewer.
I have followed several guides, but I think I am not including all needed files or something. The guides don't speak of including files of any type, but I still get errors.
In this link for example I followed the steps, but I am getting an error when I add these two lines in to the script at the bottom of the page:
var fileTransfer = new FileTransfer();
console.log(FileTransfer);
When running that I get the error Uncaught ReferenceError: FileTransfer is not defined at employee_documents.html:102
I am sure that either i am not including the files correctly in netbeans or I am missing something simple...
Any advise would be greatly appreciated.
To answer the question specifically. In order to solve the error, you need to run the cordova app using the CLI. In that way, the plugins installed from your cordova will be used otherwise if you're only running it via refresh or something similar it will produce an error like this.
In other words, type this command in your CLI:
cordova run browser
You can change this to your preferred platform (android, ios)
Hi I'm running VSCode on my mac and Windows 10 machine. They've both started displaying the same symptoms after the latest update/rollback.
Every couple of keypresses I get the output box appear, with the "HTML Language Server" selected in the dropdown. The error displayed is:
[Error - 13:47:09] Request textDocument/documentLink failed.
Message: Request textDocument/documentLink failed with message: Path must be a string. Received undefined
Code: -32603
This gets repeated indefinetly and is making VSCode unusable. I'm editing some JSP / JSTL files so I'm wondering if it's some non-valid HTML setting it off, but this has never been an issue before.
All research I've found of this error seems to suggest a faulty extension, but I've currently not got any installed.
Help appreciated!
This is a known issue and, as per this Github issue, the workaround is to open Visual Studio Code on a folder instead of a file.
I too had this popping up this morning, google pointed me to vscode's extensions, so I went through the vscode extensions, updated them all and Debugger for Chrome (2.2.0) was the only one fitting the Error message.
Since I do not have the time right now to file an issue (and answer follow-ups) on https://github.com/Microsoft/vscode-chrome-debug/issues I have just disabled the extension for now.
One thing to note is, while vscode says it is version 2.2.2 in the extension panel, it is 2.2.0 on its marketplace page and github. Might be of some interest to dive in and find out where the extension panel picks up its - false - version number - and find out whether this has some impact on creating the error.
I am working on a local project (read: offline) and I am trying to get Brackets' live preview to work since it comes in handy quite often.
Right now I have opened my project files using Brackets' "open file" option since it supposedly maps the path to the source files. Although I am getting an error saying In order for Live Preview to connect, Chrome needs to be relaunched with remote debugging enabled.
I have read else where that Chrome, by default, does not need to be relaunched for that change and that Brackets force this flag by itself.
I have tried reinstalling Brackets, launching with another project and searched all over Chrome for this flag and did not find any thing.
Any tips?
This page shows you how to instal remote debugging! It's a Chrome dev tool. It's geared towards android apps for whatever reason, but I had that same error, and following the instructions on that page helped me launch the brackets page.
If that doesn't work, here are some troubleshooting tips that have helped me out with live preview:
1) Make sure your filename has a .html at the end
2) Use different browser (I've found chrome to be a bit finicky with brackets)
3) Make a different blank file, launch that, then launch the file
Open the folder, not the file, and then select the file.
plz anyone can tell me how to open our project at Appmobi XDK. i am facing a problem that i have install it but its not allow me to open projects. when i tried to open my project a message comes unable to open a project.
now i need your help guys.
Thanks
The very first thing you need to do is to go to xdk.appmobi.com (in google chrome) and download/install our xdk. (Need Java installed also)
During the install you will need to set a default appmobi directory. This is where your app files will be stored.
Create a new app from within the XDK. You can then click the edit the source code button in the tool bar to edit your code. Here you can update the file with your own code.
You can check out a video that explains the xdk at http://www.youtube.com/watch?v=MWV8kOJlGmc Some things might have changed visually with the current version of the XDK, but essentially its the same.
Some things have changed/moved around the screen since we made the video, but essentially its functionally the same.
Check it out as it will give you tips/how To's to using the XDK.
Also, posting in our forums (forums.appmobi.com) will get your questions answered sooner!
I have a script that loads a php page for variables. There are no problems when the swf is uploaded to the site but when I run it locally, I keep getting "Error opening URL" messages. I'm using absolute pathing and if I paste the URL my script is using in a browser, the correct page opens. This only started happening after the site changed servers. Any ideas what the problem could be? Thanks.
The "Error opening URL" seems to be caused by a number of issues. I have tried to keep track of all the different solutions I have used in the past to fix the problem. Ever time I encounter the "Error opening URL" the solution is different. Hopefully one of these solutions helps you.
I usually find the following solutions on google.
- Make sure crossdomain policy is setup correctly.
- Set a bunch of variables like Security.allowDomain(domainHERE)
- Change publishing setting for your flash file.
- Make sure your connecting to the right url.
Here is what works for me... usually.
1) Make sure you are connecting to the right URL.
Use the full path, don't use relative links. Also, copy and paste the url in your web browser to see if it connects.
You can also use flash.events.HTTPStatusEvent.HTTP_STATUS to view the HTTP headers but I would recommend you check out solution 5 first. Its a much easier way with more details.
Source: http://www.judahfrangipane.com/blog/2007/02/15/error-2032-stream-error/
2) Put a crossdomain.xml file in the root of your server (usually public_html or www)
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM
"http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*"/>
</cross-domain-policy>
Source:
http://www.senocular.com/pub/adobe/crossdomain/policyfiles.html
3) While editing the flash file, press Ctrl + Shift + F12
Make sure Local playback security is set to Access Network Only.
4) If you are hosting locally using MAMP, WAMP, XAMP or something similar, skip this step. Otherwise, Call your webhost and yell at them ;)
I have hosted with godaddy, hostgator and liquidweb. It seems that all of them have some kind of firewall setup blocking flash from accessing the files you want it to.
Give your host a call, tell them your problem and ask them to whitelist the files you are trying to connect to and you should be good to go.
Remember, everytime you want to connect to a new file, it has to be whitelisted. I always forget this and it takes me 3 hours to figure out why changing the name of my file or moving it messes everything up. :)
5) Use Charles Web Debugging Proxy Program to gather some important information.
I will break this down into a few steps.
Usually for me the "Error opening URL" is due to a coding problem on the site I'm trying to connect to.
Open Charles
Run your flash file
Select the site your flash file tried to connect to in Charles side bar.
View the Response tab near the top.
On the Response tab you should see a few other tabs near the bottom. View the Headers tab.
See what HTTP_Status was returned. Then look search this page to see what that status code means. It will give a somewhat broad definition but it still helps narrow things down.
500 Means a problem with your server... If your server is running fine, then its most likely a code problem.
Then view the Text tab near the bottom of the Response tab. This will show you exactly what that webpage looks like to flash. If your server is in some kind of debug mode where it displays errors, this is where you will see them.
Well I hope this helps someone. I will try to continue to update it with more issues and solutions I run into. This is probably the number one problem I run into with flash. Super annoying!
Crossdomains.xml file possibly?
not really a solution, but a work-around:
before CTRL-ENTER on your .fla, do a CTRL-S
this seems to work about 90% of the time for me
NOTE: I never had this problem until one random day about 6 months ago. Now it plagues most of my old projects, cs4 or cs6.