The type of layout management provided depends on each container, although setting the layout is usually just a matter of selecting the container by clicking it, and applying a layout. In Qt Designer, these are automatically created for you, so you can add child objects to each page straight away.Įach container typically allows its child objects to be arranged in one or more layouts. Normally, when adding pages (tabs, pages, compartments) to these containers in your own code, you need to supply existing widgets, either as placeholders or containing child widgets. Stacked widgets, tab widgets, and toolboxes are handled specially in Qt Designer. Both widgets and spacers can be used inside containers. This feedback is important because it is easy to place objects close to containers without actually placing them inside. This indicates that you can drop the object inside, making it a child object of the container. When you drag an object from the widget box (or elsewhere) on the form, each container will be highlighted when the cursor is positioned over it. Qt Designer provides visual feedback to help you place objects inside your containers. They can be used to perform a variety of functions, such as managing input widgets, providing paged and tabbed layouts, or just acting as decorative containers for other objects. Container widgets provide high level control over groups of objects on a form. Thanks.Įdit: tried to upload a screenshot to illustrate the "redded out" text in the Qt Quick Settings Dialog, but insufficient karma as yet :(Įdit again: enough karma now for a screenshot. Or is something wrong in the rest of my configuration? Do I have some leftover cruft from an old installation? Why are the paths in "QML Emulation Layer" in Option|Qt Quick|Qt Quick Designer dialog redded out?Īny help or suggestion would be most welcome. Do I need to mess with other stuff in the qt.conf. Restart the IDE again - of course - and the same error trying to switch to design mode. It's contents: īut the missing library is in /home/rob/SailfishOS/lib/qtcreator/ There it is! It's in "/home/rob/SailfishOS/lib/qtcreator/" So back to the qtcreator director for more investigation. home/rob/SailfishOS/lib/qtcreator/libicui18n.so.42.1 home/rob/SailfishOS/lib/qtcreator/libicui18n.so.42 home/rob/SailfishOS/lib/qtcreator/libicui18n.so lets try locating where that lives: sudo updatedb locate libicui18nĪnd the results: /home/rob/.local/lib/python3.5/site-packages/PyQt5/Qt/lib/libicui18n.so.56 qml2puppet: error while loading shared libraries: libicui18n.so.42: cannot open shared object file: No such file or directoryĪnother clue. That's a clue, since QML Puppet was mentioned in the original error message. Everything seems to be there, including qml2puppet. It's there, all right, so I opened a file manager to make sure. That's never good, right? So I tried browsing for the fallback path - in my case: Then I noticed that when I open the Qt Quick Designer tab, both paths in the QML Emulation Layer box were shown in red text. To further investigate - based on suggestion on from a google search - I opened Tools|Options|Qt Quick|Qt Quick Designer and switched back and forth between "Use fallback QML Emulation layer" and "Use QML layer emulation that is built with the selected Qt", restarting the IDE each time, but no change. I started off trying that suggestion, switching between the ARM and 486 kits but that doesn't seem to change the result. Now it tries to start designer for a qml form, but I always get an error: The executable of the QML emulation layer (QML Puppet) may not be responding. At first the button was unclickable, but that was solved by enabling the Qt Quick|QML Designer plugin. I've got a simple example program working: it builds and deploys on the emulator fine once I figured out how to switch build kits around - and learning to start the project name with "harbour" - and it acts as expected.īut I can't seem to activate the "Design" mode. I've been trying to get started with Qt Creator for Sailfish IDE (Qt Creator 4.8.1 (Sailfish SDK)).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |