Daniel Peñalba

Using ClearType should help with readability.

Just you to know, ClearType support is coming in soon. Currently in dev... The difference is more noticeable zooming in:

@Xarbroughare .asset file always text in your case? We found exceptions for example with terrain files, which have .asset extension, but they are binary.

@yonggyun about the support for double byte language support we already have a beta version supporting it. Please let us know if you want to access to the beta program and want to test it. cc/ @vsanchezm

We were told that this is is purely a limitation of the Skia milestone used by SkiaSharp. The out of the box Windows Skia build has dysfunctional ClearType even with Avalonia custom Skia build that uses a up to date milestone. So at the moment the only available solution is using a downgraded Version of SkiaSharp on Windows. The developer who is working on a native skia bindings.. which is almost working… has returned from holiday and is resuming this today. So hopefully they can find a way to make clear type work with the latest skia version.

Plastic picks it from https://gravatar.com service, so once you change it there it should be update in Plastic SCM GUI.

Hi @Francois Bertrand, We compacted the GUI a little bit ... I think it looks better now.

Ok, thanks for the clarification. We added it to the roadmap 😉

@Jonah Grimm thanks for your feedback. It's always very valuated. We didn't add it because each category node (changed/added/moved/deleted) already have this info, but you're right, we're not displaying the totals. Just out of curiosity ... are these metrics (total count/checked) something that you use and it's valuable in your daily basis? And ... the most important question, ... why? I mean, in which workflow do you use them? That's being said ... yes! It's doable and it could be added in the "Items" header easily 🙂

@mklasson I already fixed this issue. https://github.com/danipen/TextMateSharp/pull/16 It will be published in the next public Plastic SCM release. Thanks for your help! 😉

Well, the file "plastic.selector" is mandatory for Plastic to work properly. If you're missing it, plastic won't work well for sure. @calbzamcan assist you to fix this issue.

About you "no selector" error: 2022-04-23 13:08:02,023 MST11\major ERROR plastic - Plastic SCM client version: 11.0.16.6860 2022-04-23 13:08:02,023 MST11\major ERROR plastic - Error message: There is no selector for this workspace. e:\Development\Unity\2021\Mouse4CatV2 Can you check the following file? e:\Development\Unity\2021\Mouse4CatV2\.plastic\plastic.selector? You should have something similar to this: rep "my-repo@my-org@cloud" path "/" smartbranch "/main"

Thank for reporting this. There is a mismatch in localization keys that were not properly removed. We will fix it for the next public release. In the meantime, if you want to workaround the issue you can manually delete the following localization key from the file: <plasticinstalldir>\client\localization\plastic-gui.en.txt Content to remove: == CloudLocalAccount == Local Sorry for the inconveniences.

Ok I think this is doable using collapsing blocks in the text editor. We can consider this feature request for future developments cc/ @mariechristineb

Thanks for reporting this. We didn't add this yet because the source editor we use (AvaloniaEdit) is super slow when displaying white spaces. As they're rewriting the text rendering layer I guess if after that displaying white spaces is faster. I'll check that after the changes.