Absent Member.
Absent Member.

[archive] Ntf Changed - thread - listbox - 8.1.1

[Migrated content. Thread originally posted on 04 March 2010]

Not sure if anyone can give me some direction here or not. What I have is a listbox (populated with many items) and an entry field on screen used for searching the listbox. Type into the entry and the listbox shortens the list to the matching items. It all works quite well excpet when we started getting into the 10,000 + items in the listbox, users had to wait for it to totally load before they could enter anything in the entry field to narrow the search down.

So I changed the call to load the listbox in a thread and it works well.


With is code the listbox goes on happily loading while the user types in the search field, and with each letter the thread stops and restarts flawlessly under acuthin.exe but not under wrun.exe, I have no idea why, it seems the Screen1-Ef-1-Ex-Ntf-Changed exception doesn't want to fire under wrun32.exe.

And on a side note I swapped the listbox out for a grid and it too works well under thin client, but when you enter text into the entry field under wrun32 it thows a "number required" warning message, like I have the field set to numeric only but I do not...

Maybe my code isn't very sound or someone could give me some direction on how I can do this so that it will work under both wrun32 and acuthin. I know paged listboxes are what i shoudl be going to, but unfortunately they are not very modern looking and users have no way to tell how many records match their search, and frankly they just are not as user friendly as a scrollbar. I have never seen any other application with paged gids/listboxes outside of acu...
1 Reply
Absent Member.
Absent Member.

RE: [archive] Ntf Changed - thread - listbox - 8.1.1

Well after some research I figured out what the problem was. I had a couple of entries in my config file on my local workstation that were not there in the thin client environment that were causing the issue. I can't remember adding them, but I'm sure it was to try and solve some issues with threads at one time or another.

Anyhow it was these two lines causing the issue when run locally. Without them it works as it should and the same as thin client.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.