drobdymo

Nov 292016
 

Hi everyone,

Over the years, there has been a lot of confusion regarding our SDK samples. In the past, to get our samples, you needed to download an “SDK Installer” from www.dymo.com. The “SDK Installer” name was a bit misleading as the installer only contained samples, no binaries. As you know, all the binaries required for our SDKs are installed as part of DLS. So in order to clear things up, we’ve consolidated all of our samples into one ZIP file. This ZIP file contains the following:

  • DYMO Framework Samples for C# and C++
  • DYMO SDK High-Level COM Samples for C++, C#, VB, and ASP.NET
  • DYMO SDK Low-Level COM Samples for C++
  • Documentation for both the DYMO Framework & DYMO SDK

This ZIP file can be downloaded here: SDKSamples.zip. Please note that all of the samples in the ZIP file are intended for use in Visual Studio 2015 and using .NET 4.5.1 where applicable.

We also have a number of JavaScript samples that can be explored. While we do not provide the source for these samples directly, you are free to use the dev tools within your favorite web browser to check out the source code for these samples.

  • Print Me That Label – a simple JavaScript sampled that can be used to check if DLS is installed properly and the JS SDK is functioning correctly
  • Preview and Print Label – see a preview of a label in the browser and print the label
  • Print 2 Labels – example of multiple label printing
  • QR Code – barcode printing example
  • Spreadsheet – example of printing multiple labels from an online data source

Furthermore, we have a a diagnostic sample that can be used to ensure your dev/client environment is setup correctly.

  • Check Environment – runs a quick check of your setup and brings to your attention any potential problems

Happy coding!

Sep 302015
 

Hello everyone,

A lot of our SDK users are running into a particular issue printing barcodes where they will be clipped or not printed at all. The issue is actually being caused by a bug in the .NET Framework (v4.0 and newer), specifically in XPS printing. The trigger for the issue is when our printers go into “Barcode and graphics” mode. Unless manually overridden, the DYMO SDK will switch the printer to “Barcode and graphics” mode whenever a barcode or image object is present on the label. When in this special mode, the resolution of the printer changes from 300 x 300 DPI to 300 x 600 DPI. This “non-square” resolution is not handled correctly by XPS and causes the clipping issues.

Below is an example of this issue. The label on top is OK while the label on the bottom is printed with the issue.

IMG1

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.

IMG2

Now that we understand the issue a little better, what can we do about it? Let me start by saying that we have made Microsoft aware of this issue. Since there are no guarantees they will fix the problem, we are currently working on a solution that will be pushed out in a future update of DYMO Label Software. In the meantime, you have a few choices for working around the issue:

  • Design your label in portrait orientation. For most label types, the issue will not arise if the label is printed in portrait orientation. By using the object rotation feature in DLS, you can easily design a label in portrait orientation that will look identical to one designed in landscape orientation.
  • Compile your SDK applications against .NET 3.5. As mentioned earlier, the issue is with .NET Framework versions 4.0 and newer. Current versions of DLS are compiled against .NET 3.5 so you will not see this issue when printing from DLS. However, if you are compiling your SDK application against newer versions of .NET, when your application runs, the newer version of the framework will be loaded. Even though the DYMO SDK binaries are compiled against 3.5, .NET backwards compatibility will kick in and the newer version will be used instead. So, to take this approach, you will need to compile your SDK application against .NET 3.5.
  • Force the print job into “Text” mode. In the DYMO Framework, you can override the print quality setting using the ILabel.Print(IPrinter, IPrintParams) API. An example of how to override this setting can be seen below (the parameter used to change the print quality is marked in bold):

    LabelWriterPrintParams prms = new LabelWriterPrintParams(1, "print job 1", FlowDirection.LeftToRight, RollSelection.Auto, LabelWriterPrintQuality.Text);
    _label.Print(printer, prms);

Thanks for bearing with us on this issue. Rest assured we are working hard to get the fix out. In the meantime, we hope this blog post will help you get your labels printing correctly.

Mar 242014
 

Hello everyone!

A new version of our JavaScript library is now available. This version fixes several printing issues specific to Internet Explorer 11.

The new DYMO Label Framework JavaScript Library 1.2.6 is available here: http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.1.2.6.js

The latest has been updated to version 1.2.6 as well: http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.latest.js

Jan 022014
 

There is currently a bug in Windows 8.1 that causes any label with a barcode to print abnormally in DLS. We are awaiting a fix from Microsoft, but in the meantime, you will need to modify a setting in DLS to workaround the issue. To do this, go to Edit -> Preferences. Navigate to the LabelWriter printer tab and change the “Print Quality” to “Text”.

Preferences

There is one side effect to making this change and that is your labels will always print at a resolution of 300×300 DPI. For barcodes, we typically like to switch our printers into high resolution mode (300×600 DPI) in order to improve barcode scanning reliability. When the “Print Quality” setting is set to “Auto” or “Barcodes and graphics”, the resolution will always be 300×600 if a barcode is present on your label. That being said, for most barcodes, 300×300 DPI is plenty of resolution. You may encounter scanning issues for barcodes with lots of data or 2D barcodes, though.

We apologize for this inconvenience and will keep everyone updated on a fix for this issue.

UPDATE
Microsoft has released a fix for this issue. It can be downloaded from the below links. Thanks Bjorn for the heads up!

KB2911106, released on 13/01/2014, solved this issue in Windows 8.1
Download x86 : http://www.microsoft.com/en-us/download/details.aspx?id=41569
Download x64 : http://www.microsoft.com/en-us/download/details.aspx?id=41570

Nov 202013
 

Hello everyone!

A new version of our JavaScript library is now available. This release addresses compatibility issues with IE11. If your web application is compatible with IE11, we strongly recommend that you upgrade to the new version.

The new DYMO Label Framework JavaScript Library 1.2.5 is available here:  http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.1.2.5.js

The latest has been updated to version 1.2.5 as well: http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.latest.js

Nov 122013
 

Hello everyone,

Today marks the first of our featured software posts. Over the coming weeks and months, we will highlight real applications that use the DYMO SDK. These posts will provide information and quotes from DYMO SDK developers/customers/users/etc. explaining how they were able to successfully integrate DYMO printers into their real world solutions. First up today, Datarecovery.com.

Michael, a programmer/analyst working at Datarecovery.com, says:

At Datarecovery.com, Inc., we use DYMO label printers crucially in our business to keep track of clients’ problem hard drives and other storage media at our offices, as well as the new drives we use for returning data, clone drives we use in recovery work, the containers we store case materials in, and any other equipment and materials associated with a data recovery case. With the DYMO SDK and label templating, we were able to integrate one-click printing of all labels needed into our case tracking system. Once newly received case materials have been checked into our system, we have a “Quick Labels” link that immediately prints labels based on what items were just checked in. We’ve also made a simple jQuery dialog that allows for printing different quantities of the various types of labels at will. The labels include the case number, item type code, checked in date, last name initial, and a barcode for scanning into our system. The extremely simple process, enabled by the DYMO SDK, results in aiding in our critical tracking of all case items.

Here are some screenshots showing how Datarecovery.com has integreated DYMO printers into their case tracking system:

 

If you would like to learn more about Datarecovery.com, please visit their website at www.datarecovery.com. If you would like your DYMO SDK application featured here on the blog, please comment on the following blog post with more information about your software: http://developers.dymo.com/2013/10/31/calling-all-dymo-sdkers/

Oct 312013
 

Hello again,

We at DYMO our very appreciative of our SDK community. Over the years, we’ve seen some very interesting and cool applications that integrate with DYMO printers. We thought it would be fun to showcase some of these applications here on our developer blog! If you’ve been involved with the creation of a DYMO SDK application and would like to have it shown here on the blog, just comment on this post with some information about your application (description, pictures, website link, etc.). We’ll sort through all of the responses and pick some of our favorites and showcase them on the blog. We’ll keep all of the responses private and contact those that we want to showcase directly before posting anything to the blog. We look forward to seeing what everyone has created!

Sep 302013
 

A quick post here to help out some of our developers that are integrating CardScan into their applications. We receive quite a few CardScan SDK questions and usually we have to forward them over to the correct support group. This is due to a miscommunication on our part, and we wanted to get the correct CardScan SDK support information out there. All CardScan SDK questions should be directed to the email and phone numbers below. We apologize for any confusion.

Email: sales@cardscan.com

Phone: 800-942-6739×1   M-F, 8:30am-5:30pm EST

Aug 142013
 

Hello everyone,

We thought it would be helpful to have sort of an “interactive” post where you could ask questions about our SDKs. Here’s how it will work:

  • Add a comment to this post asking any question you like regarding DYMO SDKs. It can be anything: how to setup a simple SDK application, potential bugs you may have encountered, etc.
  • We will sort through your questions and pick a some of the best ones to answer in this post.
  • This post will be updated with the questions and answers so everyone can see them

Once we’ve picked out the best questions, we’ll approve all of the other questions and they will appear in the comments section of this post so other developers can help you out. We’re looking forward to your questions!

  1. Is there a way to interact with Dymo label printers from an iOS app? Sample app would be great. (from Steven Hepting)

Currently, the only way to print from an iOS device is using the DYMO Proxy Service that is installed with DLS. This service acts as the “middle-man” between your iOS device and your DYMO printers. For more information on how to use this proxy service, see the following blog posts: http://developers.dymo.com/tag/ios/. Please note that this service is still in BETA and has not been extensively tested outside of DYMO.

  1. Is the proxy service available for Mac? (from Matthew Dever)

The proxy service is a Windows only tool. Also note, the proxy tool is a beta release and there are no plans to move it out of beta.

Aug 022013
 

Labelwriter.com is currently down. If you are linking to the JavaScript SDK file that is hosted on Labelwriter.com your web application will not work at the moment. As a best practice in the future, we recommend that you do not link to the JavaScript file that is hosted on our servers but download a copy and host on your own servers. This will prevent a couple of issues:

  1. Any outages on our end will not affect your application
  2. Any updates that are made to the latest JavaScript file will not break your application

While Labelwriter.com is down, you can download the latest version of the JavaScript file from here.

We apologize for the inconvenience and hope to have Labelwriter.com up and running again soon.

Update

Labelwriter.com is back up an running. Once again, we apologize for the inconvenience.