Clarion Unicode preview — beta refresh build 14373

Clarion · Unicode Preview · Beta Refresh

Refresh build 14373 — lost SQL connections re-establish themselves, SQL browses fetch faster, and the help gains a “How do I” chapter

A SQL drop. Lost server connections now automatically re-establish the connection to the server and the application continues gracefully: a VPN reconnect, a firewall that closed the session, a laptop that woke up — the files and views stay open, the next operation reconnects, a browse that was paging simply keeps paging. Two new browse prompts fetch a SQL page in one round trip instead of one row per trip, with a BLOB in the page up to 10x faster on SQL Server. A SQL connection configures itself from the OWNER string alone, no DSN on the user’s machine. The IDE’s “select a folder” is the modern Windows folder dialog everywhere. And the F1 help has a “How do I …” chapter with a task topic for every section of the tester guide, every topic in the Index. Plus the fixes and additions from beta testers’ reports in the forums: Known Folders, the wide CLIB twins, a two-picture DateTime format, a friendlier previewer. Already testing? Everything below is new since build 14313.

SQL automatic reconnect · ‘Page fetch size (SQL)’ · ‘BLOB fetch (SQL)’ · PROP:BlobFetch · DSN-less connect IDE the modern select-folder dialog on every “…” Help “How do I …” chapter · every topic indexed · Customizing a SQL Connection Compiler USTRING link names sz / z — rebuild multi-DLL solutions together From the forums Known Folders · CLIB wide twins + RmDirW · Pict(dt, pic1, sep, pic2) · previewer Jump / sidebar · varchar(max) as BLOB · BLOB hot fields · VALUE() / PROP:Value / SPIN FROM wide · PROP:FromQueue · Designer paints <13,10>

Highlights of this drop — then the full tester guide, whose “What’s new” section lists everything that changed since you last read it.

↻

Lost server connections re-establish themselves, the application continues

ODBC, MSSQL, Pervasive SQL and SQL Anywhere drivers. When the link to the server drops under a running program, every file and view of that connection stays open, the failed operation reports error 90 with the driver’s own message (FILEERRORCODE() = 08S01), and the next operation reconnects by itself — including a table the program opens for the first time after the drop, so the first save after an outage goes through. In a generated application (ABC and Clarion chains) the user sees one error box and the usual retry prompt, and Yes saves the record. A browse that was paging when the link went keeps paging: the generated browse re-runs its page fill once, on a fresh connection, and the user sees nothing at all. Hand code simply retries the failed statement; a VIEW continues after a RESET to its last position.

≫

SQL browses fetch a page per round trip — two new prompts

BrowseBox › Actions › Default Behavior, both chains. ‘Page fetch size (SQL)’: a value n fetches n rows per server round trip (ABC sets BRWn.PageSize, the Clarion chain emits BUFFER(view, n, 2, 0, 60)); a Clarion-chain SQL browse moves from one row per trip to n. ‘BLOB fetch (SQL)’ with the new PROP:BlobFetch: a browse that shows a BLOB keeps its page fetch — the driver positions on your row and reads the page in one trip, a 20-row page fill on SQL Server measured 110 us/row down to 11.5. Blank prompts generate exactly what they did, so an existing app changes nothing until you set them. A BLOB projected into a VIEW is the current row’s from the very first read, so a TEXT or IMAGE bound to a browse hot-field BLOB follows the highlight bar.

◫

AppGen: a BLOB can be a browse hot field

Pick a BLOB as a hot field on a BrowseBox and a TEXT or IMAGE bound to it follows the highlight bar: the picture, the note, the document of the selected row. The templates put the BLOB into the browse’s VIEW as a PROJECT and never into the queue (a queue cannot LIKE() a BLOB), and the highlighted row is re-fetched on every selection change, so the control always shows the current row’s blob. Both template chains, no hand code.

⚙

A SQL connection configured from the OWNER string alone

The UNICODECONNECT form works without a DSN on the PostgreSQL Unicode driver and on SQL Server: name the driver DLL and its settings as keywords in the OWNER and nothing is configured on the user’s machine. The new help topic “Customizing a SQL Connection” lays out the three layers — the OWNER string, the driver string switches, the ODBC driver’s own settings — with a copy-ready example for each. Over a slow link to SQL Server, /MULTIPLEACTIVERESULTSETS=TRUE streams the rows instead of a server cursor round trip per fetch block; the guide’s SQL section says when to use it.

▣

The IDE picks folders with the modern dialog

Every “…” in the IDE that asks for a folder — New Project’s Location, the default project location in Options, Find in Files’ Look in, the project option folders — opens the Windows common item dialog in folder mode: the navigation bar, search, the places on the left, a “New folder” button, resizable. The small “Browse For Folder” tree is gone from the IDE. The most reported request of the beta, inside and outside.

⌂

Known Folders: Downloads, Documents, AppData and every other one, by name

SpecialFolder.GetKnownDir(KF:Downloads) returns the user’s Downloads folder, the one the CSIDL list never had. KNOWNFOLDER.EQU declares the common KNOWNFOLDERIDs as KF: equates — Downloads, Documents, Desktop, Pictures, Music, Videos, LocalAppData, RoamingAppData, ProgramData, Profile, Fonts, ProgramFiles, ProgramFilesX86, Startup, the Public ones — and any other folder from KnownFolders.h is one more equate written the same way. GetKnownDir(KF:Documents, 'MyApp') appends your sub-directory, the path comes back as a USTRING so a folder outside the ANSI code page is exact, and GetKnownError() holds the HRESULT of the last call. The CSIDL methods you already use are unchanged.

