[
http://opensource.atlassian.com/projects/hibernate/browse/HBX-377?page=all ]
Max Rydahl Andersen closed HBX-377:
-----------------------------------
Fix Version: 3.2beta7
(was: 3.2LATER)
Resolution: Fixed
the * now reflect the correct state and seems to work as expected.
Can't save HQL Scratchpad
-------------------------
Key: HBX-377
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HBX-377
Project: Hibernate Tools
Type: Bug
Components: consoleconfiguration
Versions: 3.1alpha5
Environment: Windows XP, Eclipse 3.1
Reporter: Dan Bradley
Priority: Minor
Fix For: 3.2beta7
There is no way to save a non-empty HQL Scratchpad or otherwise mark it non-dirty. To
reproduce:
- Open a scratchpad window, it's non-dirty.
- Enter anything into it, it's now dirty, as shown by the asterisk in front of the
name on its tab.
- Try to save it, it doesn't save, and its dirty state does not change.
- Many Eclipse tasks will now ask you to save it before proceeding
- Try to close it, Eclipse prompts you to save. Say no and the editor closes. But say yes
and it also closes also without saving.
More broadly, I'm not sure about the UI approach. What does it mean to save a
scratchpad? Do I have to save it to a file? It's a scratchpad after all, not something
I want to keep around. But I do want multiple scratchpads to be available. If I save it
and it uses some hidden temporary file, that seems like an abuse of the Eclipse editor
window. Maybe the scratchpad should be an Eclipse view that can be embedded in the Console
Perspective, and which doesn't track a dirty/non-dirty state?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira