search

dymosoftware / DCD-SDK-Sample

DYMO Connect SDK Samples
Other
60 stars 27 forks source link

.NET Sample generates invalid PDF417 codes #7

Closed fssup closed 4 years ago

fssup commented 4 years ago

Printing PDF417 codes from the .NET Sample produces invalid PDF417 codes (both in preview and in actual print result).

Info: DCD 1.3.1 on Windows 10 1909 x64 Visual Studio 2019 DYMO.Connect.SDK 1.3.1.115 Installation steps followed from WPFSDKSample

Steps to reproduce:

  1. Installation according to WPFSDKSample
  2. Open WPFSDKSample.csproj in Visual Studio 2019
  3. Build Solution
  4. Open DCD 1.3.1
  5. Create new label with PDF417 code with some string of text (e.g. 3F21C736502C8A39)
  6. Save label to label.dymo
  7. Open bin\Debug\WPFSDKSample.exe
  8. Click browse -> select label.dymo
  9. Preview is now showing an invalid PDF417 code
  10. Select printer and roll selection and click print label
  11. Printer now printed an invalid PDF417 code

Example of invalid preview of code 3F21C736502C8A39 image

Example of valid code from interface of DCD1.3.1 of code 3F21C736502C8A39 image

I initially posted this to the framework repo in error.

markheloking commented 4 years ago

Why did you close this? The issue is still very much present on current version.

dymosoftware commented 4 years ago

Sorry, it was a mistake. We are looking into this issue.

dymosoftware commented 4 years ago

Not able to reproduce this issue. image

Could you attach the label file which you get the wrong preview?

dymosoftware commented 4 years ago

I get it with tape labels. We will look into it.

fssup commented 4 years ago

Any update so far?

Label used: D1 12mm Black on White (S0923310)

dymosoftware commented 4 years ago

We have listed a package that includes a fix for this issue. Try DYMO.Connect.SDK 1.3.1.160-beta.

fssup commented 4 years ago

Tried with 1.3.1.160-beta, and it now both previews and prints valid PDF417 codes.

It may be handy to include somewhere easily accesible (one of the READMEs?) that since version 1.3.1.160-beta one should (must?) include the new DymoSDK.App.Init() call at the start of programs built with the SDK.

Currently it's rather hidden in one of the version changelog REAMDE.txt's