✚

Wide CLIB twins, a two-picture DateTime, a friendlier Report previewer

CLIB.CLW declares the wide twins FnSplitW, FnMergeW, MkDirW, AccessW and the new RmDirW, so a program that includes CLIB.CLW calls them by name. DateTimeUtil.Pict(dt, '@D10-', 'T', '@T04') joins two pictures with a separator — an ISO stamp, a file-name stamp — in one call. The report previewer’s Jump to a Page shows “of N pages”, clamps a typed number, and has First / Last buttons; the thumbnail sidebar’s scroll buttons sit side by side at the top. And the driver trace now shows a USTRING value in full, in the record dump and on the SQL bind lines, so a trace tells the truth about Unicode data. A browse sorted by a USTRING key on SQL Server positions cleanly from every sort tab, and saving a BLOB with bind tracing on no longer ends in an access-violation box. A wide VALUE() on a CHECK or RADIO lands in the USE variable with its exact units, {PROP:Value} on any captioned control and a SPIN’s wide FROM() deliver exact units too, and CONTENTS(?Combo) answers for a COMBO without a USE variable. And the Window and Report Designers paint <13,10>, every decimal metachar and {n} repeats exactly like the compiled window.

?

F1 help: a “How do I …” chapter, every topic in the Index

Right after Welcome to Clarion in Contents: 22 task topics, one per section of the tester guide (Unicode strings, screens, reports, SQL, TopSpeedW, the lost connection, the faster SQL browse …), each linking to the reference topics it needs. The Index finds them by title and by the words you would type — “lost connection”, “reconnect”, “faster SQL browse”. Every topic in the help now carries its title and chapter as index keywords, the 2026 reference topics carry a “See also” line, and the new browse prompts are documented where F1 on the prompt lands.

✎

From beta testers’ reports: dictionary, AppGen, DATETIME, previewer

varchar(max) imports as a BLOB, so the whole column travels (it joins text, ntext, nvarchar(max) and varbinary(max) under one rule). DateTimeUtil builds from LibSrc alone and gains Pict(dt, picture) — the date part through @D4, the time part through @T4, the whole value through @DT. The Window Previewer’s generated program reads better and compiles every time, with @DT controls primed with a real date-time sample.

ƒ

USTRING link names of their own — rebuild multi-DLL solutions together

USTRING parameters now mangle as sz (every non-RAW form) and z (RAW), a link name no other type can produce, so a *USTRING and a *SHORT,ANY prototype never share one. What to do on this build: regenerate and rebuild every module of a multi-DLL solution together (template-generated .exp files regenerate on their own); a hand-written .exp with zu/su lines changes them to sz; Pro2Exp / Exp2Map users update the letter table.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW / Memory / IP, recipes, the new-language-surface quick reference, and what to focus on when testing. The guide’s “What’s new” section lists everything in this drop, and every section has its task topic in the F1 help’s “How do I …” chapter.

Open the full Unicode Tester Guide

Report tool authors — the wide generator surface (IReportGeneratorW), format detection, the EMF record set, transition paths per integration style, and the PageTextIndexClass text index the previewer searches with:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — if you see something different, the beta forum is the place.

Clarion Unicode preview — refreshed beta build (14313)

Clarion · Unicode Preview · Beta Refresh

Refresh build 14313 — a modern report previewer, Unicode reports by default, a DATETIME type for SQL, and the wide file-name family complete

A bigger drop. With EMF pages new functionality is within reach, and the first of it is a new report previewer: search with highlighted hits, page thumbnails, marks, print or save the marked pages, copy text off the page — on a wide report all of it Unicode. For this beta release every existing application picks the previewer and Unicode (EMF) reports up automatically from the templates on its next generate, so de facto every app gets EMF reports; a hand-coded program reaches the same with the new compiler pragma define(report_unicode=>on). Tell us how that lands on your reports and your third-party report tools — that default is yours to confirm. A new DATETIME type carries a SQL timestamp to 100 nanoseconds through the compiler, the dictionary, the import wizard and every SQL driver. RUN() and COMMAND() go wide, closing the file-name family. Plus the fixes from beta testers’ reports in the forums. Already testing? Everything below is new since build 14258.

Reports ReportPreviewClass · Unicode reports by default · report_unicode define · PROP:Unicode Data DATETIME type · @DT picture · DateTimeUtil · import wizard checkbox Runtime RUN / COMMAND wide · CLIB wide twins · ALL() negative count IDE IMAGE field picker · no BLOB list columns · property search

Highlights of this drop — then the full tester guide, whose “What’s new” section lists everything that changed since you last read it.

▤

A modern report previewer — reached through EMF pages

ReportPreviewClass: text search across every page with the hits highlighted (Ctrl+F, F3, match case), a thumbnail sidebar, page marks with Print Marked and Save Marked Pages As, Fit Page and Ctrl+plus/minus zoom, Shift+drag to copy the text under the band, layout remembered in the INI, the index built on its own thread so a 1,000-page report opens at once. On a wide report the search is Unicode. It is the default for new apps, and a Print Previewer prompt that still reads PrintPreviewClass generates the new class on the next generate; “Keep the classic PrintPreviewClass previewer” opts out.

