Tag Archives: Clarion beta refresh unicode

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

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.