Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4 (.NET CLR 3.5.30729) Build Identifier: M20090917-0800 I'm using the OCL console frequently and I am really missing some history function like the unix bash has, for instance. So I coded one and I think it is really helpful especially when writing long expressions. Yes, it is all my work; and yes, you may integrate it into the existing example. Instructions: 1. Apply the attached patch to the org.eclipse.emf.ocl.examples.interpreter project. 2. Run the OCL Console and explore the history with pageUp and pageDown Reproducible: Always
Created attachment 151299 [details] Patch for history in OCL console
Is there any reason to use PAGE_UP/DOWN rather than ARROW_UP/DOWN? Maintenance of the history seems confused. Why does page up both remove and add to history? Surely the history grows with each CR only?
(In reply to comment #2) > Is there any reason to use PAGE_UP/DOWN rather than ARROW_UP/DOWN? Yes. In case of multi-line expressions (shift-enter), ARROW_UP/DOWN are used to navigate between the lines. An alternative would be SHIFT + ARROW_UP/DOWN? > > Maintenance of the history seems confused. Why does page up both remove and add > to history? Surely the history grows with each CR only? Let us assume the history contains several items, and you are currently writing a new expression. Browsing the history will not destroy your current expression but let you return to it (e.g. if you want to look up an old expression and then returning to the expression your are currently writing).
*** Bug 260641 has been marked as a duplicate of this bug. ***
Committed to CVS HEAD. I'm not sure what is happening on the revised example, so I cannot be sure whether this will get 'lost' and we may need reminding of its utility. Thanks anyway.
Closing after over 18 months in resolved state.
