State of Property Editor. And other questions.

[at84]

First of all: Great work!

1. It would be also great if the Property Editor of the SWT Designer would remember its state (its width and the widths of the columns of the properties table).

2. Is it possible for you to add the following functionality: When you a (visual) class with the Designer Editor this Editor maximazes first, so you don't have to do this. It make sense for me, because the Designer Editor is usefull only in this state.
This don't have to be the default behavior, but could be one of the options in the Designer Preferences.

[Eric Clayberg]

1. It would be also great if the Property Editor of the SWT Designer would remember its state (its width and the widths of the columns of the properties table).

The latest v4.3.1 build now does this.

2. Is it possible for you to add the following functionality: When you a (visual) class with the Designer Editor this Editor maximazes first, so you don't have to do this.

Maybe. We'll need to think about that one as it isn't very Eclipse-like.

It make sense for me, because the Designer Editor is usefull only in this state.

Why? Have you considered opening the property pane and palette into separate views?

[Eric Clayberg]

Is it possible for you to add the following functionality: When you a (visual) class with the Designer Editor this Editor maximazes first, so you don't have to do this. It make sense for me, because the Designer Editor is usefull only in this state.

The latest v4.3.1 build includes a new Designer > Editor Layout > Maximize editor on "Design" page activation preference.

This option is available under Eclipse 3.2 only (it uses new Eclipse 3.2 API).

[at84]

The latest v4.3.1 build includes a new Designer > Editor Layout > Maximize editor on "Design" page activation preference.

This option is available under Eclipse 3.2 only (it uses new Eclipse 3.2 API).

Thank you very much!
I think this option simplifies the usage of the editor a bit more.
BUT, realy I don't want to bother you, the functionality is not complete.

I try to describe it better:
- I'm writing some code.
- Than I need the Design Editor. I push [F12].
- Great the Editor maximizes automatically!
- After creating or changing some visual elements, I want to switch bach the code view and push [F12] again.
- But now I have to push [Ctrl][M] to see the other views, because the Source Editor is still maximized (and it wasn't before switching to the Design Editor).

Is it a big problem to add some code that remembers the state before switching to the Design Editor and restores the state after switching back.


---

It make sense for me, because the Designer Editor is usefull only in this state.

Why?

I have some other plugins that help me writing (better) code, but I don't need them, when I'm using the Design Editor.

Have you considered opening the property pane and palette into separate views?

Yes, I've tried it. But I still had to do [F12] to switch to the Design Editor. The new option is much better for me.

[at84]

Thank you very much!

It works great.

[Eric Clayberg]

Is it a big problem to add some code that remembers the state before switching to the Design Editor and restores the state after switching back.

No. The latest v4.3.1 build for Eclipse 3.2 will (optionally) expand the editor when the Design view is selected and restore the editor when the Source view is selected.