Author: cvo | Asked: 3 months 15 days 2 hours 4 minutes ago | Viewed: 67 times | Activity: 3 months 13 days 13 hours 6 minutes ago |
0 |
Hello, I discovered your framework the other day and decided to give it a try. I downloaded the last source code, loaded nitisa.sln with VS2022, chose debug and x86 as configuration options, and performed the build, however I had some errors: * error : The BaseOutputPath/OutputPath property is not set for project 'NTL.vcxproj'. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration='Debug' Platform='Win32'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform. * The BaseOutputPath/OutputPath property is not set for project 'Nitisa.vcxproj'... * error : The BaseOutputPath/OutputPath property is not set for project 'Png.vcxproj'.... * error : The BaseOutputPath/OutputPath property is not set for project 'Standard.vcxproj'... * error : The BaseOutputPath/OutputPath property is not set for project 'Platform.vcxproj'. * error : The BaseOutputPath/OutputPath property is not set for project 'Extended.vcxproj'... * error : The BaseOutputPath/OutputPath property is not set for project 'Ide.vcxproj'.... * error : The BaseOutputPath/OutputPath property is not set for project 'Charts.vcxproj'.... and so on. 1) Could you help in fixing those errors? I take this opportunity to set a couple of additional questions: 2) are the controls native ones? Or are they rendered totally with opengl? 3) How do you handle text rendering for non-western scripts? Is it platform dependent? Or do you use third party solutions (harfbuzz, icu, freetype)? Thanks (sorry I tried to give my comment a decent layout for readability purpose but I wasn't able)
|
0 |
Answered by Support at Aug 19, 2024, 3:35:30 PM 1) We could not reproduce the issue. Perhaps you can try to set BaseOutputPath/OutputPath as the error message suggests. 2) All controls are rendered using OpenGL, no native controls are being used. 3) We use Windows API on windows and FreeType on other platforms for text rendering but support of non-western texts is only in future plans. |
0 |
Answered by cvo at Aug 19, 2024, 11:19:53 PM Hi, Thanks for the answers. I got this error: >Nitisa-15.0.0\Packages\Platform\OpenGL\dgl.cpp(15,63): error C1001: > Internal compiler error. while compiling the *Platform* project. I use Debug/x86 as confingurations and VS2022 community edition with C++ 14 and PlatformSet 143. Any sugggestion to fix it? Thanks EDIT: I saw you reply on the other comment that is equal to my last one. I could fix it using traditional initialization instead of the brackets one. I built again the entire solution and only one project weren't compiled and built: Package.CoolWidgets. The reasons, I suspect, is related to the only config available, DebugRT, while I build the entire solution with Debug&x86. I don't know if that is right or an error however. |
0 |
Answered by cvo at Aug 20, 2024, 9:04:34 PM Hi, This is going to be an update of my experience with Nitisa source. I chose DebugRT | x86 and everything compiles fine with VS2022 under Windows 10. I could run also the examples programs and test them. There is still work to do especially on the text side, you could see it on FontExplorer program for example, but what you have done is impressive. This framework is what I was looking for since I didn't want to follow the cool GUI framework Microsoft creates every day. I will give the Nitisa extension a try and create a program based on Nitisa framework to see if I can use it in production. i couldn't find another C++ GUI framework not based on GDI. Nitisa still requires improvments, but well congratulations. Possible improvments: text rendering, non-western languages rendering and manegement, different backend renders (e.g. vulkan, DX, apple's etc). |