Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Material Type] -- Change to Drop Down List #8299

Open
3Deee opened this issue Sep 2, 2020 · 3 comments
Open

[Material Type] -- Change to Drop Down List #8299

3Deee opened this issue Sep 2, 2020 · 3 comments
Labels
Type: Improvement Improvement to existing functionality.

Comments

@3Deee
Copy link

3Deee commented Sep 2, 2020

Application version
4.7

Platform
Mac IOS

Printer
Ender 5

Reproduction steps
From the Properties menu >> Material > [Material Type] is an editable, type-in entry field. Print Profiles are linked to this field. Profiles appear when [Material Type] is recognized. Profiles do not appear when [Material Type] is not recognized. Examples: When "PLA" is entered, all Profiles appear. When something else is entered, say "PLA Performance" which has slightly different material properties, Profiles do not appear. PLA Performance is a Keene Village filament. Changing [Material Type] field to a pull down list of acceptable entries would alleviate issue.

Screenshot(s)
(Image showing the problem, perhaps before/after images.)

Actual results
(see above)

Expected results
(What should happen after the above steps have been followed.)

Project file
(For slicing bugs, provide a project which clearly shows the bug, by going to File->Save. For big files you may need to use WeTransfer or similar file sharing sites.)

Log file
(See https://github.com/Ultimaker/Cura#logging-issues to find the log file to upload, or copy a relevant snippet from it.)

Additional information
(Extra information relevant to the issue.)

@3Deee 3Deee added the Type: Bug The code does not produce the intended behavior. label Sep 2, 2020
@3Deee
Copy link
Author

3Deee commented Sep 2, 2020

I came across problem and resolved it before reading other strings. Others suggested same solution. They must have a great mind too. (just kidding).

@Ghostkeeper
Copy link
Collaborator

We already have this on our backlog, arising from this issue: #8229

Good to have a separate ticket about it I guess. But if we fix this then we should also consider the original fixed.

@Ghostkeeper Ghostkeeper added Category: Cura Type: Improvement Improvement to existing functionality. and removed Type: Bug The code does not produce the intended behavior. labels Sep 3, 2020
@RaabenF
Copy link

RaabenF commented Sep 3, 2020

thank you for clarification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Improvement Improvement to existing functionality.
Projects
None yet
Development

No branches or pull requests

4 participants