Bug 312616 - [Navigation] F3 should jump to the best match
Summary: [Navigation] F3 should jump to the best match
Status: CLOSED FIXED
Alias: None
Product: M2T
Classification: Modeling
Component: Xpand (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Darius Jockel CLA
QA Contact:
URL:
Whiteboard:
Keywords: ui
Depends on:
Blocks:
 
Reported: 2010-05-12 09:35 EDT by Sebastian Zarnekow CLA
Modified: 2017-10-31 10:57 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Zarnekow CLA 2010-05-12 09:35:25 EDT
Steps to reproduce:

1) Create new xpand project (EMF sample)
2) Add the following extensions to the Extensions.ext

Model model(Entity this) :
	eContainer;

Model model(Datatype this) :
	eContainer;

3) Open the file Check.chk and have a look at 
context Entity ERROR "Duplicate entity "+name :
	model().entities().select(e|e.name==name).size==1;

4) Navigate via F3 from model() to model(Type) instead of model(Entity).
5) Change the order of the extensions in Extensions.ext and move model(Datatype) to the top.
6) Use F3 on in the check-file. You'll navigate to model(Datatype) which is wrong.
7) Try to navigate via Ctrl+Click from model() to its definition. You'll get three proposals while it could be statically computed that model(Entity) is the only one to be called from the check.
Comment 1 Darius Jockel CLA 2014-05-09 03:56:06 EDT
Fixed in V2.0.0
Comment 2 Eclipse Webmaster CLA 2017-10-31 10:46:21 EDT
Requested via bug 522520.

-M.
Comment 3 Eclipse Webmaster CLA 2017-10-31 10:57:36 EDT
Requested via bug 522520.

-M.