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
While testing 4.7.0test3 on testnet using the GUI in windows 10 I found the below issue.
I had an anomaly on creating the various asset types. On creating qualifiers and sub qualifiers that the gui textbox to input the token name was different for the various asset types. That is a prefix the # was required for that asset type. The other asset types had the appropriate prefix concealed from the user so that they didn't have to know the prefix required, just select the correct asset type from the dropdown menu and an allowed name.
I would prefer to keep the process the same for a more unified user experience.
The text was updated successfully, but these errors were encountered:
While testing 4.7.0test3 on testnet using the GUI in windows 10 I found the below issue.
I had an anomaly on creating the various asset types. On creating qualifiers and sub qualifiers that the gui textbox to input the token name was different for the various asset types. That is a prefix the
#
was required for that asset type. The other asset types had the appropriate prefix concealed from the user so that they didn't have to know the prefix required, just select the correct asset type from the dropdown menu and an allowed name.I would prefer to keep the process the same for a more unified user experience.
The text was updated successfully, but these errors were encountered: