The new highlight feature in TestFlight version 2.2.3 looks amazingly good. The colours matches my taste as they are not a bit garish, but reserved.
I don’t understand why “green” appears a second time in the colour list under the separator although already listed as default colour above the separator. Is there any scenario that could not be realised or would be more difficult to realise if ‘green’ did not appear in the list below?
I would love to try out new features on test flight !!
The default style is highlight without a specified color in the markdown, like this: ==Default== and ==🟢green== highlights. Green is the current default color, but it could potential be provided as a setting.
We understand that this is a bit confusing as they look exactly the same. Suggestions on how to make this more transparent is welcome.
It is not only confusing but it also requires understanding what happens on the level of raw markdown to clear away the confusion. Also the question remains - even if the user understands what happens in the background - when and in which scenario you are faced with the decision between green as default colour and green as non-default colour. Also here whatever the reason for your decision is it requires to think about the appearance in another editor. That may fit to obsidian but in my eyes not to bear where you want to concentrate mainly on writing and the publication process in another editor is completely taken away from you.
My suggestion is to simply make tabula rasa. While all other colours appear with an unicode circle in another editor the colour green always appear without an unicode circle. In other words: just remove green from the bottom list. I don’t think anyone would have missed or asked for that extra little feature of having the colour green in duplicate. I think the main colour is the main colour for a reason: it is used most often and is therefore the colour that should be shown in another editor without an unicode circle, i.e. as you would expect in this editor.
Of course, you can use this opportunity to kill two birds with one stone and reduce another small complexity at another point. If green is only the main colour, it is no longer necessary to show the unicode circles in bears editor after writing “==” and continuing with choosing a non default colour. The information inside of bear would have no value at all then.
Selecting the main colour entails the risk that the user will not stick with their first choice forever, but will choose a different default colour depending on his mood. Over time, this can lead to inconsistent results in the user’s own exported notes. If at all, you as devs can ask the user in an own thread which colour they consider the best to the default one and then carve it in stone. I’m sure yellow or green will win the race