Squish는 현재 커뮤니티 에디션을 제공하지 않으며, 공식적으로 10일간의 무료 평가판만 제공하는 것으로 알고 있습니다.

평가판 사용 후에는 정식 라이선스를 구매해야 계속 사용할 수 있습니다.

만약 무료로 사용할 수 있는 GUI 테스트 자동화 도구를 찾고 계시다면, 다음과 같은 오픈 소스 대안을 고려해보실 수 있습니다:

Selenium : 웹 애플리케이션의 GUI 테스트 자동화를 위한 도구로, 다양한 언어와 플랫폼을 지원합니다. PyAutoGUI : Python으로 GUI 테스트를 자동화할 수 있는 간단한 도구로, 마우스와 키보드 조작을 스크립트로 작성할 수 있습니다. AutoIt : Windows 환경에서 GUI 테스트 자동화를 지원하는 스크립트 언어로, 간단한 스크립트로 복잡한 GUI 작업을 자동화할 수 있습니다.

Qt 6.5.3에서 Qt PDF 모듈을 사용하려면 몇 가지 확인해야 할 사항이 있습니다. 아래 단계에 따라 문제를 해결해보세요. 1. Qt PDF 모듈 설치 확인

Qt PDF 모듈이 제대로 설치되었는지 확인하세요.

확인 방법:

Qt Maintenance Tool 실행 (C:\Qt\MaintenanceTool.exe) 패키지 추가 또는 제거 선택 Qt 6.5.3 -> Additional Libraries에서 Qt PDF 모듈이 설치되었는지 확인

설치되지 않았다면 체크 후 설치하세요.

2. MinGW용 Qt PDF 지원 여부 확인

Qt PDF는 MSVC 컴파일러에서는 제공되지만, MinGW용 Qt 빌드에서는 지원되지 않을 가능성이 높습니다.
즉, MinGW 11.2.0 환경에서는 Qt PDF를 사용할 수 없을 수 있습니다.

해결 방법:

MSVC 2019 또는 MSVC 2022 환경에서 Qt 6.5.3을 설치한 후 다시 빌드해보세요. 만약 MinGW 환경을 유지하고 싶다면, Qt PDF 소스를 직접 빌드해야 합니다. 3. qmake 및 CMake에서 PDF 모듈 추가 방법

qmake 환경에서 .pro 파일에 아래 내용을 추가하세요.

QT += pdf

그리고 나서 아래 명령어를 실행하여 프로젝트를 다시 설정합니다.

qmake -r mingw32-make clean mingw32-make

CMake를 사용하는 경우 CMakeLists.txt에서 다음을 추가해야 합니다.

find_package(Qt6 COMPONENTS Pdf REQUIRED) target_link_libraries(MyApp PRIVATE Qt6::Pdf) 4. PDF 모듈 직접 빌드 (MinGW 사용 시)

MinGW 환경에서 Qt PDF를 사용하려면 소스를 직접 빌드해야 합니다.

빌드 방법:

Qt PDF 소스를 다운로드:git clone https://code.qt.io/qt/qtpdf.git cd qtpdf CMake를 사용하여 빌드:mkdir build cd build cmake .. -G "MinGW Makefiles" -DCMAKE_INSTALL_PREFIX=C:/Qt/6.5.3/mingw_64 mingw32-make mingw32-make install 프로젝트에서 QT += pdf 추가 후 다시 빌드 5. 최종 점검 Qt PDF가 MinGW에서는 공식 지원되지 않음을 염두에 두세요. 가능하면 MSVC 2019/2022로 변경하여 사용하세요. MinGW에서 사용하려면 직접 빌드해야 합니다.

Sorry to say, but the issue is in your code, not in Qt.
It occurs, when a model is called with a QModelIndex from another model.
That can happen either, when there the wrong model is called, or when the index is mal-constructed.
Please boil the problem down to a minmal, cmplilable reproducer. Just showing the App architecture is helpful but not sufficient. Please post the minimal reproducer here, using code tags.

Hi, many thanks for your response,

Most probably not, I haven't done any particular setup for that.

But I'm guessing if I want to use the app in different devices I would have to setup openssl separately?

Would it be better to download the font and set it as a project resource somehow?

Many thanks for your help.

Hi,

Without knowing which Qt version, which OS, how you set things up, it's pretty much impossible to know what is going on.

AFAIK, Qt would use the C++ api for that task.

Hi,

Why are you calling planet->trailPath.moveTo(0, 0); for every "non-initial value" ?

Hi,

The first I would do is remove the stylesheet to ensure you have everything showing properly.
Then I would add things back to it.

Do you have cmake installed ?
If yes, how and where ?
If no, then install it.
Next, go to its configuration pane and point it to the one you installed.

