KTL Changelog - please subscribe to see all updates!

[cortexrd]

Keep an eye on this discussions, as it will be updated daily on all new features and bug fixes.

[cortexrd]

Just added new keyword: _zoom

Can be used to zoom in or out a view, whole page or a specific qualified CSS selector.
See: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#_zoomzoomvalue-options

[cortexrd]

Added a new keyword: _cls, which stands for Add or Remove Classes
Allows adding or removing classes from the current view, whole page or specific selectors.

Introducing the "keyword selector": ktlTarget
This allows some keywords to be applied to a view, whole page, or specific selectors.

Exposed the function ktl.core.extractKeywordParamGroups to parse groups of keyword parameters.

Added new ktl classes: ktlNarrowMarginsPage and ktlDenseGrid.
Used when high-density pages are required.

Norm

[CSWinnall]

Amazing Thank you this will be amazing to use.

[amandajane-mo]

Hi Norm,

Thanks, this is great _cls in combination with ktlTarget will be extremely useful for us, meaning we can do away with our slightly clumsy <span class='ourClass'> / .kn-view:has(.ourClass) technique for adding css to views/scenes etc.

We're already making use of your new ktlNarrowMarginsPage and ktlDenseGrid classes.

Amanda

[cortexrd]

We're already making use of your new ktlNarrowMarginsPage and ktlDenseGrid classes.

Cool!! I just wrote a demo on this now.

See How to make a high-density display in this page: #50 (comment)

Norm

[cortexrd]

Just added a new keyword: _style

See documentation here: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#_style

Norm

[cortexrd]

Hi to all,

I've just completed the migration from my older http server from https://ctrnd.com to the highly reliable AWS S3 Bucket https://ctrnd.s3.amazonaws.com.

The old one kept failing due to exceeding CPU usage, requests and bandwidth limits.
I guess the KTL is a victim of its own success !!! Thanks to all of you, dear users.

Now this also means that you need to update the KTL_Loader.js file with the new version here:
https://github.com/cortexrd/Knack-Toolkit-Library/blob/master/KTL_Loader.js

Simply overwrite the existing 5 lines from your apps with these new ones. Actually, only the line with the URL changes.

Norm

[cortexrd]

As a follow-up on the preceding message, there's another important change has been made to the KTL_Customization.js file.

The top first lines have changed from this:

