i want to use Entity{} on Page{}, this because i want to click a button and show another page that have the Qt3D model , please help how i can do it with stackview, stackview only read pages not Just Entity Module ! ,
you should use Scene3D in Page to use Qt3D.
Related
I am having a project with a Qwidget form and the Mainwindow form, this Qwidget form does not have it own class, but I want to call the form from the button click event of the Mainwindow.
I just cant figure out how I can make it work, any help is appreciated
You can create user interfaces dynamically at runtime using QUiLoader class.
See https://doc.qt.io/qt-5/quiloader.html .
Maybe that's what you are looking for.
I would like to create a single form that I can bind to a datasource in create mode and in "normal mode". The use case is that I can have an existing item in the datasource that I would like to edit, or I would like to create a new one.
I can't find a way to dynamically switch the datasource mode before opening the form. It seems that 2 forms are required to accomplish this.
Any suggestions on how to accomplish this?
It is possible to reuse form fields, but you'll still need at least two forms (containers). The idea is to create a page fragment with datasource derived from some model:
then you can add this page fragment to form (container) and override datasource.
Normally you would choose between normal mode:
#datasource.item
...and create mode:
#datasource.modes.create.item
You can find complete code sample in Project Tracker template and learn more about create mode in docs:
https://developers.google.com/appmaker/models/datasources#create_mode_datasource
I have created custom dialog class that inherits from QDialog. I would like to use it in a Qt Designer.
However there is a problem, as I do not know how to add it to the templates, that I could pick, when I select File/new.
I also tried to start with QDialog and then promote it to my custom class, however context menu on the form does not give me option to promote or change type of the form.
Is there a solution to this problem which does not include manually tweaking generated .ui file ?
How to Hide the Back Button in Qt installer framework?
Please see attached image.
See my answer to Qt installer framework hide or disable buttons quoted below:
For the wizard BackButton specifically, it automatically disables itself if there are no pages before the current page a la the Introduction page.
From QtScript this can be accomplished by removing any dynamic pages before the current page with installer.removeWizardPage and disabling all default pages before the current page with installer.setDefaultPageVisible(QInstaller.Introduction, false).
There is void QWizard::setButton ( WizardButton which, QAbstractButton * button ) what means you schould be able to set a button which behaves like you need it. Derive a Class from QAbstractButton. Reimplement the paintEvent() to paint nothing and reimplement the mouseEvents to do nothing. That should do the (dirty) trick. Even if the wizard sets it to be visible, it won't draw itself and can't digest and mouse actions. Just tested it ... should work for you.
I have form in getcmsfields_forpopup for backend(admin panel) in silverstrip. In that form, I have added nested dataobjectmanager field to enter multiple dates(has_many relation). When main form open in popup window and I click on add date link, then second popup form open in the same window not in separate one. That means after entering date data and saving it, when I click on close button, whole form is closed rather going back to main form. Please help in this regard.
This can't be done using SilverStripe's default popup form unless, maybe, you extended the DataObject Manager field and had it render itself in an iFrame.
The best option would be to manage your parent DataObjects with DataObjectManger as well. DataObjectManager supports nested DataObjectManager fields. See this tutorial "Nested DataObjectManager" (on YouTube).
If you're able, can I suggest that you try out SilverStripe 3.0? The support for this kind of thing is much better in SilverStripe 3.0 than it is in 2.4.