| Summary: | NPE in XYLayoutEditPolicy#getConstraintFor | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] GMF-Runtime | Reporter: | Svyatoslav Kovalsky <kovalsky> | ||||
| Component: | General | Assignee: | Aurelien Pupier <apupier> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | an.mayer, apupier, markusb | ||||
| Version: | unspecified | Flags: | apupier:
juno+
|
||||
| Target Milestone: | 1.6.0 | ||||||
| Hardware: | PC | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Svyatoslav Kovalsky
Rectangle rect = (Rectangle) super.getConstraintFor(request, child); Rectangle cons = getCurrentConstraintFor(child); if (request.getSizeDelta().width == 0) rect.width = cons.width; its reasonable to expect that rect != null However there are reasonable usecases when getCurrentConstraintFor(child) == null, causing NPE here Created attachment 205453 [details]
trivial - fixes NPE
Is there an ETA when this fix will be available? Which GMF/Eclipse version can we expect this fix to be in? Thanks Markus Hi, I just commited the fix. If the tests are running well also on server it will be part of Eclipse Juno. regards, tests passed Thanks, Aurelien |