var ktl;
window.ktlReady = function (appInfo = {}) {
    ktl = window.ktl;

to this:

window.ktlReady = function (appInfo = {}) {
    var ktl = new Ktl($, appInfo);

Please update accordingly, sorry for the inconvenience.
Normand

[cortexrd]

The _bcg keyword - barcode generator - has been upgraded.

It can now accept 3 parameters: size, field ID and hidden text flag "h".

See Wiki here: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#_bcgsize-fieldid-h

Norm

[jbk68]

Hey Norm, noticed that the "show app info" for both the app & ktl versions is being displayed even though I have the values set to "false" in script.

…

On Sun, Jun 25, 2023 at 8:02 AM Cortex R&D Inc. ***@***.***> wrote: The *_bcg* keyword - barcode generator - has been upgraded. It can now accept 3 parameters: size, fieldIndex and hidden text See Wiki here: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#_bcgsize-fieldindex-h Norm — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAZFAND3XDTUGDLLALDHBP3XNAZEVANCNFSM6AAAAAAZATU3JA> . You are receiving this because you are subscribed to this thread.Message ID: <cortexrd/Knack-Toolkit-Library/repo-discussions/47/comments/6273856@ github.com>

[cortexrd]

Hi,

1. Are you sure you have the latest code version? KTL is now at 0.13.9.
2. Did you do the server upgrade? See: KTL files are now migrated to a new AWS server for more reliability and availability. #22
3. Did you copy parts of the latest version of https://github.com/cortexrd/Knack-Toolkit-Library/blob/prod/KTL_Customization.js ?

Your code should look similar to this in the Javascript pane:

KnackInitAsync = function ($, callback) { // Load the Knack Toolkit Library (KTL)
    (window.LazyLoad = LazyLoad) && LazyLoad.js(['https://ctrnd.s3.amazonaws.com/Lib/KTL/KTL_Start.js'], () => {
        loadKtl($, callback, (typeof KnackApp === 'function' ? KnackApp : null), '' /*KTL version, leave blank to get latest*/, 'min'/*min or full*/);
    })
};

window.APP_VERSION = '1.0.0'; //Your App version.

window.ktlReady = function (appInfo = {}) {
    var ktl = new Ktl($, appInfo);

    //KTL Setup - BEGIN
    ktl.scenes.setCfg({
        versionDisplayName: 'MyApp',
    })

    ktl.core.setCfg({
        enabled: {
            versionInfo: {
                viShowAppInfo: true,
                viShowKtlInfo: true,
                viShowToRoles: ['Developer'], //Array of Account Roles strings who can see the version info bar. Leave empty for all.
                viPosX: 'right', //right, center, left
                viPosY: 'top', //top, bottom
                viPosXMobile: 'center', //right, center, left
                viPosYMobile: 'bottom', //top, bottom
                viOpacity: 70, //0 to 100
                viOpacityHover: 100, //0 to 100
            },
        },
    })
}

Note that it's highly recommended that the version info bar remains visible for the Developer role. It's also a button and allows doing very useful things when you click on it.

That's why this line sets it by default: viShowToRoles: ['Developer']

Norm

[jbk68]

I added the above script roughly an hour ago. Prior to adding it, for some reason this weekend, the apps that contained KTL started showing the version nfo for both our app and ktl even though the "show info" was set to "false" for both "showappinfo" and "showktlinfo". I like the new script above because it allows users to change the position of app info for desktop and mobile devices. Would be nice if we could choose what pages/views the app info is displayed or not displayed.

…

On Mon, Jun 26, 2023 at 9:24 AM Cortex R&D Inc. ***@***.***> wrote: Hi, 1. Are you sure you have the latest code version? KTL is now at 0.13.9. 2. Did you do the server upgrade? See: #22 <#22> 3. Did you copy parts of the latest version of https://github.com/cortexrd/Knack-Toolkit-Library/blob/prod/KTL_Customization.js ? Your code should look similar to this in the Javascript pane: KnackInitAsync = function ($, callback) { // Load the Knack Toolkit Library (KTL) (window.LazyLoad = LazyLoad) && LazyLoad.js(['https://ctrnd.s3.amazonaws.com/Lib/KTL/KTL_Start.js'], () => { loadKtl($, callback, (typeof KnackApp === 'function' ? KnackApp : null), '' /*KTL version, leave blank to get latest*/, 'min'/*min or full*/); }) }; window.APP_VERSION = '1.0.0'; //Your App version. window.ktlReady = function (appInfo = {}) { var ktl = new Ktl($, appInfo); //KTL Setup - BEGIN ktl.scenes.setCfg({ versionDisplayName: 'KT', }) ktl.core.setCfg({ enabled: { versionInfo: { viShowAppInfo: true, viShowKtlInfo: true, viShowToRoles: ['Developer'], //Array of Account Roles strings who can see the version info bar. Leave empty for all. viPosX: 'right', //right, center, left viPosY: 'top', //top, bottom viPosXMobile: 'center', //right, center, left viPosYMobile: 'bottom', //top, bottom viOpacity: 70, //0 to 100 viOpacityHover: 100, //0 to 100 }, }, }) } Note that it's highly recommended that the *version info bar* remains visible for the *Developer* role. It's also a button and allows doing very useful things when you click on it. That's why this line sets it by default: viShowToRoles: ['Developer'] Norm — Reply to this email directly, view it on GitHub <#47 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAZFANEWCLSN4HNOMJA7HNLXNGLTNANCNFSM6AAAAAAZATU3JA> . You are receiving this because you are subscribed to this thread.Message ID: <cortexrd/Knack-Toolkit-Library/repo-discussions/47/comments/6282893@ github.com>

[cortexrd]

Jon,

Prior to adding it, for some
reason this weekend, the apps that contained KTL started showing the
version nfo for both our app and ktl even though the "show info" was set to
"false" for both "showappinfo" and "showktlinfo".

I'm not sure why this happened. When in doubt, do a full code refresh by doing Ctrl+F5 to bypass the cache. Maybe you had an outdated version left in cache.

But now, is it working ok, as expected (not showing)?

Would be nice if we could choose what pages/views the app info is displayed or not displayed.

See my post here, I show you how to do it: #51 (reply in thread)

Norm

[cortexrd]

Introducing Keyword Options: ktlRoles and ktlTarget.

These give you more flexibility over keyword application context.

Which roles (including or excluding) will see its effect and applied to which CSS selector.

See here for details: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#keyword-options

Enjoy,
Normand

[cortexrd]

Introducing a new Keyword Option: ktlRefVal.

This new keyword option allows selecting any page element, from which the text will be extracted and used as the reference in your own "compare rules".

Currently, _cfv supports it, but more will be added as requested.

Go see the documentation here: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#keyword-options

An example here, in Knack's Forums: https://forums.knack.com/t/dynamic-colour-coding-of-grid/14517/6

Enjoy,
Norm

[cortexrd]

Colorize Field by Value (_cfv) has been boosted

It can now benefit from the new ktlRefVal option. See previous post.

Go try that! It's really useful.

Norm

[cortexrd]

I've just fixed a bunch of bugs with the User Filters' Drag'n Drop and context menu pop-up in Android.
Ref: issue #60

If someone have the chance to test on Apple devices, it would be appreciated.

Norm

[cortexrd]

Hi to all,

I've just completed a round of massive code changes in the KTL last week. The documentation has been fully updated to reflect all changes.

Due to the sheer number and complexity of all the changes and their impact over several hundreds of functions, it is possible that the current version v0.14.4 may have some unexpected/negative effect on your code and app. I am really sorry if that's your case. Please create an issue if you see anything unusual or broken.

Note that such important upgrades rarely happen. I always try to go in small incremental steps to avoid complications. But I had no choice in this case due to the nature of the deep changes in the keywords parsing algorithm and its data structure. I other words, the transition was unavoidable, maybe a bit painful... but well worth the effort.

Here are the changes:

1. It's now possible to have multiple instances of a given keyword in a view or field
2. The keyword options have been extended to several more keywords
3. The ktlRoles option is now supported almost everywhere
4. The documentation specifies which options are supported for each keyword
5. The _cfv keyword has been upgraded significantly. See the docs for details
6. Added the Account Logs viewer code. Documentation not yet be updated.
7. Completed the code to support the UTC Last Activity monitoring in the iFrameWnd, to see who's actually using the app in real time.

Enjoy,
Normand

[cortexrd]

I've just added the Add/Remove Class: _cls keyword documentation.

See here: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#_clsclass1-class2

Enjoy,
Normand

[cortexrd]

KTL Important Change: Auto Refresh Minimum Limit Increase

Hi everyone,

I need to share an important update about KTL's auto refresh feature (the "_ar" keyword) that will affect some of your applications.

The Situation

I've been contacted by Knack's upper management regarding the infrastructure impact of aggressive auto refresh usage. Their analysis shows that some accounts with small user bases (5 users, no API integrations, Pro plans) are generating tens of thousands of API calls per day through very short refresh intervals - creating a significant mismatch between server resources and actual usage.

The Change

KTL will increase the minimum auto refresh interval from 5 seconds to 60 seconds.

This change will be implemented on Friday, August 29, 2025 at 5pm EDT (9pm UTC) to give everyone time to prepare.

Why This Matters

• Current 5-second minimums can create excessive server load
• This impacts Knack's infrastructure and potentially affects performance for all users
• Increased costs for Knack: these view refreshes are actually uncounted API calls that are billed by AWS to Knack, but not by Knack to the client
• We need to be good citizens of the platform we all depend on

What You Need to Do

Please review your applications now and increase any auto refresh intervals to 60 seconds or higher.

Always try to choose the highest value possible that would be acceptable. In most cases, 60, 90 or 120+ second intervals provide perfectly adequate user experience while being much more server friendly.

Hint: to find all those keywords, you can open the app's console and copy/paste this command: ktlFindAllKeywords('_ar')

At the end of the output, you'll see a summary of any views with _ar below 60 seconds. You can then search for those view IDs in the logs above to jump directly to the Builder page using the provided links.

After Implementation

Once the update is live, any auto-refresh intervals below 60 seconds will be automatically capped at 60 seconds. Users having the Developer role will see a notification when this limit is applied and a log will be generated in the console output.

Your Cooperation Appreciated

I understand this may require some adjustments to your applications, but this change helps ensure the long-term sustainability of both KTL and the Knack platform for everyone. Please let me know if you have any questions or concerns about this change.

Thanks for your understanding and cooperation.

Normand

[cortexrd]

KTL Update: Auto Refresh Minimum Limit Change

Hello KTL Users,

Important Change: The minimum auto refresh interval (_ar) has been increased from 5 seconds to 60 seconds, effective immediately.

Background: This change addresses infrastructure concerns raised by Knack's upper management regarding excessive API usage from aggressive auto refresh configurations.

What to do:

• Review your applications and update any _ar values to 60+ seconds
• Use ktlFindAllKeywords('_ar') in console to find affected views
• The summary section will highlight instances below 60 seconds with builder links

Runtime behavior: Values below 60 seconds are automatically capped at 60 seconds. A console warning will be visible when this occurs.

Thanks for your cooperation in maintaining platform sustainability for everyone.

Regards,
Norm

[cortexrd]

New in KTL v0.34.0

New Keyword

_sfv: Set Field Value. Can be used in a form to set any input field to a specified value that can be hard coded or fetched from another field/view in the page.

Documentation

All documentation has been updated.
See it here: https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords#_sfvfield1-value1-value2-field2-value1-value2

Enjoy,
Norm

[cortexrd]

Important: KTL Version Storage Changes

Hi everyone,

I've been looking at my AWS storage costs lately, and they've gotten pretty high. Turns out I'm storing 588 old KTL files going back almost 2 years—some apps are still using v0.24.2!

I totally understand why some of you pin to specific versions rather than using "latest"—it gives you more control. But keeping all those old versions around is costing more than I anticipated.

Here's what's changing:

Going forward, I'll only keep the last 10 versions on the server, with automatic monthly cleanup of older files. I've already deleted everything before v0.24.2 (the oldest version anyone's actually using based on last week's data).

What you need to do:

If you've pinned your KTL Loader to a specific version, please update to one of the last 10 releases within the next 10 days. You can see which versions those are in the Tags section on GitHub.

If your pinned version gets deleted and you haven't updated, the loader will just fall back to the latest version automatically—you'll see a console warning when this happens.

My suggestion: Stick with auto-updating to "latest" unless you have a good reason not to. If you do pin, try to stay within the last 3-5 versions and keep things relatively current.

This keeps hosting costs manageable while still giving you some rollback options for debugging.

Thanks for understanding!

Normand
Cortex R&D Inc.

[jdwky]

I fixed that issue recently, not sure which version though. Until now, you have to manually freeze the KTL version to a specific number. If you left it blank it would start looping. Now, leaving it blank will aut-update to the lastest on a manual refresh from the user, instead of a firced refresh from the code. You can still manually force your app version updated though. So you get the best of both worlds.

Just so I'm clear, are you talking about leaving it blank here in the App Settings Object?

Or, in the javascript code?

Thanks!

[cortexrd]

I am referring to the KTL Loader:

[jdwky]

Perfect, got it. My loader has always been set up that way. But for some reason most users were getting the infinite update-version loop one day last week...

[cortexrd]

BTW, I noted a big problem with your scren shot here. The value is wrong.

It should have exactly this format:

And is supposed to be generated automaically by pressing the BROADCAST NOW button, if you're setup this way. Never edit this value manually, let the KTL do it.

[cortexrd]

This bug was fixed in v0.36.3 on Jan 5, 2026. Hope I won't see this again! Let me know...

[cortexrd]

🎉 Introducing the KTL Discovery Hub!

Hey KTL Community!

We're excited to share something new with you - the KTL Discovery Hub is now live!

What is it?

Think of it as a companion to our GitHub Wiki - not a replacement, but a powerful complement. While the GitHub Wiki remains your go-to for detailed documentation, the Discovery Hub makes it easier to discover what KTL has to offer.

Imagine browsing 200+ KTL features in one organized grid, each with its title, description, documentation links, live demos, and video tutorials - all in one place. Plus, we're transforming real-world usage data into community insights, so you can see what's trending, what's popular, and discover features you might have missed.

Why should you participate?

Here's the thing - your input is shaping the future of KTL. We're actively planning KTL Next-Gen (KTL-NG), and understanding which features you actually use and love is crucial for deciding what gets enhanced, optimized, and carried forward.

It's super simple: just click "Send KTL Usage" in your KTL Developer Tools (requires v0.35.1+). One click, fully automated. Done.

"But what about my data?"

We get it - privacy matters! The Discovery Hub homepage has a detailed breakdown of exactly what's sent, but here's the short version:

✅ What's sent: Feature usage, keywords, config settings, app metadata
🔒 What stays private: All emails and IDs - used ONLY for internal calculations, never shown to anyone
👀 What's public: Aggregated stats, trends, and insights (plus the last 8 chars of your App ID so you can find yourself in the rankings if you're curious!)

No business data. No sensitive info. Just usage patterns that help the community discover what works.

Visit the KTL Discovery Hub and send your usage data. Every submission helps us build a better KTL that serves the real needs of our community.

Thanks for being awesome! 🙌

Normand D.

[cortexrd]

📢 User Filters Migration Coming in KTL v0.37.0

Hey everyone!

Just a heads up that KTL v0.37.0 is dropping tomorrow with an important change to how User Filters are stored.

What's Changing?

User Filters will now be saved directly in User Prefs instead of using separate database tables. This simplifies the architecture and improves sync reliability across devices.

Automatic Migration

When you update to v0.37.0, KTL will automatically migrate your existing filters to the new storage format. The transition should be seamless, but...

Just in Case...

If you're currently using User Filters tables, you may want to export them for archival purposes before updating. Better safe than sorry!

Setup Required

To enable the automatic migration, you'll need to have User Prefs configured in your app. If you haven't set this up yet, check out the documentation:

• User Filters Overview
• Migration Procedure

Questions? Drop a comment below!

Norm

[cortexrd]

🎨 New Feature coming tomorrow in KTL v0.37.0: Theme Editor & Dark Mode Support

Hey everyone!

Excited to share that KTL now has a built-in Theme Editor with full dark mode support!

What's New

Theme Editor - A visual editor that lets you customize colors across your app in real-time. You can tweak:

• Background colors
• Headers, tables, forms
• Text and link colors
• And much more

Dark Mode - Finally! Your users can switch to a dark theme that's easy on the eyes, especially for those late-night data entry sessions.

Dual Logos - Upload separate logos for light and dark themes. The right one shows up automatically based on the active theme.

Flexible Deployment

• Per-user: Users can pick their own theme and it saves to their preferences automatically
• App-wide: Developers can set a default theme for everyone
• Export/Import: Created a theme you love? Export it and share with others, or import themes from the community

How to Access

• From your My Preferences page (see setup instructions)
• Or press Shift+T anytime when focus is not on an input field (just click on the app's background first)

Getting Started

Check out the Theme Editor:

And a sample of what an app can look in Dark mode!

Would love to hear your feedback and see what themes you come up with!

Norm

[cortexrd]

📢 What's New in KTL v0.39.1 (since v0.34.0)

Tonight, the KTL has grown to an impressive 30,000+ lines of code! 🎉

A lot has happened since v0.34.0. Here's a summary of all the new keywords, options, and major features you might have missed.

---

New Keywords

_tags: Add/Remove Tags

Enables bulk tag management directly in grid views. Add or remove tags from multiple selected records at once using a dropdown interface.

This keyword can help overcome the limitation often encountered when you can't have a logical OR operator in display/page rules and field filters. Use tags to aggregate or segregate records in ways that Knack's native filtering doesn't support.

_tags
_tags=Categories
_tags=field_456

_dttip: Data Tooltip

Display data from hidden columns as tooltips on other columns. Perfect for showing additional information without cluttering the grid.

_dttip=Notes, Product Name
_dttip=Notes, Product Name, Details, show
_dttip=[Notes, Product Name, Notes], [SKU, Product Name, SKU, show]

_mmb: Move Menu Buttons

Relocate menu view buttons to another view's title bar or submit row. Great for cleaner layouts.

_mmb=Customer Details
_mmb=Order Form, submit, left

_df: Disable Field

Disable specific fields in forms.

_df
_df=Email, Phone Number
_df=field_123, field_456

_string: String Concatenation

Concatenate field values and literal text, then inject (replace if existing) the result into any element.

_string=[Project #], [ - ], [Project Name], [ktlTarget, $(`#${viewId} .kn-title`)]

_bm: Bookmarks

Add a bookmarks feature to your app. Users can save, rename, and organize page bookmarks with cross-device sync via User Prefs.

_bm
_bm=all, top

_ask: Confirmation Dialog

Prompt users with a confirmation dialog before executing action links. Prevents accidental clicks.

_ask
_ask=[Delete, Delete this record?, Yes, No]

_sfv: Set Field Values

Set default values in form fields on load, with support for dropdowns, radio buttons, and reference values.

_sfv=Status, Active
_sfv=[Status, Active], [Priority, High]
_sfv=[Customer ID, ktlRefVal], [ktlRefVal, CID, Customer Details]

---

Theme Editor & Dark Mode

The Theme Editor gives users full control over their app's appearance with dark mode support, color presets, saved themes with cross-device sync, and the ability to share themes via export.

For full details, see the Theme Editor Documentation.

_theme=headerColor, #2d3748
_theme=[headerColor, #1a365d], [darkLogo, https://example.com/logo-light.png], [lightLogo, https://example.com/logo-dark.png]

---

Enhanced Developer Search

The KTL Search tools have been completely unified and enhanced:

• type: filter: Filter results by view type, object type, or element type (e.g., type:grid, type:form)
• Unified search: One tool to search keywords, fields, views, objects, and more
• Improved UI: Help popup, better result formatting, modernized window behavior (drag, resize, close)
• Deep nested search: Now searches all nested attributes - very usefult to find _tags among others.

---

New Keyword Options

ktlEmpty (for ktlCond)

Check if a Grid, List, or Search view has zero records. Supports Universal Selector formats.

_hv=ktlCond, is, ktlEmpty
_hv=ktlCond, is, ktlEmpty, view_449
_cls=[ktlHidden], [ktlCond, is, ktlEmpty, My Grid Title], [ktlTarget, ...]

ktlCond support expanded

• Now works with _style for conditional styling
• Improved support for radio buttons and checkboxes in forms
• Works with _req for multi-choice form fields

Multiple instances support

• _ni now supports multiple instances
• _sfv supports multiple instances

---

Developer Tools Improvements

• Keyboard shortcuts in Dev Popover (when pressing ctrl+shift while hovering around): Press V/S/F/O to copy View/Scene/Field/Object IDs
• PIN icon: Disable auto-close on the dev popover when you need it to stay open
• Find Scene References: New icon in Dev Popup to find all references to the current scene
• Ctrl+Shift+F: Opens KTL Dev Tools and Search, or re-opens last search results

---

Other Notable Improvements

• KTL Discovery Hub: Official release for community keyword sharing. PLEASE GO USE IT!! We only have 13 entries :( Visit the KTL Discovery Hub
• Bulk Operations: Ctrl+click toggle for master checkbox, improved reliability
• User Prefs Sync: Auto-migration from User Filters table, better localStorage/database sync
• Sticky Columns (_stc): Many fixes for dark theme, scrolling, window resize
• _ro: Now supports chosen dropdowns with 500+ entries
• _req enhancements: Support for Image and File field types, highlightEmptyFields flag
• _lbl replacements: Dynamic text substitution support
• IoT/Kiosk improvements: Better watchdog, multi-tab support, auto-login

---

Resources

• Full Changelog
• Keywords Documentation
• KTL Configurator
• KTL Discovery Hub

---

Upgrade today and explore these new features!

Enjoy,
Normand D.

[hwrainbird]

I'm a big fan of this format of grouping the biggest features :) Thanks again for the great work you're doing! Do you think it would be possible to modify or allow customisations to the *Shift + Ctrl* shortcut? I use a lot of shortcuts that include Shift and Ctrl and the Dev Popup appears every time. Perhaps *Shift + Ctrl + D *or Shift + Ctrl + Space* *? Thanks, Harry Rainbird ***@***.*** Rainbird Applications

[cortexrd]

Hi Harry,

To be honest, I have the same problem too! I will do the same as I did for the Theme Editor and add a Hotkey configurator.

Actually, even better: have one centralized dialog in the My Preferences page, where you could set up several hotkeys, as I'm sure I can find a few more places that could use them.

Norm

[cortexrd]

📢 KTL v0.40.0 Released

A quick update with developer experience improvements and bug fixes.

---

What's New

Theme Editor: Menu Buttons Background Color

Theme Editor has a new color picker for Menu Buttons Bg.

Centralized Hotkey Settings

Dev tool hotkeys are now managed from a single location with full theme support. Customize your keyboard shortcuts for KTL Search, Theme Editor, and other dev tools in one place.

---

Bug Fixes

• ktlLoggedInAccount in ktlCond: Fixed issue with getting the Name field
• Escape key handling: Improved reliability when closing dev tool windows
• KTL Search: Enhanced ID lookups and better keyword display

---

Resources

• Full Changelog
• Keywords Documentation
• KTL Discovery Hub — Share your keyword discoveries!

---

Happy development!

Normand D.

[kpmcdona63]

Thank you for all of the great work that you do, Norm! You are an invaluable asset to the Knack community.

…

-- Kevin P. McDonald Portfolio Project and Process Management Analyst OCC | Office of Information Technology North Carolina State University t | 919 513 1409 email | ***@***.***

On Thu, Jan 29, 2026 at 2:05 AM Cortex R&D Inc. ***@***.***> wrote: 📢 KTL v0.40.0 Released A quick update with developer experience improvements and bug fixes. ------------------------------ What's New Theme Editor: Menu Buttons Background Color Theme Editor has a new color picker for Menu Buttons Bg. Centralized Hotkey Settings Dev tool hotkeys are now managed from a single location with full theme support. Customize your keyboard shortcuts for KTL Search, Theme Editor, and other dev tools in one place. image.png (view on web) <https://github.com/user-attachments/assets/8e80d6d3-b07c-4dbb-948c-ea2572fd0e9b> ------------------------------ Bug Fixes - *ktlLoggedInAccount in ktlCond*: Fixed issue with getting the Name field - *Escape key handling*: Improved reliability when closing dev tool windows - *KTL Search*: Enhanced ID lookups and better keyword display ------------------------------ Resources - Full Changelog <https://github.com/cortexrd/Knack-Toolkit-Library/blob/dev/CHANGELOG.md> - Keywords Documentation <https://github.com/cortexrd/Knack-Toolkit-Library/wiki/Keywords> - KTL Discovery Hub <https://ctrnd.knack.com/ktl-hub#home> — Share your keyword discoveries! ------------------------------ Happy development! Normand D. — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BTXDFVBEZAXQI4LNDWBAM5D4JGWMZAVCNFSM6AAAAAAZATU3JCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNRTGY3DAMI> . You are receiving this because you are subscribed to this thread.Message ID: <cortexrd/Knack-Toolkit-Library/repo-discussions/47/comments/15636601@ github.com>

[cortexrd]

_arh: New [identifier] parameter — Fix for blank Identifier in Record History

If you've been using the _arh keyword, you may have noticed that the Identifier field in your Record History entries sometimes shows up blank.

This happens because _arh assumes the Identifier is the Display Field of the object.

However, the Display Field is often a formula Text field (e.g. combining a name with an ID number), and since formula fields are read-only, they cannot be added to an Add/Edit form. When the field isn't present in the form, the record data returned on submit simply doesn't contain it — resulting in a blank Identifier.

The solution: [identifier]

A new optional group parameter lets you explicitly specify which field to use as the Identifier. There are two approaches:

1. Add a Details view to the page that includes your Display Field, and point _arh to it. You can hide it with _hv if you don't want it visible to users.

2. Use a specific field already in your form that clearly identifies the record being processed (e.g. a name or serial number field).

Syntax

The parameter uses Universal Selectors, so you can reference fields and views by ID or by label:

_arh=[identifier, field_123, view_456]

_arh=[identifier, Client ID Name, Client Details View]

_arh=[identifier, field_123] — when the field is in the current view

This can be combined with all existing parameters as usual:

_arh=[context, Client Updates], [identifier, Client ID Name, Client Details View], [expiry, 90d]

Documentation: _arh docs

Enjoy,

Normand

[cortexrd]

📢 What's New in KTL v0.41.0 Release

FIRST... A big thank you to everyone who has participated in the KTL Discovery Hub — your submissions are greatly appreciated! If you haven't submitted your KTL usage yet, please take a moment to do so. Understanding how KTL is being used across different apps is very important to me and helps shape the library's future.

Highlights

New: _legend keyword — Auto-Generated Display Rules Legends

Ever wondered what those icons and colors in your grid columns mean? The new _legend keyword automatically reads Display Rules from the Knack Builder and generates visual legends right on the column headers.

Three modes:

• Per-view: Add _legend to any view title/description
• Global: Add _legend=all to enable legends on every table and search view across all pages
• Custom text: Override auto-generated descriptions with human-friendly text:
  _legend=[Status], [Pending Approval], [Approved and Ready], [Overdue]

Features:

• Icon chips show the actual Font Awesome icon as a white glyph on the rule's colored background
• Color swatches for background-color and text-color rules
• Merges seamlessly with existing _ttip tooltips — one icon, combined content
• Touch-compatible: tap to toggle, tap outside to dismiss
• Handles boolean fields cleanly (shows "Done" instead of "Done is true")
• Supports date-relative criteria formatting

New: ktl.api Module

A centralized Knack API helper for robust record management:

• CRUD operations with pagination and adaptive concurrency
• Batched record creation with rate limiting
• Automatic retry with Retry-After header support
• 429 rate limit tracking and summary logging

Bulk operations (_tags, Bulk Duplicate) have been refactored to use ktl.api for improved reliability and throughput.

Other Changes

• _tags: Bulk ops checkboxes now show regardless of user roles
• _hf: Now hides fields in all view types (grids, forms, details, lists)
• _cfv: Fixed off-by-one error in column index selectors
• Utility bar: Pause Auto-Refresh moved from floating checkbox to utility bar; flashing red indicator when Hidden Elements is active

Upgrade Notes

Drop-in replacement — no configuration changes required. The _legend keyword is opt-in: add it to view titles/descriptions where you want legends to appear, or use _legend=all for global coverage.

Enjoy,
Norm

[cortexrd]

📢 What's New in KTL v0.42.3 (since v0.41.0)

✨ Featuring: Knavigator Integration

A big thank you to Ivan Jovanovic for creating Knavigator — an essential tool for Knack developers. It can now be launched directly from the live app: click the magnifier icon in the Dev Info Popup and it opens Knavigator straight to the hovered item, showing all its details in one place.

---

Here's a summary of all the new keywords, options, and major features since the last announcement.

---

Enhanced Keywords

_qt: Quick Toggle — Confirm & Mode

Quick Toggle now supports two new parameter groups:

• confirm: Prompt users before toggling with a customizable message
• mode: Restrict toggling to one direction only (f2t = false-to-true, t2f = true-to-false)

_qt=[green, red], [confirm]
_qt=[green, red], [confirm, Are you sure you want to activate?]
_qt=[green, red], [mode, f2t]
_qt=[green, red], [confirm, Please confirm], [mode, f2t]

A quickToggle event is also dispatched for custom integrations.

_dv: Disable View — ktlCond Support

_dv now supports ktlCond with the special ktlLoggedInAccount value for conditional view disabling based on the logged-in user.

_dv=[ktlCond, is, ktlLoggedInAccount, field_123]

_cpyfrom: Major Improvements

• Add optional refresh parameter to force destination view refresh
• Add count display mode in ktlMsg for progress via infoPopup
• Fix duplicate PUT requests, connection field copy, and multi-instance state handling

---

Page Integrity Monitor

New automatic monitoring system that continuously checks HTML structure to detect partial page loads or server errors. Auto-retries before forcing a page reload — solves unattended kiosk devices hanging on white screens or incomplete views.

---

Dark Theme Expansion

• Highcharts report charts: Full dark theme support
• Virtual keyboard: Dark theme styling and html background fix
• Dev tools: Consistent dark theme across all developer windows
• Theme Editor: Fix false "Discard unsaved changes?" prompt on first use

---

Developer Tools Improvements

• Knavigator integration: Click the magnifier icon in the Dev Info Popup to open Knavigator straight to the hovered item
• Enhanced search: Keyword options support and not-found feedback in dev tools search
• View IDs hotkey (Alt+I) and improved keyboard handling
• Z-index management: Alt+S, Alt+X properly bring dev tool windows to front
• Show Menu Buttons: Background color picker for all app designs

---

ktl.api Improvements

• Simplify method signatures by removing refreshViews parameter
• Unify bulk batch execution and standardize progress and logging
• Fix findRecords filter merge to preserve caller boolean logic
• Bulk write defaults: continueOnError now defaults to true
• Enforce plain-object options across all write methods

---

Checkbox & Bulk Operations

• Unified addCheckboxesToTable function with customizable onRowChange and onMasterChange callbacks
• Shift-click for checkbox range selection in tables
• Better state reset when changing scenes

---

Other Notable Fixes

• Fix fixTableRowsAlignment with schema-based positional rebuild (handles grouping columns and hideColumns)
• Fix CSS specificity issues with inline edit background and grid left borders
• Fix waitViewDataReady race condition returning empty data
• Prevent multi-tab version toggling in service worker update log
• Add null guards for getKtlAddOnsDiv callers

---

Resources

• Full Changelog
• Keywords Documentation
• KTL Configurator
• KTL Discovery Hub

---

Enjoy,

Normand D.

[cortexrd]

📢 What's New in KTL v0.42.7 (since v0.42.3)

✨ New: _cg keyword — Collapsible Groups

Grid and search views with grouping now support collapsible group rows. Each group header gets a toggle button (+/−) to collapse or expand its records.

Modes:

• Per-view: Add _cg to a view title/description to enable on that view only
• Global: Add _cg=all to enable on every grouped table and search view across the app. Only needs to be placed once in any view of any page, typically the Home page
• Start collapsed: Add collapsed parameter to have groups closed by default

Features:

• Toggle button respects theme colors automatically
• Collapsed state is saved to userPrefs and synced to the database, so it persists across sessions and devices
• User preferences always take precedence over the keyword's default state
• Supports ktlRoles for role-based access control

Examples:

_cg
_cg=collapsed
_cg=collapsed, all
_cg=[collapsed, all], [ktlRoles, !Customer]

---

Bug Fixes & Improvements

• Bulk ops: Fix viewId fallback — pass viewId to processBulkEdit/processBulkDuplicate to prevent undefined object name
• Auto-login: Fix issue requiring repeated auto-login attempts
• Tooltip selector: Fix querySelector failing on jQuery pseudo-selectors like :textEquals — reuse jQuery object instead
• Inline editing: Skip cell-edit click handler on views without inline editing enabled
• KTL Search Tool: Fix parameterless keywords being reported as "not found"
• clog: Add caller tracing via ktl.core.logCaller
• findFieldWithDescription: Fix null field access with optional chaining

---

Resources

• Full Changelog
• Keywords Documentation
• KTL Configurator
• KTL Discovery Hub

---

Enjoy,

Normand D.