why do you think C4D has any special handling for emojis? The font rendering is OS dependent, so any kind of text - including emoji codepoints - is drawn by the underlying operating system routines. Anything else would mean a ridiculous effort by Maxon to replicate font behavior. (I do not know how Windows internally handles emojis, I doubt that every available font has all these characters so most likely certain codepoints are mapped to common glyphs regardless of the font... but that is not a C4D question anyway.)

I’m confident they will find out ;-) Thanks for everything!

OK, thanks!

Hmmmm, well, on the one hand this function is a nice thing: It really does do the escaping for me, so the spaces in the URL are correctly replaced with "%20". But it does not handle anchors in a URL. This URL works fine: file:///Applications/Maxon/Cinema 4D R22/plugins/myplugin/help/content/omyobject/omyobject.html But this URL is not opened, instead an error (code -43) is thrown: file:///Applications/Maxon/Cinema 4D R22/plugins/myplugin/help/content/omyobject/omyobject.html#MYOBJECT_ATTRIBUTE That is a pity.

hi, this is the current state: "I think this is related to the ASYNC_POPUPEDIT being a non-resizable, modal dialog - and as such it is displayed kind of "Win legacy style" by the OS. Nothing we actively do set (and something which could change once they do further design overhauls in Win10)" Cheers, Manuel

Always using the threadIndex, of course :-) Thanks, I'll try that!

Ah, great, thank for checking! Then I don't need to worry about my bmp code :-) Cheers, Frank

arff, that's really strange, I'll send you a simple example and see if the error still happen on your system.

Hi @JuicyJuggles , I apologize for coming late here but luckly you've been already provided in the meanwhile of some good guidance from @PluginStudent and @zipit . Rest assured that the API documentation is, by far, the best place where to look for answers although I can see that, due to huge number of covered topics, it could take time to get used to browse it effectively. Last but not least, if the issue is addressed, don't forget to mark the right post as correct answer or if it's not possible to identify a specific one, to set the whole topic as Solved Cheers, Riccardo

Hello to all @zipit said in GetFontDescription() on Windows and Mac: FONT_FLAGS Thank you i miss flags in https://plugincafe.maxon.net/post/58961

Thanks a lot! That helps :-) Cheers, Frank

Oh man, it really was the missing message. Never thought it would have such weird consequences to forget that. Thanks guys!

Thank you! That does it exactly!

@r_gigante @kbar Thanks for the infomation. I assumed that was the case and it makes sense, I'm just reluctant to stop supporting older versions of Cinema but it might be time. Riccardo, I think I was using the incorrect version of osX or XCode, not sure which, but using your codesign worked when I moved onto a later version of both and it is correctly signing my R20 compiles. Thanks both of you for all of the help and clarifying of notarization. Dan

Thanks for the update Frank. Looking at your "resolutions" I think that the actions you took were responsible, in the first case, to clean the existing derived data for the R20 project, whilst in the second, to refresh the DerivedData subfolder where the newly re-created R21 project was supposed to store intermediate files. Please keep us updated and for the mean time I'm going to set this thread as solved. Cheers

I think we are talking past each other. You can of course build any project any way you like. An then make sure that your plugins link to the build result using the link options defined in projectdefinition.txt. But I think you want to include an already existing (non-plugin) project in the solution created by the Project Tool, right? And I think that is not possible. I guess you could add the project manually to the solution created by the Project Tool.

OK, thank you!

Ok, thanks @r_gigante... I'll keeping going with the workaround.