Topics created by a_block

Thanks for the offer. much appreciated. But your explanations were good and plenty as usual.
I think, I know exactly what is going on.

No worries. Thanks for trying. 🙂

Thanks, Ferdinand. I'll take a closer look as soon as I find the time.

Hi Maxime,
that's a bummer.

Just a few additions:

is done by calling HandleMouseDrag. Your code is paused until the drag operation ended

Yes, no objection. But it should be said, during this "pause" one does still receive messages, among them BFM_DRAGRECEIVE_START and BFM_DRAGRECEIVE. Just not BFM_DRAGEND. Which makes me think, if only the receiver would not "consume" this message, it could already work...

From a pure implementation point of view, it also does make sense since it would make no sense if each drag operation have to support all possible managers

I wouldn't want it differently. But I still think, the initiator of an action deserves result information. after all these years, I'm still wondering, what's this obsession with not delivering feedback to a caller. Yes, I'm looking at you CallCommand()...

Finally it is not possible to drag objects directly to the viewport

I didn't even consider, drag and drop could work differently for materials and objects, or objects not working at all. So, thanks for the info and avoiding even more headache on my end.

I guess, we are back to the drawing board then.

Anyway, greetings to the team.
Cheers,
Andreas

Hi Ferdinand,
thanks a lot!
No ETA needed, I'm grateful it will be added eventually.
Cheers,
Andreas

Hello @a_block,

Thank you for reaching out to us and pointing out these flaws. We are aware of these changes but since it was for quite some time unclear if these changes were intentional or not, we postponed documenting them. The changes to the look and functionalities of GeDialog borders will be included in an upcoming documentation. But since these changes effectively demand symbols or even function arguments to be deprecated, this would be more a developer's task than a documentation task.

I can of course put a note into the documentation, but this would only be a band aid. I will try to find a clean solution by poking the relevant devs.

Cheers,
Ferdinand

Hello @a_block ,

we have removed the restriction of having to add at least one tag to postings in the General Tak forum, allowing for more open-ended and broader questions in this forum.

The tagging restrictions for all other forums remain.

Cheers,
Ferdinand

Ah, damn, I forgot that Python doesn't have SceneHookData. Sorry.

Hi Ferdinand,
thanks for your thorough and detailed reply.

The problem is, I need to put the correct name of the rendered output into a text file. This needs to match, when rendered later on. So, just guessing something similar is also not an option.

I already anticipated, there would be no easy solution.

By the way, even if I had the time to test render 1x1 images, it would still not be ok, there are resolution tokens...

I will most likely reduce the amount of freedom the user has here, in order to end with something deterministic.
Thanks for your help and ideas. You can consider this topic closed from my side.

Cheers to the entire SDK Team,
Andreas

Sorry, for causing extra work

Hi Ferdinand,
thanks for the quick and detailed answer, even trying to find workarounds. I had hoped, I could spare you this extra effort by saying, that it's no functional issue on my end.

I am already satisfied with the confirmation. Often it is enough to be able to stop worrying about my own mental integrity.
And while this new behavior certainly will not improve performance, I can happily ignore performance issues beyond my own responsibility.

Regarding the GeDialog stuff: No worries, either. As mentioned back then, no future fix/solution can help me there and I went down a different route to get the project done with support for R19 to present. Yet, I'm thankful for your tenacity and that the issue is still being researched. Some meals simply need time to develop their flavours.

Thanks and cheers,
Andreas

Hey Andreas,

no need to feel sorry. It is valuable for us to be aware of this, as this could cause more serious problems further down the road, even though it is hard to reproduce for now. We have pushed this off to QA for now, due to them having the required tools (hardware) to assess this more thoroughly.

I do not see anything inherently wrong with that. But the only ones who could answer this with complete certainty are the developers who wrote the Cinema 4D core. And until we cannot say with a reasonable degree of certainty that this is a reproduceable bug that we want to address, I will not bother them with this, since there is other "stuff" in front of the queue for them anyway.

I have forked your second part of the question, as I would like to keep this thread clean, as I would anticipate that QA will confirm this bug, it then going to the developers, and we will then report back here. Which will get a bit convoluted when there is a second question being discussed here. The topic can be found here.

I understand that this is not the most satisfying procedure for you, as it will take a bit of time. The issue of yours must go through our bug tracking system now first, rather than taking the shortcut we sometimes offer here, of us talking with the developers and then creating an issue if we decide to do so.

Cheers,
Ferdinand

Hi Ferdinand,

thanks for the confirmation and looking into it.

While it's a bit unfortunate, I do not consider this a major road block. From my side this thread can be considered close.

Cheers

Hi Ferdinand,
right, no worries. I am aware, "Question/Solution" is realized by a plugin and didn't expect it to be an easy fix. To have it documented is a good solution. Personally the topic here was more a kind of personal conditioning for me. Now, that I wrote about it, I won't forget so easily...
Cheers

i removed the ids from the sdk. it looks like they are only used internally. there is no use in the sdk for developers.

Given my own blind spots on flags and GetAllTexturesNew() I was actually quite glad, you hadn't had the time to look into it. Unfortunately I was obviously too late to stop you from investing time nevertheless... Sorry.

Which then will turn a bit into a data structure/similarity problem when you want to group your textures into nice packages.
Yeah, this, plus my concerns below.

Regarding running over the project's frame range: Especially character animators seem to have a habit of storing information outside the project's frame range. That's where I'm afraid to loose information. Or I would need to establish additional means to figure out such frames. I doubt document's GetMin/MaxTime() help here. So it would be iterating over all tracks in a document I guess.

And you are right, you shouldn't spend additional time on this. Given the result of my other current thread, everything in this thread really is the least of my problems.

Somehow I have a "Händchen" (I guess, one would save, I have a knack for) for maneuvering myself in these situations...

Thank you Andreas for closing it.

Cheers,
Ferdinand

Oh, my bad then. Will update immediately, which I should have probably done before posting to the public forum. I'd say, if you can, please remove this thread, so nobody gets confused.

And don't worry about InitValues().

Cheers

Hi Maxime,

thanks for the answer and verifying what I had thought. Indeed I would need it in Animation mode and especially for the case where user highlighted multiple poses at once.

I had seen that thread, but it did not contain a definitive confirmation from Maxon. Maybe the thread I was thinking of was in a different forum.

Anyway, good to have your confirmation, now. And not possible only means I can stop wasting time looking around and instead need to implement another workflow for the user. Maybe not as slick as with the selection info, but no show stopper either.

Cheers,
Andreas