[Interest] QRemoteObject : slot call with return value
Hi, I would have a question about remote object slot call with return value: If a slot id called from client with a return value, it is asynchronized on client side (push), but what happens on host side ? 1) network iodevice receive the request 2) slot is called, in which thread ? network iodevice thread, or Object thread ? (i will test that today) 3) network iodevice get the return value of the call Does it mean the network iodevice thread is locked until the slot answer? or is it done by a future or something like this? Daes ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] Building Qt 5.15 on Ubuntu 20.04
Hi, Just install package python-is-python2 or python-is-python3. Regards, Tom čt 28. 5. 2020 v 6:43 odesílatel Nicholas Yue napsal: > Hi, > > Is there a way to specify a different python for the build of Qt 5.15? > > On Ubuntu 20.04, there is either python2 or python3 but during the build > of QML, the build script is looking for python > > For now I am creating a symlink but was wondering if there is a better > way. > > Cheers > -- > Nicholas Yue > Graphics - Arnold, Alembic, RenderMan, OpenGL, HDF5 > Custom Dev - C++ porting, OSX, Linux, Windows > http://au.linkedin.com/in/nicholasyue > https://vimeo.com/channels/naiadtools > ___ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest > -- Tomas Konir Czech Republic ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
Re: [Interest] QRemoteObject inheritance
Hi Brett,
Thanks for those details, it will help me to start the tests in the
right direction.
One of those new possibilities ties in here.
If you use repc to create the base class (Source or SimpleSource), it
will have the Q_CLASSINFO() added to the class by repc.
So you can create derived classes and then pass the derived class
pointer to enableRemoting() call.
That will get you the full API from the repc defined class up to the
derived class.
I didn't mention this before because I thought you weren't using repc
because you had pre-existing QObject classes that didn't make sense to
(re)create from repc.
Yes that is currently what i have: hierarchy of classes created specially for
remoting, from a hierarchy of back-end classes non-exposed.
So that would require a bit of refactoring, but it deserves at least a try, if
that make my code simplier.
MODEL and CLASS : do those keyword allow a hierarchy of object to be exposed without more work ?
Correct. Although to be honest, the QAIM behavior isn't ideal. Since
the model isn't local, even basic aspects, like the number of rows and whether
a node has children, are asynchronous and answered by model updates.
Yes, i am aware about the remote model limitation, but it has merits to easily
expose an existing model.
Currently i am constructing dynamically models client side from Replicas data,
but it requires obviously a lot of extra-coding, but in fact, i am more
interested by the CLASS keyword, that could help me to create hierarchy of
remoteobjects quite easily.
I suppose it enableRemote on the property Object automatically.
And also, if you have some information about that, are the
cmake tools
ready for REPC ?
There's been cmake support for a long time. I know it works at a high
level, but I still mostly use qmake.
Yes, sorry i found it:
https://doc.qt.io/qt-5/qtremoteobjects-cmake-qt5-generate-repc.html
qt5_generate_repc(SOURCES simpleswitch.rep
SOURCE)add_executable(directconnectserver ${SOURCES})
Thanks a lot for your advice.
Daes
Hi Daes,
On 5/24/20, 7:19 AM, "Daesdemon" wrote:
Hi Brett,
I don't know why, but i even didn't think to use REP on the server
side,only. That could obviouly changes a lot of thing as a boilerplate
tool. It was an all or nothing in my head, even if i knew globally the
way it works.
Excellent. It opens up a lot of possibilities.
For a quick test i will try the
Q_CLASSINFO(QCLASSINFO_REMOTEOBJECT_TYPE, ) then I'll
change my design to test the SourceAPI usage. I will probably have new
questions
One of those new possibilities ties in here. If you use repc to create the
base class (Source or SimpleSource), it will have the Q_CLASSINFO() added to
the class by repc. So you can create derived classes and then pass the derived
class pointer to enableRemoting() call. That will get you the full API from the
repc defined class up to the derived class. I didn't mention this before
because I thought you weren't using repc because you had pre-existing QObject
classes that didn't make sense to (re)create from repc.
MODEL and CLASS : do those keyword allow a hierarchy of object to be
exposed without more work ?
Correct. Although to be honest, the QAIM behavior isn't ideal. Since the model
isn't local, even basic aspects, like the number of rows and whether a node has
children, are asynchronous and answered by model updates.
And also, if you have some informations about that, are the cmake tools
ready for REPC ?
There's been cmake support for a long time. I know it works at a high level,
but I still mostly use qmake.
Regards,
Brett
___
Interest mailing list
Interest@qt-project.org
https://lists.qt-project.org/listinfo/interest
[Interest] Building Qt 5.15 on Ubuntu 20.04
Hi, Is there a way to specify a different python for the build of Qt 5.15? On Ubuntu 20.04, there is either python2 or python3 but during the build of QML, the build script is looking for python For now I am creating a symlink but was wondering if there is a better way. Cheers -- Nicholas Yue Graphics - Arnold, Alembic, RenderMan, OpenGL, HDF5 Custom Dev - C++ porting, OSX, Linux, Windows http://au.linkedin.com/in/nicholasyue https://vimeo.com/channels/naiadtools ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] do you use IncrediBuild with Qt ?
if so, please vote for this bug: https://bugreports.qt.io/browse/QTCREATORBUG-24093 ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
[Interest] how to reset the layout in QStackedWidget/QScrollArea
Hi, I have the following situation in the code: m_propertiesDock = new QDockWidget(this); addDockWidget(Qt::RightDockWidgetArea, m_propertiesDock); auto* sa = new QScrollArea(m_propertiesDock); stackedWidget = new QStackedWidget(sa); sa->setWidget(stackedWidget); sa->setWidgetResizable(true); m_propertiesDock->setWidget(sa); Later, different widgets of different sizes are shown in the stacked widget. The scroll area is used here to be able to show widgets that are bigger then the currently available place in the application window. Here an example for how it looks like: https://labplot.kde.org/wp-content/uploads/2018/10/histogram_main_window.png The properties dock widget is on the right hand side showing the widget with the properties of the histogram and. The problem now is that the widgets shown there have very different minimum sizes and when switching from a small one to a big one and then back to the small one, the whole available space left after the big widget is used also for the small widget. This leads to the situation where the small widget is unnecessarily stretched and the scroll bars are still visible which is actually not needed in this case. The checkbox "visible" like on the screenshot above is moved to the bottom of this available space and the user has to scroll down also for small widgets after switching from a big widget. This is how it looks like after such a switch: https://imgur.com/a/F5mCDwi So, I'm looking for a way to how squeze the stacked widget and maybe also the scroll area to the minimum size of the currently shown widget so there is no need to show the scroll bars in the scroll area. Can someboy please point me into the proper direction? Thanks and Regards, Alexander ___ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
