Conversation
He didn't do it for every little thing, but those comments reflect exactly that, what he added/changed with respect to the gist version. |
I should have expressed myself differently. I understand the purpose of these comments, what I don't understand is the reasoning behind this manual procedure, we have version control software and diff tools built for this purpose after all. |
|
True, but if I look at my own coding habits, I actually do a similar thing, mainly so I don't have to resort to VCS or Differs to see what I changed/added when I just scroll through code. |
|
is there a particular reason to having a separate setting for highlight color? i feel like following the accent color would suffice and keep consistency, but maybe im missing something |
|
following the accent color leads to the issue as described earlier. It now just automatically uses a slightly different shade of the normal accent color. |
|
ahh i see. well then now that it uses a darker shade of accent automatically, the custom color for highlighted is effectively just cosmetic, and might aswell just use the accent color itself for consistency then? |
|
Hmmm, just checked again, the highlight is actually controling the text color of the executable(s). Still, for consistency it might indeed be better to just use the accent color, so it shows the same as updated games. |
|
Will this one ever get merged? |
|
low priority right now, but eventually yeah |


sorry for dumping everything in one commit, installed new git tool today and accidentally messed up my history with a hotkey
here is an overview to compensate:
begin_listboxto override item stylesListItemwhich handles styles and holds some other stuff which was previously computed inlineis_diris_filepathetc.PickerTypeenum and wrapped olddir_pickerfield withPickerType.Dirsvarianthighlighting happens based on picker type and extension,
PickerType.Execswill only highlight executables,PickerType.Mediaonly media, etc. i wanted to use mimetypes detection for this feature but turns out thatpython-magicrequires custom libmagic dlls for windows and pure pythonfiletypepackage is extremely limited at the moment.P.S. i noticed that you've added comments like
# addedand# changedin reference to the gist. i'm not sure what purpose they serve. perhaps it's time to remove them? it should be sufficient to leave the first comment pointing to the gist itself.