5axes / nameit Goto Github PK

Thank you, this extension makes our workflow so much more productive!

Feature Request - Is it possible to engrave/deboss the letters rather than have them embossed? Something like a negative text height?

Reason - The Name It ID's usually get placed on our rafts. If the ID was engraved into the raft, it would be completed before the actual part and have zero impact on the actual print in terms of travels away from the print and the potential for stringing. We also print our first layers very thin with adaptive layer height for curvature and detail reasons. It would be nice if the text was engraved into the thick and robust raft layers rather than embossed with the thin and wispy wall settings of a detailed part.

steps to reproduce:

• select object
• extensions - name it - add number
• extensions - name it - add name

Every other following adding of a number or name ID's or Names the previous identifiers as well.
I can imagine a usecase that requires both number and name, but not multiple uses of name AND id.
Might be cleaner to use it as a toggle. 'name' adds or removes the name of the file. 'id' adds or removes the id.

When adding the new nodes that contain the text, they are added as individual items in the "undo / redo" stack. So if you add the name to 5 items at once, you have to undo it 5 times to get back to the same result.

Since this is the result of a single user action (The user pressed a single button), it would make more sense to me to have a single undo result in all of the names being removed.

You can do this by creating a single "GroupedOperation" and add all the other operations to that operation. Only the GroupedOperation needs to be pushed to the OperationStack.

In a futur release, possibility of enhancement: add optional prefix and suffix to the number identification

Hi @5axes !

We (UltiMaker, or the Cura team at least) wanted to send an update w.r.t. the new SDK, but the email address ([email protected]) you've listed in the plugin(submission form)s bounces.

Cheers!

To avoid re-sending it, I've also listed it here:

Dear Cura-plugin Contributor,

This mail is to inform you that, for the upcoming Cura version (5.2.x), we're bumping the SDK/API version to '8.2.0' (was '8.1.0').

You were sent this mail because this mail-address was given to us as the correspondence address on at least one currently active Cura plugin.

Since this is a minor increase, there shouldn't be any breaking changes. Nevertheless, you may want to update, depending on whether the added classes or updated function signatures (added optional parameters or type-checking) are of use to your plugin.

Publicly available added classes and changed functions in Uranium and Cura since 5.1.1 are:

cura/Machines/Models/CompatibleMachineModel.py
<new class>

cura/API/Account.py
+    permissionsChanged = pyqtSignal()
+    def permissions(self) -> List[str]:

cura/Machines/Models/GlobalStacksModel.py
+    def setFilterAbstractMachines(self, new_filter: Optional[bool]) -> None:
+    def filterAbstractMachines(self) -> Optional[bool]:

cura/PrinterOutput/Models/PrintJobOutputModel.py
+    def isMine(self) -> bool:

cura/Settings/CuraStackBuilder.py
+    def createUserContainer(cls, new_stack_id: str, definition: DefinitionContainerInterface,stack: GlobalStack,
                            variant_container: "InstanceContainer",
                            material_container: "InstanceContainer",
                            quality_container: "InstanceContainer"):
+    def createAbstractMachine(cls, definition_id: str) -> Optional[GlobalStack]:

cura/Settings/GlobalStack.py
+    def hasNetworkedConnection(self) -> bool:

cura/Settings/MachineManager.py
+    def getMachinesWithDefinition(self, definition_id: str, online_only=False) -> List[ContainerStack]:
+    def activeMachineIsAbstractCloudPrinter(self) -> bool:

cura/resources/qml/Dialogs/ChoosePrinterDialog.qml
<new class>

cura/resources/qml/PrinterSelector/MachineListButton.qml
<new class>

cura/resources/qml/PrinterSelector/PrintSelectorCard.qml
<new class>

cura/resources/qml/Menus/Configurationmenu/CustomConfiguration.qml
Removed printerTypeSelectorRow and all sub-items

cura/resources/qml/PrintSetupSelector/Recommended/RecommendedInfillDensitySelector.qml
Added property ignoreValueChange to infillSlider item

UM/Settings/InstanceContainer.py
+    def createMergedInstanceContainer(cls, instance_container1: "InstanceContainer",instance_container2: "InstanceContainer") -> "InstanceContainer":

newly deprecated in 5.2 (these will be removed at some point in the future):
* cura/API/Account.py
  "Get permissions from the 'permissions' property"
  def updateAdditionalRight(self, **kwargs) -> None:
* cura/API/Account.py
  "Get permissions from the 'permissions' property"
  def additionalRights(self) -> Dict[str, Any]:
* UM/Qt/QtApplication.py
  "Showing toast messages is no longer supported"
  def showToastMessage(self, title: str, message: str) -> None:

Discussed in #10

When Trying to add the part name, NameIT only uses the bodynames instead.

Should be Line 5 mount, but only shows up as bodies

It's a know "issue" . The function in case of Group , generate the names of each individual element .

Issue / Not Issue ?

It would be awesome if this could print the first X characters of the file name, or custom labels that could be input manually.

Added a custom setting with an "Initial layer speed" dedicated to printing letters.

Add the possibility to select different Font 👍🏻

#8

Can us a dropdown list in sthe settings ?

Hi, I cannot find the plugin either on the Ultimaker marketplace or from the install instance of Cura 5.1. Even if I search in all plugins from "5axes". Is it normal ?

Discussed in #18

Currently the plugin converts all the names in capital letters. This is normal because I think that the letters are easier to print in this case (example of i and j which in capital letters has no dot) .

But some feedback are expected on this point. Could be in a futur release integrated as an option in the settings of the plugin.

Originally posted by @5axes in #2

Not sure if this is even possible since 'multiply' of objects is a cura feature.
If you currently multiply an ID'd object, the copies have the same ID, but do get the new object name 'object (2).stl'

'fixing' this might need an extra look at what happens when an ID is already in use for that object
(for example; object.stl ID1, object(1).stl ID2 and creating a copy of object.stl... that would create an object(2).stl but would the ID be 2 or 3?)