☷

For this beta release, reports print Unicode (EMF) by default

The new global “Unicode reports” check (on by default for this beta, so we hear how it lands) makes each Report procedure set Report{PROP:Unicode} = True as its report opens — USTRING fields, wide captions and emoji print as typed on .emf pages, error 546 stops, the PDF/HTML/TXT targets register their wide face; a per-procedure “Unicode pages” prompt opts one report out. The same check writes the compiler’s report_unicode define into the project, so hand-coded REPORT structures carry the UNICODE attribute too (PRAGMA('define(report_unicode=>on)') in a hand-coded module). PROP:Unicode is documented as the run-time face of the attribute. Watch for: a third-party page tool that read .wmf files sees .emf now.

⌚

DATETIME: a date and a time in one value, to 100 ns

A new data type — seconds since the Clarion day zero with seven decimal places, the precision of SQL Server’s datetime2(7). Compares, sorts, keys and does arithmetic in seconds; zero is blank. In a SQL table it reads and writes the backend’s timestamp column and CREATE() declares it: datetime2(7), timestamp(6), SQLite ISO text, Oracle TIMESTAMP(7); a VIEW filter on it is evaluated server-side. The @DT…@DT7 picture formats and enters it, DateTimeUtil converts to and from DATE and TIME (SetNow reads the precise clock), the Dictionary Editor offers the type, and the SQL import wizards create it for timestamp columns when “Import date-time columns as DATETIME” is checked (off by default — nothing changes for existing dictionaries).

▶

RUN() and COMMAND() wide — the file-name family is complete

RUN() takes a USTRING command line: a program in a folder outside the Windows codepage is located and started exactly and its parameters travel as typed; an ANSI-only USTRING takes the old path byte-for-byte. COMMAND() no longer shifts every parameter by one for a program that lives in such a folder (the ₿ folders from the forum). CLIB.CLW stays narrow by design, with four exported wide twins (_fnsplitW, _fnmergeW, _mkdirW, _accessW). With EXISTS, COPY/RENAME/REMOVE, DIRECTORY, FILEDIALOG and the PATH family already wide, that closes the family.

✎

Designers and dictionary, from beta testers’ reports

The Window Designer’s IMAGE gets the dictionary-field picker (BLOB and BINARY MEMO fields, the ones IMAGE,USE() accepts), and dropping a BLOB onto a window creates an IMAGE bound to it. A BLOB is never offered as a list-box column, and an app that already has one stops generation with a plain sentence instead of the compiler’s “Illegal parameter for LIKE”. The property-pane search is case-insensitive in every designer, and UNICODE is coloured as an attribute in the editor.

ƒ

Fixes from the forums: ALL(), the PDF class, datetime2 DDL

ALL() with a negative count returns ” again instead of “Clarion RTL internal exception” 0B000000. ABPRPDF.CLW compiles without warnings, and a real defect went with them: a wide report text longer than 99 units was cut in the PDF (150 units drew as 15). MS SQL CREATE of the legacy datetime group emits datetime2(7) on SQL Server 2008 and later — “Specified scale 8 is invalid” is gone.

?

F1 help, current for this drop

The IDE help (ClarionHelp.chm) carries new topics for DATETIME, the Date-Time Pictures, ReportPreviewClass, PageTextIndexClass and the Report template’s Preview Options; PROP:Unicode and the report_unicode define on the REPORT pages; the “Unicode reports” and “Unicode pages” prompts; and the three new stock icons ICON:PageUp, ICON:PageDown and ICON:Clear.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW / Memory / IP, recipes, and what to focus on when testing. The guide’s “What’s new” section lists everything in this drop; changes are also flagged inline with dated “beta refresh” notes.

Open the full Unicode Tester Guide

Report tool authors — the wide generator surface (IReportGeneratorW), format detection, the EMF record set, transition paths per integration style, and now the PageTextIndexClass text index the new previewer searches with, usable by your own viewer as-is:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — if you see something different, tell us on the beta forum.

Clarion Unicode preview — refreshed beta build (14258)

Clarion · Unicode Preview · Beta Refresh

Refresh build 14258 — the designers keep your Unicode, the fixes from four beta threads, and the wide path family

A shorter drop, built from the beta forum. The Window and Report Designers accept every U'' spelling and no longer rewrite it into a raw glyph; the Window Previewer can keep the generated program; DROP lists and COMBOs take a wide FROM at runtime; INSTRING() searches backwards from past the end; FILEDIALOG() opens on a Unicode folder; and the porting notes for SIZE() are in the help. Threads 47, 54, 57 and 60, closed. Already testing? Everything below is new since build 14234.

IDE U” hex literals in the designers · ANSI files keep U” · Save Preview Program Runtime DROP/COMBO wide FROM · INSTRING · FILEDIALOG Help SIZE() porting notes · INSTRING start rule

Highlights of this drop — then the full tester guide, whose “What’s new” section and dated “beta refresh” markers flag exactly what changed since you last read it.

✎

