Unicode for question marks in a circle

[DanBadea]

The KISS principle respected... And reusable.

The lemonade...

I'm sorry about my old circled question marks. They are beautiful now (and pretty elegant... I think...).

Of course, the procedure must be completed with the link feature on the label and/or arrangement (as it must open a tip window...) but that is an easy task.

[DanBadea]

BTW, let's close this thread before they are joined on another thread... Above we have only two possibilities to have a "circled question mark" on AI2, the first possibility - is .image (it is ugly), and the second possibility - create ourself one as needed, unfortunately without Unicode (this sign simply... doesn't exist as Unicode). In that manner, we can make any pseudo-character sign.

Thank you all.

PS - There exists and CSS variant... but... arghhhhhh... don't use it, it will complicate your life.

[Kevinkun]

you can use an icon font

questionmark.aia (2.7 KB)

(download this file and rename it to questionmark.ttf, or other name but ends with .ttf)

and check this for the unicode
download.zip.aia (15.4 KB)

I got this ttf file from here:

iconfont-阿里巴巴矢量图标库

[ABG]

Strange, I see no circled question mark when I open the ttf file.

[Kevinkun]

same for me, but it will show the question mark if you follow the steps, right?

[ABG]

I guess I have learned a disappointing lesson about the Windows font viewer.

[ABG]

But where is questionmark.ttf?

You only posted iconfont..

[Kevinkun]

sorry for the mis understanding, I have edited my post.

[ABG]

The link says questionmark.aia, but iconfont.aia arrives.
Double check that link replacement, or better yet add a fresh one?

[Kevinkun]

it does not matter what name it is, just make sure its a ttf file.

[ABG]

Thank you, I will study this further tomorrow.

[DanBadea]

@Kevinkun

you can use an icon font

It can be a solution... But... It have pros and cons...

Pros

1. Simple to use.
2. No blocks needed.

Cons

1. From my visual point of view the rendering quality is not as good as the bluest-one.
2. Lack of customization.

I prefer the below approach as the only cons that it has is the fact that requires a few blocks (a few blocks = 69 blocks... in the below version )...

Here I have some questions for @Kevinkun

Why KevinkunEnhance.SetAsCard doesn't accept a string as margins but KevinkunEnhance.SetMargin accept string?! It is a small problem with the use of singular and plural vs results (I think that SetAsCard must accept string to customize independent the margins because actually, I must use a supplementary .SetMargin block ).

Why CompCreator.OnClick does not accept a list at component?! In the above example, it is a must to sense the touch on the label and arrangement, the only actual way is to duplicate the OnClick block!

BTW Kevin, can I ask you if you can/want/have time to make an extension?! Paid or free...

Thank you.