https://codereview.qt-project.org/#/c/214045/ was merged. dev is fixed now.
— Liang
> On 11 Dec 2017, at 12:22, Liang Qi wrote:
>
> dev is blocked by "Module "" () Failed to provision template
> 'qtci-osx-10.11-x86_64-3-9946c2’:” issue, should be fixed by following change:
> https://codereview
Hi,
Afaik the fix was applied to 5.9 and 5.10 branches, whereas your change targets
dev. Restaging will not help at the moment.
On Dec 12, 2017, at 19:38, Stottlemyer, Brett (B.S.)
mailto:bstot...@ford.com>> wrote:
Hi list,
I saw some traffic on QtBase showing the above error staging from Ger
Hi list,
I saw some traffic on QtBase showing the above error staging from Gerrit (which
I thought was fixed). I'm seeing the same thing on the Qt Remote Objects
module. Is this expected? Is there anything trick other than retry?
The specific change is https://codereview.qt-project.org/#/c/2
This was apparently the result of a miscommunication and no force
pushing is contemplated.
On 12/12/2017 01:24 PM, Tuukka Turunen wrote:
Hi,
Force pushing of what? Of course in a situation where nothing else is
possible, we need to have a way to unblock CI by forced push. But we
are not pus
Hi,
Force pushing of what? Of course in a situation where nothing else is possible,
we need to have a way to unblock CI by forced push. But we are not pushing
other than really mandatory fixes in bypassing the CI.
It is very unfortunate that dev has been broken for a while, but work is
ongoin
12.12.2017, 16:53, "Denis Shienkov" :
> > Did you try QQuickItem::grabToImage?
>
> Of course, it is veeery slowly.
I guess your best bet then is hardware grabbing video output
>
> 12.12.2017 16:40, Konstantin Tokarev пишет:
>> 12.12.2017, 16:13, "Denis Shienkov" :
>>> Hi all...
>>>
>>> Is i
Now I tried to use the following code:
classBindableFbofinal:publicQSGBindable
{
public:
explicitBindableFbo(QOpenGLFramebufferObject*fbo)
:m_fbo(fbo)
{}
voidbind()constfinal{m_fbo->bind();}
private:
QOpenGLFramebufferObject*m_fbo=nullptr;
};
Grabber::Grabber(QQuickItem*parent)
:QQuick
> On 12 Dec 2017, at 14:53, Denis Shienkov wrote:
>
> > Did you try QQuickItem::grabToImage?
>
> Of course, it is veeery slowly.
If the frame was rendered on the GPU, you have to download it from there, and
that is slower than if you had rendered into CPU memory, as widgets do by
default. T
> Did you try QQuickItem::grabToImage?
Of course, it is veeery slowly.
12.12.2017 16:40, Konstantin Tokarev пишет:
12.12.2017, 16:13, "Denis Shienkov" :
Hi all...
Is it possible to grab a QQuickItem content (e.g. with all sub-items)
when an item changes?
Did you try QQuickItem::grabToImage
12.12.2017, 16:13, "Denis Shienkov" :
> Hi all...
>
> Is it possible to grab a QQuickItem content (e.g. with all sub-items)
> when an item changes?
Did you try QQuickItem::grabToImage?
>
> E.g. with widgets I use the following code:
>
> bool MyWidget::event(QEvent *event)
> {
> if (event->
12.12.2017 16:13, Denis Shienkov пишет:
Hi all...
Is it possible to grab a QQuickItem content (e.g. with all sub-items)
when an item changes?
E.g. with widgets I use the following code:
bool MyWidget::event(QEvent *event)
{
if (event->type() == QEvent::UpdateRequest)
myGrab();
Hi all...
Is it possible to grab a QQuickItem content (e.g. with all sub-items)
when an item changes?
E.g. with widgets I use the following code:
bool MyWidget::event(QEvent *event)
{
if (event->type() == QEvent::UpdateRequest)
myGrab();
return QWidget::event(event);
}
void MyW
Ah, so last successful integration on qt5 super module was nearly a month ago??
11/172017
Now, what I was really after was last generally unsuccessful integration to see
how all the brokenness went through. I guess the git repo is not the source of
truth for that. The integrations yesterday we
Hi,
I find the easiest way to find the last successful integration for example for
qt5.git dev is this:
(1) Go to http://code.qt.io/cgit/qt/qt5.git/ and pick the dev branch
(2) Click on the last commit in the branch
(3) Click on the "Change-Id" link or paste the commit sha1 into
14 matches
Mail list logo
