History | Log In     View a printable version of the current page.  
Issue Details (XML)

Key: SDK-11272
Type: Bug Bug
Status: Closed Closed
Resolution: Not a Bug
Priority: B B
Assignee: Joan Lafferty
Reporter: Court Shrock
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Flex SDK

DragManager throws null object reference when modules have draggable components but the loading application does not have any draggable components

Created: 06/12/07 07:39 PM   Updated: 08/28/07 12:37 PM
Component/s: Drag and Drop
Security Level: Public (All JIRA Users )

File Attachments: 1. File ModuleDragTest.air (1.26 Mb)
2. Zip Archive ModuleDragTest.zip (1.68 Mb)

Issue Links:
Relationship
This issue relates to:
SDK-9354 [Customer][Wish-Flex] If you add a cu... B Closed
 

Severity: Runtime Error
Reproducibility: Every Time
Discoverability: Medium
Found in Version: SDK Moxie M2 (Beta) - 172357
Milestone: SDK Moxie M3 (Beta 2)
Affected OS(s): Windows - XP
Steps to Reproduce:
Steps to reproduce:
1. run the ModuleDragTest AIR application
2. click either of the DragModule buttons (the app loads the module)
3. click the other DragModule button (the app loads the other module)
4. try to drag any item in the list
 
 Actual Results:
TypeError: Error #1009: Cannot access a property or method of a null object reference.
at mx.managers::DragManager$/get isDragging()[E:\dev\flex_3_beta1\sdk\frameworks\projects\framework\src\mx\managers\DragManager.as:158]
at mx.controls.listClasses::ListBase/mx.controls.listClasses:ListBase::mouseMoveHandler()[E:\dev\flex_3_beta1\sdk\frameworks\projects\framework\src\mx\controls\listClasses\ListBase.as:7731]

 
 Expected Results:
No error
 
 
 Workaround (if any):
in the main application, uncomment the commented section (which adds a drag enabled list child to the main application).
 
 
Language Found: English
Bugbase Id: none
Triaged: Yes
Regression: No
QA Owner: Joan Lafferty
Resolved by: Darrell Loverin
Participants: Court Shrock, Darrell Loverin, Joan Lafferty and Robert Vollmar (Adobe)

Sub-Tasks  All   Open   
 Sub-Task Progress: 

 All   Comments      Sort Order:
Court Shrock - [06/12/07 07:44 PM ]
The runnable AIR file ... the zip has the source

Joan Lafferty - [06/13/07 06:04 PM - edited ]
This seems very similar to bug SDK-9354 where there is odd behavior for custom components on subsequent Tab views. I reproduced the issue outside of an Apollo Application directly in Flex. It happens only with Modules. I changed the modules to custom components and those worked fine.

Sending for Internal Review.

Joan Lafferty - [06/13/07 06:31 PM ]
This also reproduce in our Flex 2.0.1 hotfix build.

Darrell Loverin - [07/24/07 03:58 PM ]
This is the same issue as SDK-9354, except the singleton in this bug is DragManager. The work around is to define DragManager in the parent application of the two modules so that the modules shared the same DragManager class. Adding

import mx.managers.DragManager;
private var dummy:DragManager;

to ModuleDragTest.mxml works around the problem.


Robert Vollmar (Adobe) - [08/28/07 12:37 PM ]
Choosing just one component due to upcoming JIRA changes.