Designers: every U” spelling works, and your Unicode stays Unicode

The Window and Report Designer parse U'<26DDh>', U'<1F600h>' and {n} repeats exactly like the compiler — build 14234 refused a window with a hex literal. And a designer opened from an ANSI .clw now writes wide text back as a U'' literal (decimal units) instead of a raw glyph that forced the save-as-UTF-8 prompt; UTF-8 sources keep the glyph as before.

☷

DROP lists and COMBOs: a runtime wide FROM

?List{PROP:From} = U'…' on a LIST,DROP() or a COMBO keeps its characters — in 14234 that one property took the narrow path, so a declared FROM(U'…') worked and the runtime write showed ?. Reminder for continued FROM strings: put U on every piece.

ƒ

INSTRING backwards from past the end, and two porting notes

INSTRING(sub, s, -1, SIZE(s)) now finds the last match on a CSTRING or USTRING (those push only their used length, so a start past the end returned 0). Porting notes in the help: SIZE() of a USTRING is bytes, so a Windows API’s character count is SIZE(v)/SIZE(v[1]) — right for every string type — never SIZE(v).

▭

Window Previewer: Save Preview Program

A second checkable item in the Window menu, under Unicode Preview: latched on, the generated preview program, its project and exe move into .WinPreview\ in the project folder with the injection include beside them, so File ▸ Open builds and runs it as-is; a preview that fails to compile still keeps its source. Both latches are menu items only — the toolbar keeps just the Preview button.

⌂

FILEDIALOG positioned; the “Internal error 01” dialog is gone

FILEDIALOG() with FILE:Directory and a USTRING start folder opens with the selection on that folder even when its name is outside the Windows codepage. The “Output corrupted stack, wsldebug.cpp line 412” dialog was the release diagnostic logger misfiring; it now logs to C120LOG.TXT and carries on, so what you see next is the real fault.

\

PATH, SETPATH, LONGPATH and SHORTPATH are wide

A USTRING folder or file name is resolved in its exact characters and the result comes back wide, so a folder whose name lies outside the Windows codepage can be entered with SETPATH and read back with PATH() (the earlier drop best-fit it to ? and SETPATH failed with error 3). The no-argument forms return the current directory exactly; a STRING argument or receiver gets the same bytes as always. With EXISTS, COPY/RENAME/REMOVE, DIRECTORY and FILEDIALOG already wide, only RUN remains in the file-name family.

?

F1 help, current for this drop

The IDE help (ClarionHelp.chm) carries the INSTRING start rule with a SIZE(cstring) example, the USTRING porting note, the previewer’s second latch, and a USTRING note on each of the PATH, SETPATH, LONGPATH and SHORTPATH topics.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW / Memory / IP, recipes, and what to focus on when testing. The guide’s “What’s new” section lists everything in this drop; changes are also flagged inline with dated “beta refresh” notes.

Open the full Unicode Tester Guide

Report tool authors — the wide generator surface has shipped (IReportGeneratorW — six methods, opt-in, zero break for existing implementors). Format detection, the EMF record set, transition paths per integration style:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — different behavior is exactly what we want to hear about.

Clarion Unicode preview — refreshed beta build (14234)

Clarion · Unicode Preview · Beta Refresh

Refresh build 14234 — Unicode file names end to end, Unicode PDF, and a previewer for wide windows

Everything in this refresh traces back to a beta thread. The whole file-name family went wide — EXISTS, COPY/RENAME/REMOVE, FILE,NAME(ustring), DIRECTORY() with 64-bit sizes and FILEDIALOG(); both PDF targets export real Unicode text; the Window Previewer previews a window as a wide program; keystrokes, clipboard and tooltips carry Unicode; the dictionary lives as text. Already testing? Everything below is new since build 14204.

Files EXISTS · COPY/RENAME/REMOVE · FILE,NAME · DIRECTORY · FILEDIALOG Reports PDF Unicode (both targets) · encryption fix IDE Unicode Preview · dictionary as text · Reload Solution

Highlights of this drop — then the full tester guide, whose “What’s new” section and dated “beta refresh” markers flag exactly what changed since you last read it.

≡

Unicode file names, end to end

A file name or folder outside the Windows codepage — a Unicode user profile, a currency sign, CJK — now works through the whole family: EXISTS(), COPY()/RENAME()/REMOVE(), and FILE,NAME(ustring) on TopSpeedW and the DOS/ASCII/BASIC drivers (every driver takes a USTRING name whose text fits the codepage; the classic drivers report error 45 instead of a silent 90).

⌂

DIRECTORY() with Unicode names and 64-bit sizes; FILEDIALOG goes wide

A new queue type FILE:QueueW — Name USTRING, Size REAL (exact past 2 GB), Attrib32 — lists every name with its real characters; the old queues are untouched. FILEDIALOG() with a USTRING variable opens on a non-codepage path and returns it exactly, and a USTRING title shows as typed.

⎙

PDF export is Unicode — both targets

The stock Report to PDF target embeds a glyph-preserving subset of each font so a REPORT,UNICODE‘s text renders, searches and copies in any reader; Image2PDF does the same through libharu, color emoji included as pictures. Password-protected PDF export — is fixed.

▭

Window Previewer: a latched “Unicode Preview” button

