IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
I also added an option for this, which made it easier for me to debug.
I haven't added it to the prefs yet.
TODO:
- Add the option to the prefs.
- Allow to turn on wrapping on a per-variable basis ('w' will turn this
on and off in the variables, view, and there will also be an option
in the variable inspection options window).
- Right now, wrapped lines beyond the first line are indented two
spaces. This is the same as what digging into a variable looks like,
which make it confusing (granted, digging in still indents further,
but it's harder to follow). I think variables that are sub variables
should have some kind of character preceding them, like:
varname: [1, 2, 3]
+ 0: 1
+ 1: 2
+ 2: 3
- When variables are not wrapped, there should be an ellipses at the
end. When unicode is supported, we can use …, otherwise, we use ...
This shows one possible use of the custom stringifier functionality.
The example function computes str(), unless it takes longer than one
second to compute (it uses signal.alarm() to determine this), in which
case it falls back to type.
Also included in this commit is a change that makes the custom theme and
custom stringifier preferences persistant, so that the user does not
have to re-enter them if deselects "Custom". This wasn't easy to split
out, so it's included here.
I still need to add support for manually choosing a the custom
stringifier on a per-variable basis.
This doesn't work, as the user will likely try to choose "Custom" before
entering a file name, resulting in an error. So instead, make choosing
"Custom" select the file entry box, and don't try to load it until the
preferences dialog is closed. Built-in themes are still updated
automatically.
lists
For now, you do it by selecting the list you want to grow/shrink and
pressing [ to grow and ] to shrink, but this can easily be changed.
This uses proportional growing/shrinking, just like the vertical -/+
does, i.e., [ multiplies the weight by 1.25 and ] divides the weight by
1.25. This perhaps should be changed, as it feels a little awkward,
though the "weight" part of it is hard-coded into urwin, and changing
that would not be easy. On the other hand, this isn't too hard to get
used to, and it's pretty easy to get the sizes you want.
All sizes are saved in the configuration file and reloaded in future
uses. So technically, a picky user could set any weight he wants to
suit his needs.
The problem was that the change didn't propagate to the global dict as I
thought it would. So instead, we use the get_state() of the checkbox
(which is backwards by the way). ui.setup_palette() doesn't seem to be
necessary in this case, so I left it out. Anyway, it will still be
called when the dialog is closed.
The keyboard shortcuts u/d seem backwards with the current order. On
the other hand, it seems like the current stack frame should be on top
to some. Therefore, we make this an option. See
https://github.com/inducer/pudb/pull/4.
Right now, the line numbers setting doesn't work correctly, and I don't
know enough about urwid/pudb internals to figure out why. Any help here
would be much appreciated.
Also, it would probably be a good idea to factor out the saving to file
so that it only happens when the dialog is closed.
