Recent posts

#21

PlanetSquires Software / Re: Tiko - beta tests

Last post by Paul Squires - August 06, 2026, 09:55:46 PM

It is not a problem of the size of the font, but of the space between lines. Like writing with Word using 1.5 between lines. The same problem that happened with the menus in an early version.

Yes, I kind of figured it would result in the same issue as the top menu problem we dealt with. I'll get it all fixed up.

#22

PlanetSquires Software / Re: Tiko - beta tests

Last post by José Roca - August 06, 2026, 09:14:36 PM

It is not a problem of the size of the font, but of the space between lines. Like writing with Word using 1.5 between lines. The same problem that happened with the menus in an early version.

#23

PlanetSquires Software / Re: Tiko - beta tests

Last post by Paul Squires - August 06, 2026, 08:24:33 PM

Thanks José,

As I feared, the larger font and spacing was too much. The OK, CANCEL don't fit on the dialog based on your display.

#24

PlanetSquires Software / Re: Tiko - beta tests

Last post by José Roca - August 06, 2026, 05:30:58 PM

@José Roca if you have tried this beta then I would be interested to know if the dialog and font sizes are okay on your computer/laptop.

No. I guess there are "Ok" and "Cancel" buttons, but they aren't visible.

#25

PlanetSquires Software / Re: Tiko - beta tests

Last post by hajubu - August 06, 2026, 04:46:45 PM

Thanks, Paul.

Yes , I had edited the "OWL" for all the necessary entries  manually.
therefore the results are the same , as what you did with the adapted defines and surrogates

Therefore my observation , said before, can be also confirmed with your edition.
a) The CLef-symbols IS NOT visualized in TIKO Editor : OWL is Visible as it should
b) FBC log text does not display the UNICODE symbols (by nature).
c) TODO/NOTES show a equivalent  of the OWL in Black & White only

b.r. Hans

P.S: I'll try to understand the reason behind - then I'll will be back.

#26

PlanetSquires Software / Re: Tiko - beta tests

Last post by Paul Squires - August 06, 2026, 04:04:37 PM

The problem is not the compiler, but rather the test code itself. The #DEFINE set at the top of the code has hardcoded values later in the test suite based on that value. Changing that value from a clef to an owl did not (obviously) change the hardcoded HI/LO values later in the test.

Use the attached test code file (in the zip) until I can update the Github repository.

#27

PlanetSquires Software / Re: Tiko - beta tests

Last post by Paul Squires - August 06, 2026, 03:48:24 PM

The OWL produces the following error output:

USTRING usage showcase

FAIL m[1] is the HIGH surrogate got= 55358 want= 55348
FAIL m[2] is the LOW surrogate got= 56713 want= 56606
FAIL units recombine to U+1D11E got= 129417 want= 119070

 142 checks, 3 failed

I'll post a fix/explanation as soon as I can.

#28

PlanetSquires Software / Re: Tiko - beta tests

Last post by hajubu - August 06, 2026, 03:10:39 PM

thanks , Paul

I'm trying a little the USTRING, but I'm struggling withe visualization.
The character used in the showcase "ustring_usage_test_owl.bas" U+1D11E is not visible in TIKO.
The emoji OWL can be visualized as it show below.

I added/changes from the Musical Clef values to the values for OWL. )inclusive for the surrogate pair (hi,lo)
All 146 test running fine for both , but not the visibility for the clef.

Also the compiler log files do not show the symbol, which may by nature of the fbc.
Your TODO/NOTES TAB Panels show the OWL with the emoji for the black & white symbols.
The Musical Clef sees , do not have an equivilant (?).

b.r. Hans

Code Select Expand

'#define ASTRAL wchr(&h1D11E)      ''  surrogates( hi:0xD834, lo:0xDD1E ) i.e. |𝄞|   U+1D11E MUSICAL SYMBOL G CLEF)
'#define ASTRAL wchr(&h1F989)       '' surrogates ( hi:0xD83E, lo:0xDD89 ) i.e. |🦉| U+1F989 OWL



#29

PlanetSquires Software / Re: Tiko - beta tests

Last post by Paul Squires - August 06, 2026, 09:11:28 AM

Hi Hans,

I tried doing so myself and the new toolchain did not show up under the list of available toolchains. Turns out there was a bug in the new PsListTree control that scrolled the first item off the top of the list (which happened to be that new toolchain). it's fixed now but not in the development branch because I am doing other major work off a feature sub-branch from development that I don't want to disturb.

To make things easier for you, I have attached the new tiko.exe with the fix included.

Just add the whole \fbc-win folder from the USTRING repo to the \toolchains folder off of Tiko. I renamed my new toolchain to fbc-win-USTRING so that I would know for sure what that toolchain does.
 

#30

PlanetSquires Software / Re: Tiko - beta tests

Last post by hajubu - August 06, 2026, 08:47:49 AM

Hi, just tried the new "UString" with fbc-win (1.20?) under the Toolchains within Tiko-beta.

How can we add the additional compiler with the help of the Settings options (Ctrl + ,).
I do know to add them manually in the settings.ini ( that worked).

Testing this with  Tiko132 - it does offer to set the alternatives with the options (Shift + F7) as it find the new folder under the "Toolchains" by itself.

It would be a great support you could check the possibilities.

Thanks Hans (Hajubu)