Dymo Label Framework Download
Doreen Kaczmarek
My project involves printing patient labels on a Dymo 400 Turbo. I have installed the latest framework, DYMO.Label.Framework.latest.js, and am trying to use one approach I have found on the web to print the label. My problem is that the XML was designed for an address label and not a longer patient label. When I send to the printer it advances past the next label, wasting one. Plus I want to print the ID not the address or zip code in the bar code. Anyone have any ideas?
You can download the DYMO SDK. Now first thing you need to know is that at least at the time of this writing the the dymo.label.framework.js provided in the SDK does not work. Find the Internet Shortcut under the DYMO Label Framework > Samples > Javascript click on any of these shortcuts. Click View Source to view the source of the page. Look in the section for the DYMO.Label.Framework javascript file. Copy the URL out, and download the file using that URL.
Has anyone tried using the Dymo Label Printer with V8 software? If I create a label template using that software, I am not able to see the contents on my label. I used the Dymo Labview add-on and this works if I create a label using previous versions of Dymo Sfotware.
I am struggling with the dymo software, to change a datafield. Does anybody has succes doing this, if possible send me a sample. Now we use the printlabel.exe programm, but it is kinda slow. All help is greatly appreciated.
A some may be already aware of, Google has announced that it will phase out support for NPAPI in Chrome with the ultimate removal in Sept 2015. We use NPAPI in the framework for plugin support for most browsers except for IE which we use an ActiveX plugin. We are investigating alternatives to NPAPI but we have not come up with a solution yet.
Update (4/20/2015)
It has been our experience that just enabling NPAPI may not be enough. In some instances, close the chrome browser then uninstall and re-install the DLS software for the plugin to appear in the plugin list: chrome://plugins/
Go here to see if your browser has the framework installed correctly: Check Environement
Since the new communication protocol needs to discover the port that the DYMO service is listening on, a new method was introduced, dymo.label.framework.init(callback). This method performs a scan of a range of ports to look for the DYMO service. This method needs to finish before any other DYMO Framework API calls are made. To accomplish this, the method takes a callback method that will be called as soon as the dymo.label.framework.init method finishes.
If the dymo.label.framework.init method is not called (i.e. no user code has been changed) then the Framework goes into backward compatibility mode. It will try to scan the first port in the defined range and if it finds the service, the new communication protocol will be used. If it fails, it will fall back to the previous implementation that uses native plugins (NPAPI/Active-X).
We have added a new tracing feature. This can be used to help debug issues with the new service. The property is called dymo.label.framework.trace. When set to true, it will put tracing messages in the browser developer console. You should set the trace property before calling the dymo.label.framework.init method:
What you may notice is the label with the issue stops printing at a distance across the label that is equal to the width of the label. This is the crux of the XPS bug and as you can see, also affects other label object types as well.
The library now makes use of a new initialization method to perform asynchronous initialization through use of a callback method. Since the library performs initialization in the background, calling an SDK function prior to initialization results in an error. Your code should be updated to call the new dymo.label.framework.init() method while providing it a callback to be invoked by the library when initialization completes. Please note the library invokes this callback whether or not initialization completes successfully.
The dymo.label.framework.checkEnvironment() method returns a CheckEnvironmentResult object along with multiple parameters (please refer to existing documentation on checkEnvironment() method). The new JavaScript library contains an additional property within this object called isWebServicePresent. You can use this property to determine if the web service is actually used.
760c119bf3