|
Bugzilla – Full Text Bug Listing |
| Summary: | Mouse cursor should indicate when trying to drop something in an illegal location | ||
|---|---|---|---|
| Product: | [Identity Manager] Identity Designer | Reporter: | Tim Pew <tpew> |
| Component: | Modeler | Assignee: | Lee Lowry <llowry> |
| Status: | VERIFIED WONTFIX | QA Contact: | Tim Pew <tpew> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | Keywords: | Provo |
| Version: | 1.0.0 Designer | ||
| Target Milestone: | 1.1 M1 | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Integration Test | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Tim Pew
2004-12-09 23:30:01 UTC
Transferred from Remedy DEFECT000388675. Status when transferred: Fixing/Work in Progress I've spent a tremendous amount of time trying to figure out why Eclipse behaves this way, to no avail, and I've sent a question to the message group. In the meantime, I've put educational prompts in at drop time so at least the situation is handled (and in someways, it's actually better). I believe the current behavior and educations prompts are good enough for FCS; meanwhile, hopefully I'll get more insight from the Eclipse people on how to resolve this. Marking as resolve Later. Beyond FCS Reopening bugs for determination of fixing bug or adding enhancements for Milestone 1.1. Bill Large effort, small gain. Open so we can close. I believe the education prompts are more valuable than the cursor in this case. Sometimes the cursor is sufficient, but this the perfect opportunity to explain to the user why it can't drop and then they get to learn the mindset of DirXML systems. Based on comments above, changing fixed in milestone from "Future" to 1.1M1 |