When you block the event loop - how should the ui be redrawn? Use the canceld() signal and don't block the event loop...

@jeremy_k - thanks for that clarification.
I ended up defining runTest() as follows:

INVOKABLE QList<QVector2D> TopoDataItem::runTest(void ) { QList<QVector2D> profile; // Add content to profile [...] return profile; }

The QML invokes the method as follows:

Button { text: qsTr('run test') onPressed: { var profile = topoDataItem.runTest(); // Do stuff with profile data [...] } }

This seems to work with my application, without need to register additional stuff with the metatype system.

Hi @OlivierD
You can use colorsemantic using the addAttribute(....) to define a color for each face , iirc just make sure that in the model Material you set

lighting: DefaultMaterial.NoLighting

@Groundbounce Better to show some code about how Property is applied.

Some progress but still having some problems:

if(NOT LINUX) set (deploy_tool_options_arg "") if(APPLE) set(deploy_tool_options_arg "${deploy_tool_options_arg} -hardened-runtime") elseif(WIN32) set(deploy_tool_options_arg "${deploy_tool_options_arg} --pdb") endif() # Generate a deployment script to be executed at install time # App bundles on macOS have an .app suffix if(APPLE) set(executable_path "${CMAKE_CURRENT_BINARY_DIR}/$<TARGET_FILE_NAME:DeepSkyStacker>.app") else() message ("Target filename:" $<TARGET_FILE_NAME:DeepSkyStacker>) set(executable_path "${CMAKE_CURRENT_BINARY_DIR}/$<TARGET_FILE_NAME:DeepSkyStacker>") endif() message ("executable_path: " ${executable_path}) message ("deploy tools options arg: " ${deploy_tool_options_arg}) qt_generate_deploy_script( TARGET DeepSkyStacker OUTPUT_SCRIPT deploy_script CONTENT " qt_deploy_runtime_dependencies( EXECUTABLE \"${executable_path}\" DEPLOY_TOOL_OPTIONS ${deploy_tool_options_arg} )" ) else() qt_generate_deploy_app_script( TARGET ${PROJECT_NAME} OUTPUT_SCRIPT deploy_script DEPLOY_TOOL_OPTIONS ${deploy_tool_options_arg} ) endif() install (SCRIPT ${deploy_script}) install(TARGETS ${PROJECT_NAME} BUNDLE DESTINATION .)

gets me this:

[226/227] Install the project... -- Install configuration: "Debug" -- Running Qt deploy tool for /Users/amonra/.vs/DSS/out/build/DeepSkyStacker/DeepSkyStacker.app in working directory '/Users/amonra/.vs/DSS/Darwin/arm64/Debug' '/opt/Qt/6.8.2/macos/bin/macdeployqt' '/Users/amonra/.vs/DSS/out/build/DeepSkyStacker/DeepSkyStacker.app' '-appstore-compliant' '-always-overwrite' '-hardened-runtime' -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/MacOS -- Installing: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/MacOS/DeepSkyStacker -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/PlugIns -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/PlugIns/platforminputcontexts -- Installing: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/PlugIns/platforminputcontexts/libqtvirtualkeyboardplugin.dylib : : -- Installing: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/Frameworks/QtQmlModels.framework/Versions/A/QtQmlModels -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/Frameworks/QtQmlModels.framework/Versions/A/Resources -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/Frameworks/QtQmlModels.framework/Versions/A/Resources/PrivacyInfo.xcprivacy -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/Frameworks/QtQmlModels.framework/Versions/A/Resources/Info.plist -- Up-to-date: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/Frameworks/QtQmlModels.framework/Versions/Current error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: for: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/MacOS/DeepSkyStacker (for architecture arm64) option "-add_rpath @executable_path/../Frameworks" would duplicate path, file already has LC_RPATH for: @executable_path/../Frameworks error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: no LC_RPATH load command with path: /opt/Qt/6.8.2/macos/lib found in: /Users/amonra/.vs/DSS/Darwin/arm64/Debug/./DeepSkyStacker.app/Contents/MacOS/DeepSkyStacker (for architecture arm64), required for specified option "-delete_rpath /opt/Qt/6.8.2/macos/lib"

So, I think I'm almost there, but still missing something critical.

@vinadenenko
Discussed at https://lists.qt-project.org/pipermail/interest/2022-September/038483.html as a Qt6 change/issue.
I believe the solution there is "The recommended approach is to explicitly use a corresponding QFuture<void> constructor"?
Yes, see https://doc.qt.io/qt-6/qtcore-changes-qt6.html#implicit-conversions-between-qfuture-and-other-types in the docs.