Next to the Preview button (and in the Window menu): latched on, the next preview is generated as a wide program — every substituted USE variable a USTRING — so the preview runs the real wide ENTRY/TEXT/LIST classes. Latched off, the generated program is byte-identical to today’s.

⌨

Unicode keystrokes reach USTRING controls exactly

The runtime pump is wide: Win+. emoji, IME composition and any injected Unicode keystroke land in a USTRING ENTRY/TEXT as typed; ANSI windows keep their ANSI keystrokes by construction. CLIPBOARD()/SETCLIPBOARD() carry Unicode, and tooltips are wide on every lane.

≣

The dictionary as text

A .dctx twin beside the .dct is the source of truth: honest UTF-8 (a £ in a picture, a Ω in a prompt survive the round trip), Dictionary-menu export/import, and an audit of who changed what. Reload/Close Solution no longer revert an external .sln/.cwproj edit.

ƒ

UVAL(), PROP:ClipEntry, compiler messages restored

UVAL(string [,pos]) is the inverse of UCHR() — the code point at a unit position, merging a surrogate pair. SYSTEM{PROP:ClipEntry} (opt-in) clips typed trailing spaces from @S entries into CSTRING/USTRING.

☷

LIST and TEXT: the last residuals closed

Declared FORMAT() headers and column pictures keep their Unicode, the string FROM() lane is wide both ways, {PROP:Text} into a TEXT stores exact units, and TopScan previews a UNICODE blob as text. The LIST family is fully wide on declared and runtime lanes.

⊞

Oracle driver goes wide

NCHAR/NVARCHAR2 import as USTRING sized in units, NCLOB as a Unicode blob, DDL emits VARCHAR2(n CHAR)/NVARCHAR2(n-1) — and three long-shipped defects went with it. Set NLS_LANG to a Unicode-capable character set on Instant Client.

?

F1 help, current for this drop

The IDE help (ClarionHelp.chm) updated with the new RTL features: DIRECTORY/FILEDIALOG with FILE:QueueW, the previewer’s Unicode Preview, the PDF targets’ Unicode notes, UVAL, PROP:ClipEntry and the updated compiler messages.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW / Memory / IP, recipes, and what to focus on when testing. The guide’s “What’s new” section lists everything in this drop; changes are also flagged inline with dated “beta refresh” notes.

Open the full Unicode Tester Guide

Report tool authors — the wide generator surface has shipped (IReportGeneratorW — six methods, opt-in, zero break for existing implementors). Format detection, the EMF record set, transition paths per integration style:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — different behavior is exactly what we want to hear about.

Clarion Unicode preview — refreshed beta build (14204)

Clarion · Unicode Preview · Beta Refresh

Refresh build 14204 — a drop built from your reports

Nearly every item in this refresh traces back to a beta field report — exactly what the beta is for. CHOOSE() and POPUP() go wide, control pictures carry Unicode, TXA round-trips in UTF-8, INI files and the registry go wide, a full sweep of the string built-ins closed out the remaining port regressions — and there’s a Windows 11 fix every desktop app should retest. Already testing? Everything below is new since build 14175.

Language CHOOSE · POPUP · pictures · built-ins sweep IDE TXA in UTF-8 · %CWVersion 12026 Runtime INI · registry · Win11 hit-test fix

Highlights of this drop — then the full tester guide, whose “What’s new” section and dated “beta refresh” markers flag exactly what changed since you last read it.

?:

CHOOSE() takes USTRING values

A USTRING among CHOOSE’s values used to make the whole result numeric — even a plain-string alternative came back as '0'. Now string values give a string result that keeps every unit, and string-mixed-with- numeric stays numeric, exactly the STRING rules. From Carl B.’s report.

☰

POPUP() is wide

Menu text draws its real glyphs — currency signs, CJK, emoji — and the item structure (|, {}, ~, …) is decided on the wide text itself, so a full-width | in an item no longer splits the menu. All-ANSI POPUPs take exactly the old code path. Also from Carl B.’s reports.

@

Control pictures carry Unicode

A picture with symbols outside the codepage — say @n~₿~-15.2 — set on a LIST column (PROPLIST:Picture) or a pictured display STRING now formats with the real symbol and reads back intact. A wide LIST heading also survives a later reformat. (The pictured-ENTRY editor is a separate queued step.)

✎

Runtime caption rewrites go wide

{PROP:Text} = <wide value> on the caption families — PROMPT, STRING, BUTTON, CHECK, RADIO, TAB, GROUP/OPTION/SHEET — now keeps exact units. This was on the known-limitations list; it’s off it now.

ƒ

String built-ins, swept against gold

Every string built-in was measured two-era against Clarion 12 gold, and the remaining beta regressions fixed: DEFORMAT(x) with the picture omitted, ERROR() returning unclipped padding, NUMERIC() rejecting trailing spaces, ALL('',n), wide RIGHT()/CENTER() padding — and wide-to-wide compares now clip trailing spaces like narrow always did.

⇅

TXA export/import in UTF-8

Export application text as Application text, UTF-8 — a filetype choice in every export dialog, ClarionCL /u8 /ax on the command line, or the AutoExport-on-save option. Import auto-detects UTF-8 (with or without BOM) and rejects loudly, naming the line, instead of silently mangling. Defaults stay ANSI, byte-identical. From Petar’s request.

