Hi @lasselauch there is actually no plan to update ResEdit. There is the R20 Resource Editor but for the moment it's only for Node stuff. Cheers, Maxime.

Hi @dskeith thanks for reaching out us. As pointed out by @PluginStudent, the NBIT_SOLO_LAYER behavior is explained in the Layer Manuel although it make sense to add a note to the Python API as well. With regard to a complete example, I've partially reworked your code to make sure that by executing the script multiple times you can run across all the solo configurations that the scene can handle. import c4d # Main function def main(): layer_root = doc.GetLayerObjectRoot() if not layer_root: return # Get the first layer in the scene layer = layer_root.GetDown() if not layer: return soloSet = False while layer is not None: # Set `rawdata` to True flag so to get the original layer values without any additional global changes layer_data = layer.GetLayerData(doc, rawdata=True) # check the current layer solo state: if layer_data["solo"] == False: # if not "solo" then set to True layer_data["solo"] = True # update the layer layer.SetLayerData(doc, layer_data) # update the flag soloSet = True break # deactivate if layer solo was True layer_data["solo"] = False layer.SetLayerData(doc, layer_data) # go to next layer layer = layer.GetNext() # if one (or more) solo was set the set NBIT_SOLO_LAYER otherwise clear if soloSet == True: doc.ChangeNBit(c4d.NBIT_SOLO_LAYER, c4d.NBITCONTROL_SET) else: doc.ChangeNBit(c4d.NBIT_SOLO_LAYER, c4d.NBITCONTROL_CLEAR) # Add an event c4d.EventAdd() # Execute main() if __name__=='__main__': main() Cheers

spam frenzy all over again, lately.

Hello, which tool do you actually want to configure? best wishes, Sebastian

Hi Daniel, thanks for sharing your further considerations. I see your points and maybe we should consider to update our documentation to reflect the notes above. I will discuss with the team and maybe we could come with a better introduction where the "plugin" term is used in a less generic meaning. Cheers, Riccardo

Thanks Riccardo, It all (well, some of it) starts to make sense after your explanation. A big step forward in starting to understand how to proceed with the MAXON API.

Hi CMPX, thanks very much for the comment. It's definitively something helpful we'd consider to add in the future. Best, Riccardo

Hi, thanks for the additional feedback. Please keep the discussion going, as we are late as always, the "feedback window" is not closed, yet. Well, I doubt it should ever be closed, we are always interested in your feedback. It's just the our first round of feedback evaluation, that was supposed to end end of November. So, please go ahead and pull more community members into the discussion. We'd really like to get some more opinions and feedback, especially when approaching such topics as reorganizing the category structure. The breadcrumbs idea is nice. And as soon as we have fixed the problem of users not being able to mark posts (not only entire threads) as correct answer, we'll also discuss about making threads questions by default. Cheers, Andreas

Hi Mike, please check this thread to properly use the Q&A functionality. Cheers, Riccardo

Hi Donovan, thanks for your feedback. Currently we are bound mostly by DevKitchen preparations. But we promise to get back to this issue and think about other options as soon as we find the time. Until then: If you click on the "unread message queue", there in the top right you have commands to mark messages as read, either all or just for certain categories. Maybe this can at least ease your pain, until we find the time to address the issue. Bye, Andreas