-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
9 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b25ce41
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really nice work on this!! This looks so good and works really well so far. For your first gui this is super impressive 😤
Problem with formatting tasks
It turns out that in the terminal, the way characters are spaced in stdout is different than they are in qt which is really annoying. I tried messing with this for a while and did not really get anywhere yet. I tried making a custom formatter which did not assume characters in python and qt were one to one but there was no luck there :/ My solutions for now would be
1. Do what you were doing before with manually entering the dots in the.json
file and test till you find the right ratio. This seems extremely painful tho so only do this if you really want to2. I did some research and it looks like instead of using the text that goes withQCheckBox
, pair the checkbox with aQLabel
. Then wed have a layout kinda like anHBox
for each task. In which the first item is the task and the second is the points. We could then align the points all the way to the right which would at least align all the points, still no dots tho3. The last idea would be to see if we can mess with the css of the text to make it mono spaced and maybe that could fix things. This is probably the most promising, but wed have to look further into it. UPDATE this is definitely what we want to do here. I tried it and it works
Parent everywhere
You actually do not need to provide parent when you are creating a widget, I ran your code again without parent and it works the same
A bit more pythonic
This does not affect how your code runs, just some fun python tricks you can choose to use or not, this really does not matter
Order of items
Rearrange your
addWidget()
calls such that the titles and progress bar get added before the scroll area