-
Notifications
You must be signed in to change notification settings - Fork 67
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
Ability to select a container to add widgets to #83
Comments
openContainer now correctly deals with different container types.
Just tested this on version 0.042 and .openLabelFrame() does not put the added widgets into the frame border Also is it possible to start an empty container, then later use the .openLableFrame()? |
As mentioned in issue (#98) the website is out of sync with the release cycle - it's being updated from the development build (next_release branch). This will hopefully be resolved with the next release (0.05) - which is scheduled for the end of the month. If you want access to the 0.05 features, you can switch to the next_release branch and download the appjar.py file, and replace your existing one... |
Currently, it's not possible to create empty containers - as there was no way to reopen them, there was never a use case for this. It does seem that this is something desirable, now that containers can be opened later and modified... I'll raise this as a new feature request. |
this is the code im testing with for the open container
Pressing Next2 is what i want to get when pressing next. What am I doing wrong? and doing pressing Next2 first then Next renders the results I would expect. Edit: I am using the next_release version |
Having a quick look, I think there's a bug in getRow when you open a container. getRow is returning 0 when you open the labelFrame, causing it to overwrite the existing widgets, instead of returning what would have been the nextRow. If you manage your own row counter your may have more success, initialise it to 0, then add 2 at the beginning of each iteration. |
In fact, all container settings get lost when you reopen a container. __removeContainer() should pop the top item, but add it to a cache |
Container config options weren’t being kept. Now, when you open a container, the old config is used. This keeps row counts, sticky, padding settings consistent. Added dictionary of usedConfigs with type__title as a key When a container is closed, the config is added to this dictionary. When a container is opened again, the config is loaded from this dictionary.
Have updated next_release to retain config options. |
Start on work to allow toolbar to be hidden/shown when mouse goes over. Involves having a second label - just a few pixels tall. When the mouse goes over it - hide it & show the toolbar. When the mouse leaves the toolbar - hide it & show the label. Includes a function to ```setToolbarPinned()``` to turn it on/off. Now needs an icon (drawing pin) to place in toolbar to call the pin function/show pin status.
Added icons (50% size of originals, and show them in toolbar Clicking the icon will toggle the pin state, and in turn change the icon
* added basic tooltip - need to merge into next_release so we can change it easily on toggle * changed way it functions - tbs default to no pin, user has to call `.setToolbarPinned()` to turn it on and give the top an initial pinned status * changed `.__dimensionWindow()` it now makes sure the toolbar is showing before setting minimum size A couple of things to think about: * should be possible to remove the pin, after it’s added * hiding the toolbar causes the window to shrink - maybe not ideal…
Trying to get all feature branches merged into one
Once the GUI is up and running, there is a requirement to dynamically create new widgets.
It's possible to hide/delete existing widgets. But, if widgets are added - they'll be added to the topLevel container at the end (or over the top of existing /removed widgets).
It should be possible to select a container, remove all widgets from it, and add widgets to it.
A simple call -
openContainer(type, name)
- could be provided to allow widgets to be added to the relevant container.removeAllWidgets()
should then only apply to the current container and its children...The text was updated successfully, but these errors were encountered: