Mac OS X Download link:
Mac OS X Download link:
Windows Download link:
It has come to our attention that Google Chrome is flagging calls to the DYMO Web Service as “not secure.” This has been causing many of our users to have issues when printing through Chrome.
We have found the issue and have an internal fix undergoing QA testing at this very moment. We estimate the fix will be released within 2 to 3 weeks. We apologize for the inconvenience at hope this will be resolved soon.
In the meantime, please consider several temporary fixes that have been identified within the below blog post:
We have been receiving a lot of support inquiries with regards to a missing DYMOPrinting.dll file. If you have this problem, the simplest solution is to copy the DYMOPrinting.dll file from your installation folder to the folder where your application is executing.
Our blog had some login and posting problems for an extended period of time due to unforeseen technical difficulties. As a result, we were unable to immediately respond to many inquiries over the past few weeks.
The problem has been resolved as of today, so any inquiries that were posted within the last month or so will now be addressed ASAP.
Thank you for your understanding!
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.
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.
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:
LabelWriterPrintParams prms = new LabelWriterPrintParams(1, "print job 1", FlowDirection.LeftToRight, RollSelection.Auto, LabelWriterPrintQuality.Text);
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.
The latest has been updated to version 1.2.6 as well: http://labelwriter.com/software/dls/sdk/js/DYMO.Label.Framework.latest.js
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!
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.
Phone: 800-942-6739×1 M-F, 8:30am-5:30pm EST
Happy holidays to all DYMO users and developers! Thank you for being with DYMO, for all the questions, comments, and feedback. It’s invaluable!
2011 was quite a year, with a lot of new releases and new features.
Next, we expanded the presence in the web and mobile dimensions by releasing DYMO Label Web SDK, DYMO Label Mobile SDK for iOS, and DYMO Label Mobile SDK for Android. Although SDKs are still officially in the beta stage, we know they were successfully used, e.g. MailChimp used it on iPad for visitor management, and Google itself used it on Android during developers conferences.
Finally, DYMO Label SDK for Windows was released with updated samples and documentation.
On the sad note, after dozen years with DYMO, I am leaving the company and this is my last post.
Anyway, Happy Holidays! Happy New Year! Let new year be better, brighter, more peaceful than 2011. May the Force be with you. Live long and prosper. Bye.