Open esauvisky opened 5 years ago
Hi!, i am having this issue... I am using Windows. And for the time being no access to a linux machine or other... Is it possible for you to put the configuration here, so that I can just copy paste? (not sure that will work, but I am willing to try)
Quick dirty solution from Azelphur works for those using Windows. Download the following app in your phone : https://play.google.com/store/apps/details?id=jp.ddo.hotmist.unicodepad
Find the non breaking character u00A0, copy it 12 times ^^ and add it after the naming you want in calcy, and before the following : $CatchDate$|$Lucky$|$ATT$|$DEF$|$HP$|$Gender$|$Trade$|$IV%Min$|$IV%Max$|$AttIV$|$DefIV$|$HpIV$|$FaMove$|$SpMove$|$Appraised$|$Legacy$
Should give something like this (without the ""): "WhateveruWanttoNAMEit""12Nonbreakingspaces" $CatchDate$|$Lucky$|$ATT$|$DEF$|$HP$|$Gender$|$Trade$|$IV%Min$|$IV%Max$|$AttIV$|$DefIV$|$HpIV$|$FaMove$|$SpMove$|$Appraised$|$Legacy$
I'm almost sure I sent a PR or Aze switched the nbsp for \xa0 instead of what was being used before. We ran multiple tests with several users until finding that was the most universally accepted nbsp.
If it wasn't sent, my bad, just cherry pick the commit or change the nbsp for that one
That commit was merged, we are using \xa0 https://github.com/Azelphur/PokemonGo-CalcyIV-Renamer/blob/master/ivcheck.py#L53 The above info is useful though for anyone having problems.
There were some reports of the nbsps not being pasted alongside the rest of the
CALCY_STRING
when configuring the device with--copy-calcy
.Further investigation with help from one of the affected users and a small testing script allowed us to narrow the issue a little bit:
u0020
. We tried all possibilities fromu2000
tou2008
[1].u2003
spaces we use from a chat message and paste it on CalcyIV. It also worked with the same device when running the script on a linux box.So far we only know for sure the problem relies between OS <-> adb which includes Python and all the libraries we use. The clipper service was working properly as it worked when running from a linux box.
My idea with the script was to find a nbsp that would work, but it seems like the problem is they are being converted to normal spaces regardless of which one we use.
[1]: When making the script, I forgot to add some other nbsps available (to be honest I didn't even know how many there were) The script now includes all I could found.