New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
status bar #5
Comments
please take a look at the readme - you must include this from JP Numris project |
Thanks. Got it.
…On Mon, Nov 11, 2019 at 1:27 PM ekke ***@***.***> wrote:
please take a look at the readme - you must include this from JP Numris
project
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AHIREUGEJLBGHGQQA4WM5UDQTFMTXA5CNFSM4JLUPKR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDW2KMQ#issuecomment-552445234>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHIREUEVPI6VVU4G2RRCCETQTFMTXANCNFSM4JLUPKRQ>
.
--
Ricardo Santos
|
dear ekke
I found the following issues running the code in Qt
1º include <statusbar.h> i had to replace by include "statusbar.h"
2º I think that there is a problem with the name of 2 images, whose entry i
had to delete from images.qrc :
white/schedule_list@"x.png
black/search@“x.png
I still have this warnings
Warning: QML import could not be resolved in any of the import paths:
org.ekkescorner.data
Warning: QML import could not be resolved in any of the import paths:
StatusBar
Warning: QML import could not be resolved in any of the import paths:
QtQuick.Controls.Material.impl
Warning: QML import could not be resolved in any of the import paths:
QtQuick.Controls.impl
Warning: QML import could not be resolved in any of the import paths:
QtQuick.Controls.Fusion.impl
Warning: QML import could not be resolved in any of the import paths:
QtQuick.Controls.Imagine.impl
Warning: QML import could not be resolved in any of the import paths:
QtQuick.Controls.Universal.impl
Do you know why these warnings appear? Are they harmful?
thanks
On Mon, Nov 11, 2019 at 3:08 PM Ricardo Santos <ricardos.geral@gmail.com>
wrote:
… Thanks. Got it.
On Mon, Nov 11, 2019 at 1:27 PM ekke ***@***.***> wrote:
> please take a look at the readme - you must include this from JP Numris
> project
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <#5?email_source=notifications&email_token=AHIREUGEJLBGHGQQA4WM5UDQTFMTXA5CNFSM4JLUPKR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDW2KMQ#issuecomment-552445234>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AHIREUEVPI6VVU4G2RRCCETQTFMTXANCNFSM4JLUPKRQ>
> .
>
--
Ricardo Santos
--
Ricardo Santos
|
with the images you're right. the warnings are an old issue: https://bugreports.qt.io/browse/QTBUG-47389 the statusbar: I'm using the statusbar in all my projects. so I cloned the statusbar project outside my conf app project at the sam level and then included. probably you have copied something inside the project ? |
You are right. I've messed the statusbar folder. It's working now. Thanks.
…On Mon, 11 Nov 2019, 20:27 ekke, ***@***.***> wrote:
with the images you're right.
the warnings are an old issue: https://bugreports.qt.io/browse/QTBUG-47389
the statusbar: I'm using the statusbar in all my projects. so I cloned the
statusbar project outside my conf app project at the sam level and then
included. probably you have copied something inside the project ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5?email_source=notifications&email_token=AHIREUHPFGR55PNOEJAVK2DQTG52LA5CNFSM4JLUPKR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDYAMWY#issuecomment-552601179>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHIREUEHYRT75SJYOHMPV5LQTG52LANCNFSM4JLUPKRQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi ekke
nice work
this is missing no?
include(../statusbar/src/statusbar.pri)
thanks
The text was updated successfully, but these errors were encountered: