Home » Eclipse Projects » Remote Application Platform (RAP) » Strange behaviour for ComboBox and TabFolder
| Strange behaviour for ComboBox and TabFolder [message #1830412] |
Sat, 25 July 2020 10:30  |
Eclipse User |
|
|
|
Strange behaviour for ComboBox and TabFolder
created standard window(parent TabFolder) with widgets
inside code with widgets, ran ProgressMonitorDialog
.... And Error.
Attention!!!
1.If Change TabFolder to CTabFolder to That's all right!!!!
2. If change Combo to other widget (for example Label) that's all right too and with TabFolder.
I don't understand where is mistake. Combination Combo and TabFolder doesn't work
Dmitry
Error: Error: Operation "create" on target "w2680" of type "null" failed:
Cannot read property 'addEventListener' of null
Properties:
parent = w2669
style = DROP_DOWN
children =
bounds = 0,0,0,0
tabIndex = 1479
visibleItemCount = 30
items = Any,ARCHIVE+BACKUP,RESTORE+RETRIEVE,ARCHIVE,BACKUP,DBBACKUP,DELETE FILESPACE,EXPIRATION,IMPORT+EXPORT,MOVE DATA,MOVE NODEDATA,MIGRATION,OFFSITE RECLAMATION,POOLPRIMUTILGB,RETRIEVE,RESTORE,RECLAMATION,REPLICATION,STGPOOL BACKUP,SHREDDING,TAPE MOUNT
selectionIndex = 0
editable = false
Stack: Error: Operation "create" on target "w2680" of type "null" failed:
Cannot read property 'addEventListener' of null
Properties:
parent = w2669
style = DROP_DOWN
children =
bounds = 0,0,0,0
tabIndex = 1479
visibleItemCount = 30
items = Any,ARCHIVE+BACKUP,RESTORE+RETRIEVE,ARCHIVE,BACKUP,DBBACKUP,DELETE FILESPACE,EXPIRATION,IMPORT+EXPORT,MOVE DATA,MOVE NODEDATA,MIGRATION,OFFSITE RECLAMATION,POOLPRIMUTILGB,RETRIEVE,RESTORE,RECLAMATION,REPLICATION,STGPOOL BACKUP,SHREDDING,TAPE MOUNT
selectionIndex = 0
editable = false
at Object._processError (https://127.0.0.1:5020/rwt-resources/3130/rap-client.js:226:3814)
at Object.processOperationArray (https://127.0.0.1:5020/rwt-resources/3130/rap-client.js:226:924)
at Object.processMessage (https://127.0.0.1:5020/rwt-resources/3130/rap-client.js:226:253)
at Object._handleSuccess (https://127.0.0.1:5020/rwt-resources/3130/rap-client.js:230:3677)
at rwt.remote.Request._success (https://127.0.0.1:5020/rwt-resources/3130/rap-client.js:98:925)
at rwt.remote.Request._onReadyStateChange (https://127.0.0.1:5020/rwt-resources/3130/rap-client.js:98:1596)
at XMLHttpRequest. (https://127.0.0.1:5020/rwt-resources/3130/rap-client.js:7:219)
Debug: off
Request: {"head":{"requestCounter":118},"operations":[["set","w965",{"selection":["w1140"]}],["notify","w965","Selection",{"item":"w1140","button":1,"shiftKey":false,"ctrlKey":false,"altKey":false}],["set","w965",{"focusItem":"w1140","focusCell":0}],["notify","w965","MouseDown",{"x":92,"y":644,"time":360530,"button":1,"shiftKey":false,"ctrlKey":false,"altKey":false}],["set","w1",{"cursorLocation":[92,644]}]]} |
|
| |
| Re: Strange behaviour for ComboBox and TabFolder [message #1862513 is a reply to message #1830416] |
Fri, 08 December 2023 05:50  |
| Eclipse User |
|
|
|
|
I see link to my old post. I don't exactly remember how to decided this problem but it was be releated with initialisation order for widgets before other operations (Especcially with progressbar operations and threads) and there were the problems exacly with combo widget. Why? I don't know. Try check an initialisation data for Combo. Maybe you create Combo in one place but set data for them in other
|
|
|
Goto Forum:
Current Time: Sat Jun 21 03:22:13 EDT 2025
Powered by FUDForum. Page generated in 0.04444 seconds |
Home