qt-labs / vstools

Other
77 stars 24 forks source link

Can't open existing .pro project #8

Closed caxapexac closed 1 year ago

caxapexac commented 1 year ago

Describe the bug Opening .pro files doesn't work (Can't see any error logs)

To Reproduce Steps to reproduce the behavior:

  1. Go to Extensions->QtVsTools->Open qt project file
  2. Select .pro file inside my project
  3. ...
  4. Nothing happens

Expected behavior At least some logs

Screenshots image

Desktop (please complete the following information):

.pro

QT       += core gui sql printsupport axcontainer

greaterThan(QT_MAJOR_VERSION, 4): QT += widgets

CONFIG += c++17
#CONFIG += qwt

# You can make your code fail to compile if it uses deprecated APIs.
# In order to do so, uncomment the following line.
#DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000    # disables all the APIs deprecated before Qt 6.0.0

SOURCES += \
    main.cpp \
    mainwindow.cpp \
    numroom.cpp \
    pdf_cr.cpp \
    pdf_materials.cpp \
    adress.cpp \
    renderer/windowgraphicsview.cpp \
    room.cpp \
    spritecursor.cpp \
    windowsize2d.cpp \
    windowsize3d.cpp \
    changes.cpp \
    finaldimensions.cpp \
    form_window.cpp

HEADERS += \
    adress.h \
    changes.h \
    finaldimensions.h \
    form_window.h \
    mainwindow.h \
    numroom.h \
    pdf_cr.h \
    pdf_materials.h \
    renderer/windowgraphicsview.h \
    room.h \
    spritecursor.h \
    windowsize2d.h \
    windowsize3d.h

FORMS += \
    adress.ui \
    changes.ui \
    finaldimensions.ui \
    form_window.ui \
    mainwindow.ui \
    numroom.ui \
    pdf_cr.ui \
    pdf_materials.ui \
    room.ui \
    windowsize2d.ui \
    windowsize3d.ui

# Default rules for deployment.
qnx: target.path = /tmp/$${TARGET}/bin
else: unix:!android: target.path = /opt/$${TARGET}/bin
!isEmpty(target.path): INSTALLS += target

RESOURCES += \
    img.qrc

P.S. Creation of the new qt project works properly

P.P.S. image Qt version is set

kaheimri commented 1 year ago

Many thanks for reporting the issue @caxapexac. The progress of the reported bug is tracked here: https://bugreports.qt.io/browse/QTVSADDINBUG-1091 Please head over to our own issue tracker if you want to comment or add some more information on the issue.