Urgent.News

What's breaking now, across thousands of outlets.

Tech

Uniface 10 field triggers - leaveField compiles, but loseFocus is what runs

A customer app built in Uniface 10 got a quick entry form: while the user moves from field to field, the form tidies names, checks the e-mail address, fills in the city from the postal code and lists similar customers. All of that runs in field triggers. The first version did nothing at all, and the compiler did not complain. Tested with Rocket Uniface 10.4.03 Community Edition (10.4.03.021) on…

A customer app built in Uniface 10 featured an entry form that automatically tidied names, checked e-mail addresses, filled in cities from postal codes, and listed similar customers as the user moved from field to field. This functionality relied on field triggers, with the first version running smoothly despite the compiler's reluctance to accept the trigger name leaveField.

Tested on Rocket Uniface 10.4.03 Community Edition (10.4.03.021) for Windows, the issue arose when the trigger failed to execute. After some investigation, it was discovered that Uniface 10 had renamed the interactive field triggers, with the one that fires when a cursor leaves a field now being called loseFocus. The original trigger, leaveField, was not among them, yet the compiler still accepted it, allowing it to appear in the compiled form but still not run.

To ensure a trigger runs, it's essential to check its name first. In the case of the postal code field, the trigger was renamed to loseFocus, and the code within called various entry functions to validate and process the data. The issue of the tag field failing to show suggestions on double-click was also addressed, with the solution involving setting the DblClk property to Detail.

It's crucial to note that field triggers are part of the XML export and not part of the component script, so tools that only inspect the component script may miss them. To avoid confusion, it's recommended to use the proper Uniface 10 trigger names: loseFocus, getFocus, validate, detail, and valueChanged.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Your Contact Form Says Thanks, Then Loses the Lead. Here Is a Next.js Handler That Cannot Drop One

Picture the failure mode that worries me most on a service business site. A homeowner fills out the contact form, clicks Submit, and sees a green "Thanks, we will be in touch." Behind that message…

  • Contact forms are critical for service-based websites to capture leads.
  • Failure to store submissions first can lead to lost leads and false expectations.
  • Storing leads in controlled storage before notifying third-party services prevents silent loss.

What can happen after a payment platform already received your payout

A factual account of a USD 330 hold, what freelancers can do next, and why I built a small awareness site with open comments.

  • Freelance freelancer's USD 330 payout held after receipt by Skydo on Nov 13, 2026
  • Payment marked received but delayed due to routine due diligence checks on Nov 16
  • Additional document requests and delayed release keep payout held until Nov 17

How I Cut a Days-Long Malware-Scanning Build to Under an Hour

A build that used to take days of console work now takes one Terraform apply, in under an hour. And when the policy changes, it no longer means a rebuild.

  • Multi-day malware scanning reduced to under an hour using Terraform
  • GuardDuty Malware Protection scans new objects in landing bucket
  • Terraform module enables easy deployment in shared or individual enclave accounts

More from Monday 16 November →