§

INI files and the registry go wide

GETINI/PUTINI accept and return USTRING exactly — and a wide write to a missing .ini creates it UTF-16 LE with BOM. The GETREG family matches the registry’s native UTF-16 end to end: RegEdit shows your real characters, and reads them back exactly.

#

Templates can gate the Unicode era

%CWVersion is now 12026 — #IF(%CWVersion >= 12026) is the idiom for template and third-party code that must also generate for older builds (equality tests against 12000 break; use >=). And multi-DLL exports of procedures taking USTRING arrays now link.

⊞

A Windows 11 fix worth retesting

Menus and mouse clicks going dead when another app’s always-on-top window (Windows 11 shell “island” windows are the usual trigger) overlapped a Clarion window — fixed, from a tester’s precise analysis (thanks, Alexey). If you’ve seen a Clarion app stop responding to the mouse on Win11, retest on this build.

?

F1 help, rebuilt and current

The IDE help (ClarionHelp.chm) is rebuilt: the Unicode-era language surface — USTRING and friends, the new and changed built-ins, the INI/registry notes — is now in the F1 help itself, not only in the tester documents.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW / Memory / IP, recipes, and what to focus on when testing. The guide’s “What’s new” section lists everything in this drop; changes are also flagged inline with dated “beta refresh” notes.

Open the full Unicode Tester Guide

Report tool authors — the wide generator surface has shipped (IReportGeneratorW — six methods, opt-in, zero break for existing implementors). Format detection, the EMF record set, transition paths per integration style:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — different behavior is exactly what we want to hear about.

Clarion Unicode preview — refreshed beta build (14175)

Clarion · Unicode Preview · Beta Refresh

Another refresh — the window itself goes wide

This drop pushes Unicode out into the window chrome — titles, menus, the status bar — carries wide columns into LIST and the TopScan browser, widens the client/server IP driver, and folds in a batch of fixes straight from your reports. Already testing? Everything below is new since the last build.

UI window chrome · menus · status · LIST cells Drivers IP goes wide IDE Solution Explorer reload

Highlights of this drop — then the full tester guide, whose dated “beta refresh” markers flag exactly what changed since you last read it.

▭

Window chrome goes wide

Window, frame and MDI-child titles, menu item text, and runtime writes to the status bar, message zone and tips now carry exact UTF-16 — set them in the designer or at runtime with {PROP:Text}. Narrow apps are byte-for-byte unchanged.

≣

Wide LIST columns — and TopScan

The last narrow LIST surfaces went wide: split columns (one queue field fanned across cells with |) and column headings now draw real glyphs, not best-fit. TopScan’s browser rides the same change — its cells show Ω, é, 中 with no changes on your side.

⇔

Controls widen at runtime

Bind an ENTRY or TEXT to a USTRING at runtime with {PROP:Use} and the control now switches to the wide class on the spot (and back again for a STRING) — no longer only when the USE was declared wide at compile time.

⟳

Solution Explorer keeps up

Edit a project outside the IDE — hand-edit the .cwproj, AppGen, source control, code-generation tooling — and the tree now offers to reload so it reflects reality. A manual Reload Solution command too, and a guard against silently overwriting an external edit on save. From a tester request — thanks, Mark S.

⇄

The IP driver goes wide

USTRING fields and UNICODE memo/blob travel end to end through the client/server IP database stack — client, requester and data server — round-tripping bit-identically at rest. Keys inherit the backing driver’s order for free.

⎙

Two report fixes from the field

A saved REPORT,…,UNICODE now reopens in the designer without the “Unexpected attribute” error, and two reports previewed at once no longer collide over page files (which could overwrite or drop one report’s pages). Both straight from beta reports.

☺

UCHR() and hex code points

New UCHR(code) is the one-argument form of CHR(code,1), and U'<…>' constants now take hex (U'<1F4A9h>' = one emoji) and full code points that emit the surrogate pair for you. Out-of-range is a loud error, never a silent truncation. From Carl B.’s post.

⚙

A compiler crash, fixed

An Internal Compiler Error that appeared and vanished with unrelated source edits — triggered by an identifier ending in a colon (e.g. from PRE(CS:)) landing at a pool boundary — is fixed. Reported against an earlier build; the fix rides this one.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW / Memory, recipes, and what to focus on when testing. Changes since the last build are flagged inline with dated “beta refresh” notes.

Open the full Unicode Tester Guide

Report tool authors — the wide generator surface has shipped (IReportGeneratorW — six methods, opt-in, zero break for existing implementors). Format detection, the EMF record set, transition paths per integration style:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — different behavior is exactly what we want to hear about.

Clarion Unicode preview — refreshed beta build

Clarion · Unicode Preview · Beta Refresh

New beta build — shaped by your reports

The Unicode preview moves fast: this refreshed build folds in fixes and features driven directly by tester feedback, widens two more drivers, and lands full documentation coverage. Already testing? Everything below is new since the last build.

Language MESSAGE · CHR · RTF · parameters Drivers Memory goes wide · TopScan reads .tpsw Docs Language Reference + Database Drivers updated

Highlights of this drop — then the full tester guide, whose dated “beta refresh” markers flag exactly what changed since you last read it.

💬

MESSAGE() displays wide

