Eclipse Community Forums: GMF (Graphical Modeling Framework)

Help

Home

Home » Modeling » GMF (Graphical Modeling Framework) » Problem Saving diagram: URI changing

Show: Today's Messages :: Show Polls :: Message Navigator

Problem Saving diagram: URI changing [message #223085]

Sat, 28 March 2009 11:25

maatari

Messages: 74
Registered: July 2009

Member

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3321087959_2556729
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit

Hi all,

I

Report message to a moderator

Re: Problem Saving diagram: URI changing [message #223093 is a reply to message #223085]

Sat, 28 March 2009 11:36

maatari

Messages: 74
Registered: July 2009

Member

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3321088610_2565344
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit

Hi,
Please find in the following the an example XML file I

Report message to a moderator

Re: Problem Saving diagram: URI changing [message #223121 is a reply to message #223093]

Sat, 28 March 2009 12:43

maatari

Messages: 74
Registered: July 2009

Member

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3321092617_2803282
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit

Hi,

Althought I read all thread on saving issue, I can find a solution nor an
explanation to it. Visibly I need to understand what is happening while
saving. If someone can just explain between saving EMF resource GMF.
Because, more than this,
I found that:

If I remove the save from the workSapceModifyOperation, the problem is
solved but the all editor as a problem of synchronization with the file,
raising null pointer Exception and more or less freezing the application.

I guess that should be the right behavior, but then I don

Report message to a moderator

Re: Problem Saving diagram: URI changing [message #223129 is a reply to message #223121]

Sat, 28 March 2009 19:08

maatari

Messages: 74
Registered: July 2009

Member

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3321115699_3819122
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit

Hi, I just use a trick to solve my issue, by saving the URI right after the
creation of the diagram in a global variable.
Then, I use this URI to open the diagram. Before, I was using the same
global variable referring to the diagram just created to obtain its URI but
only after the workSapcemodify operation was done, but on time to open the
diagram in its editor.

So the issue is solved. I can save delete and etc.... The change a reflected
in both diagram. However, I still have a save issue.
I still can

Report message to a moderator

Re: Problem Saving diagram: URI changing [message #223138 is a reply to message #223129]

Sat, 28 March 2009 22:08

maatari

Messages: 74
Registered: July 2009

Member

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3321126504_4448219
Content-type: text/plain;
charset="ISO-8859-1"
Content-transfer-encoding: 8bit

Hi all,

after several debug related to the documents provider, I realize that, the
RessourceSetInfo, that it obtain has a canBesave variable that always return
false when needed.
Does anyone has already encountered this problem ? Also if you have any
information regarding the ressourceSetInfo and how it works, I

Report message to a moderator

Re: Problem Saving diagram: URI changing [message #223604 is a reply to message #223138]

Tue, 31 March 2009 11:38

Alexander Shatalin

Messages: 2928
Registered: July 2009

Senior Member

Hello Daniel,

Actually the dirty state should be set for diagram editor inside generated
XXXDocumentProvider.ResourceSetModificationListener inner class – see notifyChanged
method implementation. To my understanding the fact that this method is not
working properly means that either used ResourceSet/Resource implementation
is not properly trackingModifications (see ((Resource) value).setTrackingModification(true)
call in the originally generated DocumentProvider) or you’ve used different
ResourceSets in DocumentProvider then one used to load all the diagram elements…
Hope with these pointers you’ll be able to debug forward and find a reason
of your problems.

-----------------
Alex Shatalin

Report message to a moderator

Previous Topic:	browse code source of a GMF application
Next Topic:	Seeking feedback on Google Summer of Code idea implementation details

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 17:24:54 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter