Community
Participate
Working Groups
Created attachment 251017 [details] The expected behavior When trying to edit a value .e.g the name of an element in the advanced tab in the properties view the widget for that value is visually changed to "edit mode". That is, the widget isn't showing any changes made until Enter is pressed. See the attached images for actual and expected behavior. This is most likely a GTK3/SWT issue. --- Ubuntu 14.04 / Mars M5 / Papyrus 1.1.0.201502230616 eclipse.buildId=4.5.0.I20150203-1300 java.version=1.7.0_76 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.committers.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.committers.product
Created attachment 251018 [details] The actual behavior
I don't understand, even with the attachments. Do you mean that the property editor does *not* visually enter edit mode? That you type blindly, not seeing the text that you're typing until you press Enter?
(In reply to Christian W. Damus from comment #2) > I don't understand, even with the attachments. > > Do you mean that the property editor does *not* visually enter edit mode? > That you type blindly, not seeing the text that you're typing until you > press Enter? Exactly! Thanks for clarifying.
Gosh, I was half-hoping that I was joking. That's not a nice experience! It does seem to be a GTK3 integration thing. I get the expected edit behaviour on Mac. Could you do me a favour and see whether an EMF-generated editor for some Ecore model has the same behaviour? (in fact, the *.ecore editor itself is a good test) I doubt that this is in code that Papyrus can influence.
(In reply to Christian W. Damus from comment #4) > Gosh, I was half-hoping that I was joking. That's not a nice experience! > > It does seem to be a GTK3 integration thing. I get the expected edit > behaviour on Mac. > > Could you do me a favour and see whether an EMF-generated editor for some > Ecore model has the same behaviour? (in fact, the *.ecore editor itself is > a good test) I doubt that this is in code that Papyrus can influence. Yes it has, and actually to might be even lower,i.e. a SWT thing. https://bugs.eclipse.org/bugs/show_bug.cgi?id=436324 Seems like GTK3 and SWT are not best friends https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=gtk3%20swt /Patrik
Whoa, indeed. OK, so it seems like the resolution of this bug is "Not Papyrus." I'm not sure what the Papyrus team's procedure is for that ...
Please raise the prio to, at least, major.
*** This bug has been marked as a duplicate of bug 438505 ***
The Eclipse Platform GTK3 bug has been fixed, per comment 8. Patrik, would you be able to confirm this for Papyrus? (given that you have the requisite test environment). Thanks
(In reply to Christian W. Damus from comment #9) > The Eclipse Platform GTK3 bug has been fixed, per comment 8. > > Patrik, would you be able to confirm this for Papyrus? (given that you have > the requisite test environment). Thanks You will need tonight's Eclipse build or later, it should be listed as I20150512-2000 when it's available here: http://download.eclipse.org/eclipse/downloads/
AS I wrote in bug 461041, this still doesn't work even with bug 438505 fixed.
Fixed with https://git.eclipse.org/r/47920.
