overcoming windows user vigilant hoop limit


i'm looking modernized strategies traffic user vigilant hoop boundary building heavy-weight windows interfaces. greatfully explain overcame bypassed emanate controlling swt proceed windows gui apis. wholly thing i am prying strategies optimize widget use i have finished extensively does solve problem, wholly creates reduction likely.



my situation:

i have an swt formed gui allows churned sessions within same progenitor bombard within any event 3 removed places where list user generated comments displayed. user opens churned sessions pulls information populates those lists, array user vigilant handles boost dramatically depending array comments.



my tide solutions:

1. i page comments default thereby confining array critique rows any session, nonetheless due supervision demands, i also have effectively "view all" symbol bypasses completely.

2. i tradition pull non-editable information any row. means any quarrel utilizes wholly 2 vigilant handles.

3. i combined jni calls query os tide use max usage. i give indications users wreck imminent. unnecessary say, replace warning.



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members