You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to have regressed from this commit, 37b0660
Reverting to the prior implementation of GetNormalizedName() fixes the issue,
varnormalizedName=string.IsNullOrEmpty(name)&&prevAttribute!=null?prevAttribute.Name:name;if(string.IsNullOrEmpty(normalizedName)){thrownewArgumentException("0 length attribute name found not in a 1setOf");}
When the exception is thrown in GetNormalizedName(), tag is Keyword, name is an empty string, and prevAttribute is two-sided-long-edge. If it's helpful I can attach the binary response from the printer.
The text was updated successfully, but these errors were encountered:
@xqrzd Sorry, I missed notification.
If the tag is Keyword, the name is an empty string, and the prevAttribute is two-sided-long-edge, then why was return prevAttribute.Name; not used?
Is prevAttribute.Name also an empty string?
Even if you have 3 attributes with the same name then previous value should be calculated correctly.
It seems to have regressed from this commit, 37b0660
Reverting to the prior implementation of GetNormalizedName() fixes the issue,
When the exception is thrown in GetNormalizedName(), tag is
Keyword
, name is an empty string, and prevAttribute istwo-sided-long-edge
. If it's helpful I can attach the binary response from the printer.The text was updated successfully, but these errors were encountered: