Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot split the view of an opening template #1803

Closed
tanbt opened this issue Jun 20, 2018 · 2 comments
Closed

Cannot split the view of an opening template #1803

tanbt opened this issue Jun 20, 2018 · 2 comments
Labels
bug Stale Inactive issue marked for closing

Comments

@tanbt
Copy link
Contributor

tanbt commented Jun 20, 2018

Steps to reproduce

  • Open a template
  • Split the editor vertically or horizontally

Actual behavior

The splitted editor is empty.

[1998269]  ERROR - tor.impl.FileEditorManagerImpl - Looks like idPropertyChangeListener already exists. Double initialization? 
java.lang.IllegalStateException: Looks like idPropertyChangeListener already exists. Double initialization?
	at com.vaadin.designer2.services.companionfile.FlowCompanionFileService.addIdPropertyChangeListener(FlowCompanionFileService.java:59)
	at com.vaadin.designer2.services.companionfile.FlowCompanionFileService.initialize(FlowCompanionFileService.java:43)
	at com.vaadin.designer2.intellij.editor.flow.FlowEditorProvider.initializeCompanionFileService(FlowEditorProvider.java:119)
	at com.vaadin.designer2.intellij.editor.flow.FlowEditorProvider.createAndConfigureEditor(FlowEditorProvider.java:111)
	at com.vaadin.designer2.intellij.editor.AbstractDesignerEditorProvider.createEditor(AbstractDesignerEditorProvider.java:52)

Expected behavior

The editor is splitted and works as usual.

IDE, Designer and OS version

IntelliJ, Designer 3, Windows

References

@stale
Copy link

stale bot commented Aug 15, 2019

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a few things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

  • Check if the issue is still valid for the latest version. There are many duplicates in our issue tracker, so it is possible that the issue is already tackled.
  • Provide more details how to reproduce the issue.
  • Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
  • Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
  • If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

@stale stale bot added the Stale Inactive issue marked for closing label Aug 15, 2019
@stale
Copy link

stale bot commented Feb 11, 2020

The issue was automatically closed due to inactivity. If you found some new details please comment on the issue so that maintainers can re-open it.

@stale stale bot closed this as completed Feb 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Stale Inactive issue marked for closing
Projects
None yet
Development

No branches or pull requests

2 participants