All the displayed text — message, caption, custom |-list button captions, the copyable CANCOPY form — now renders exact UTF-16, emoji included. No prototype change, no code change; plain ANSI calls are untouched.

☃

CHR() takes the full Unicode range

CHR(1F4A9h,1) returns the surrogate pair directly — no manual D800h math. Constants fold at compile time. And shared code can now gate its wide paths on the new predefined compile flag _USTRING_ (undefined on older compilers, so OMIT keeps it portable).

Rich text binds USTRING

TEXT,...,RTF with a USTRING USE variable displays, edits and saves back wide. Plain text stays exact UTF-16; formatted content saves as portable RTF source — paste it into Word or WordPad and your characters survive, emoji included.

✎

Sharper language edges

Value USTRING parameters are writable private copies (STRING parity — something value CSTRING never offered), and a &USTRING reference-assignment crash found through a beta report is fixed. Keep those reports coming.

Ω

Emoji fixes from the field

Two beta reports, two fixes: a color emoji at the right edge of an ENTRY was clipped, and mixed text-plus-emoji on UNICODE report pages could drop the text half. Both print and display correctly now.

≣

The Memory driver goes wide

USTRING fields, keys and UNICODE blobs on DRIVER('Memory'). Keys order by linguistic collation — the same order a keyed QUEUE gives wide components, so in-memory tables and queues agree.

⌕

TopScan reads .tpsw

TopSpeedW joins TopScan’s driver list — open, browse and edit wide TPS files; USTRING values round-trip bit-identically at rest. Plus a Segoe UI face-lift (your saved font choice is kept).

№

64-bit SQL integers, lossless

bigint / PG int8 imports as DECIMAL(19,0) and the full 19-digit value round-trips on every driver lane — earlier builds went through LONG or a double and silently rounded past 15–16 digits.

§

The books caught up

The Language Reference now covers the whole Unicode surface — USTRING, BSTRING, CHR, conversion functions, the REPORT UNICODE attribute, error codes. The Database Drivers guide gains TopSpeedW, the text-driver 4 GB story, and a first-ever precise chapter on driver-string and owner-string syntax (now 1024 characters, up from a silently truncating 255).

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW / Memory, recipes, and what to focus on when testing. Changes since the last build are flagged inline with dated “beta refresh” notes.

Open the full Unicode Tester Guide

Report tool authors — the wide generator surface has shipped (IReportGeneratorW — six methods, opt-in, zero break for existing implementors). Format detection, the EMF record set, transition paths per integration style:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — different behavior is exactly what we want to hear about.

USTRING — Unicode that feels like Clarion (v2)

Clarion · Unicode Preview (v2)

USTRING — Unicode that feels like Clarion

Wide text end to end: declare it, type it, store it, browse it. No new programming model. No special “Unicode mode.” If you already know CSTRING, you already know USTRING — and your existing ANSI apps stay byte-identical.

SQL MSSQL · ODBC · PostgreSQL · SQLite ISAM TopSpeedW · ASCII · BASIC · DOS UI ENTRY · TEXT · COMBO · captions · blobs · reports

A few highlights for Clarion developers evaluating this build — then the full tester guide (declaration rules, import maps, backends, recipes, what to poke at).

∅

Hands-off by design

Pick USTRING in the DCT, USE it on a control, PUT it to SQL. No conversion buffers, no “wide mode” flag, no per-screen ceremony. It just works the way Clarion always did.

Σ

All SQL backends speak Unicode

MSSQL, ODBC, PostgreSQL, and SQLite: USTRING(n) ↔ NVARCHAR(n-1) (logical length round-trips). Keys, GET, SET/NEXT, and bound WHERE values stay wide — never narrowed literals.

⚡

TopSpeed goes wide

Classic TPS is untouched. New driver: DRIVER('TopSpeedW'), .tpsw files, USTRING fields + UNICODE blobs, keys that work, and clean version rejects instead of silent mojibake. TopSpeedW files use the new 512 GB big file format — the classic 2 GB limit is now a guarded error, never a corrupted file, and SEND('BIGFILE=ON') upgrades an adopted classic file in place.

Text drivers now do 4 GB

ASCII, BASIC and DOS files work to 4 GB in shared and exclusive modes. Before: shared files quietly died at 2 GB with a false “Access Denied”, and growing past 4 GB silently overwrote the start of the file. Now the limit is a clean, reported error — a full file is an error, not a corrupted file.

◉

A blob is a field

On SQL there is no MEMO(n) — long text is the blob. TEXT,USE(blob) displays and edits; IMAGE,USE(blob) displays. Window binding ships today; Report is the same mental model (next surface).

Ω

Reports print wide

Add UNICODE to a REPORT and wide text prints end to end — preview, print-after-preview, direct print — and emoji print in color, composing over colored bands. A report left un-opted posts a loud error 546 on wide data — never silent mojibake.

あ

Type your language — everywhere

Source (UTF-8 / UTF-16), Window/Report designers, DCT messages/tips, IME, emoji panel, clipboard. Captions and free-form ENTRY/TEXT/COMBO carry exact UTF-16 on any system codepage.

✓

ANSI apps stay byte-identical

No USTRING? No wide designer text? Rebuild and ship — same binary behavior as before. Opt-in tokens (e.g. PostgreSQL UNICODECONNECT=1) never change default connects.

⇄

Import maps that tell the truth

Import Tables: nvarchar → USTRING, ntext / nvarchar(max) → UNICODE memo/blob, binary max → BINARY blob — attributes already ticked. Data Browser edits wide without narrowing.

✨

Surrogate-safe editing

Emoji and non-BMP text edit as atomic characters on wide ENTRY/COMBO. Color emoji via DirectWrite where available; ordinary edits never leave half a pair behind.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, reports, blobs, SQL / SQLite / text drivers / TopSpeedW, recipes, and what to focus on when testing.

Open the full Unicode Tester Guide

Report tool authors — preview replacements, export targets, or anything that reads page files: when a report opts into UNICODE, pages are .emf instead of .wmf. Transition paths, format detection, and the generator-interface roadmap:

EMF Page Files — Transition Note

Standalone pages (best full-width). Everything described there is implemented unless marked as a known limitation — different behavior is exactly what we want to hear about.

USTRING — Unicode that feels like Clarion

Clarion · Unicode Preview

USTRING — Unicode that feels like Clarion

Wide text end to end: declare it, type it, store it, browse it. No new programming model. No special “Unicode mode.” If you already know CSTRING, you already know USTRING — and your existing ANSI apps stay byte-identical.

SQL MSSQL · ODBC · PostgreSQL · SQLite ISAM TopSpeedW · ASCII · BASIC · DOS UI ENTRY · TEXT · COMBO · captions · blobs

A few highlights for Clarion developers evaluating this build — then the full tester guide (declaration rules, import maps, backends, recipes, what to poke at).

∅

Hands-off by design

Pick USTRING in the DCT, USE it on a control, PUT it to SQL. No conversion buffers, no “wide mode” flag, no per-screen ceremony. It just works the way Clarion always did.

Σ

All SQL backends speak Unicode

MSSQL, ODBC, PostgreSQL, and SQLite: USTRING(n) ↔ NVARCHAR(n-1) (logical length round-trips). Keys, GET, SET/NEXT, and bound WHERE values stay wide — never narrowed literals.

⚡

TopSpeed goes wide

Classic TPS is untouched. New driver: DRIVER('TopSpeedW'), .tpsw files, USTRING fields + UNICODE blobs, keys that work, and clean version rejects instead of silent mojibake.

◉

A blob is a field

On SQL there is no MEMO(n) — long text is the blob. TEXT,USE(blob) displays and edits; IMAGE,USE(blob) displays. Window binding ships today; Report is the same mental model (next surface).

あ

Type your language — everywhere

Source (UTF-8 / UTF-16), Window/Report designers, DCT messages/tips, IME, emoji panel, clipboard. Captions and free-form ENTRY/TEXT/COMBO carry exact UTF-16 on any system codepage.

✓

ANSI apps stay byte-identical

No USTRING? No wide designer text? Rebuild and ship — same binary behavior as before. Opt-in tokens (e.g. PostgreSQL UNICODECONNECT=1) never change default connects.

⇄

Import maps that tell the truth

Import Tables: nvarchar → USTRING, ntext / nvarchar(max) → UNICODE memo/blob, binary max → BINARY blob — attributes already ticked. Data Browser edits wide without narrowing.

✨

Surrogate-safe editing

Emoji and non-BMP text edit as atomic characters on wide ENTRY/COMBO. Color emoji via DirectWrite where available; ordinary edits never leave half a pair behind.

Full tester guide — mental model, conversion rules, DCT import table, screen controls, blobs, SQL / SQLite / text drivers / TopSpeedW, recipes, and what to focus on when testing.

Open the full Unicode Tester Guide

Standalone page (best full-width). Everything described there is implemented unless marked as a known limitation — different behavior is exactly what we want to hear about.

Maintenance Release + USTRING Beta (Compiler/RTL Changes)

We have two updates scheduled for release this week:

  • Maintenance Release (shipping first)
  • USTRING Beta Release (follows)

USTRING Beta: Compiler + RTL Changes

The USTRING implementation requires coordinated changes to both the Compiler and RTL (Runtime Library).

We initially explored making the RTL interchangeable at runtime, allowing the IDE to switch between:

  • Shipping (production) RTL
  • USTRING-enabled (beta) RTL

However, this approach introduced unnecessary complexity and risk of cross-contamination between environments.

Decision:
We are shipping the USTRING beta as a separate IDE build, each with its own aligned Compiler + RTL.

Result:

  • Eliminates risk of mixing beta RTL into production builds
  • Keeps production and experimental toolchains fully isolated
  • Simplifies support and debugging

Fix: “Check for Updates” Failure

The Check for Updates feature failed shortly after the C12 release.

Root Cause:

  • A server-side WAF (Web Application Firewall) policy change
  • Requests were rejected with HTTP 403 (Forbidden) during TLS negotiation/connection handling

Status:

  • ✅ Client-side handling updated
  • ✅ Server compatibility restored

The update mechanism is now functioning normally.

Email Notification Rollout

Because the update mechanism is unavailable, we are notifying all subscribers via email.

  • Rollout begins this week
  • Email platform has been changed to improve delivery reliability

If you encounter any issues with updates or the new builds, please report them so we can address them quickly.