Okay, I think I've got everything fixed now. I removed the "Close" button, which was causing problems. Now you need to close it with the "x" button (or middle-click on the Simple Script tab if it's docked with other plugins).
If there are still unresolved issues with the docking, post them here.
Note: The SimpleScript.ini file must now be in the plugins\Config folder. If you just have it in the plugins folder, you'll need to move it.
Again, thanks to Zobo for fixing the docking problems.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are problems in the plugin tabs:
- the name of the plugin is not readable on the tab. what I can read is "imple Script"
- if the simple script tab is not active, the simple script tab is empty, no icon
- the simple script tab is taking almost the whole width of the plugin tab bar.
why don't you put only an "S" inside the tab (active and not active).
The menu with the various functions (changing case, clipboard functions, loading and saving files etc) is too small. I cannot work in it on my screen.
I still don't know how to close your plugin.
In explorer pluging there is a "v" sign in the plugin menu.
Clicking again the plugin is disabled.
Why don't you do the same with the simple script plugin?
As always, thanks for this great plugin!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep. I'm still working on these. One of the next things I'm planning to do is add an icon, which should fix most of the tab issues. I might shorten "Simple Script" to just "Script" or possibly "SScript" on the tab.
>The menu with the various functions (changing case, clipboard functions, loading and saving files etc) is too small.
Do you mean the font size, or the window? There's not much I can do about the font size; it's already tight for space, and expanding it may do more harm than good. If you're concerned about the window, I can add a splitter that will allow you to make it bigger.
>I still don't know how to close your plugin.
Click the "X" in the upper right if it's the only one docked, or middle-click the Simple Script tab if there are others docked.
>In explorer pluging there is a "v" sign in the plugin menu.
It's a good idea, and maybe I'll add it eventually. The only problem is I don't know how to capture events from Notepad++, such as the event that fires when the window is closed from another method, which I would need in order to update the check mark on the menu.
I'm planning to fix all of these. I just haven't had time to work on Simple Script lately. Version 1.13 was mainly to address the docking issues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I dont know how your form worked, but looking at the results of the close button I guess the window did close but the pane was left open, leaving a grey area. To show your dialog again call
I work with c++ so it goes probably a bit different. I find it most convienient to create a non visible window (in win32 its CreateWindow with the visible flag not set) and then register it, and letting notepad++ do all the other work (in fact, as soon as notepad calls for the dialog to show, it gets created first if it doesnt exist, then it explicitly calls the show function).
If you ever going to make a toolbar icon or support checking the menu item, use
SendMessage(nppData._nppHandle,NPPM_SETMENUITEMCHECK,(WPARAM)funcItem[0]._cmdID,(LPARAM)FALSE);
(again c++, the import thing to keep in mind is the index of the array with funcItems, currently with your plugin its 0).
Currently I think a close button is convienient if the menu function isnt a toggle, but if you were to make it a toggle option and/or add a toolbar icon, I think it isnt that badle needed. Thats how most of the dockable plugins work atm I think (though obviously that does not have to mean its a standard ;])
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'll have to look into this. I was considering making the menu function a toggle, but it runs into the same problems as a close button: How to write a function to close it.
I'll experiment a little with the SendMessage calls you mentioned above. I'm familiar enough with the Delphi versions of the functions that I think I can translate them easily enough.
Thanks.
fidvo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Okay, I think I've got everything fixed now. I removed the "Close" button, which was causing problems. Now you need to close it with the "x" button (or middle-click on the Simple Script tab if it's docked with other plugins).
If there are still unresolved issues with the docking, post them here.
Note: The SimpleScript.ini file must now be in the plugins\Config folder. If you just have it in the plugins folder, you'll need to move it.
Again, thanks to Zobo for fixing the docking problems.
Still same troubles as in 1.12 and 1.11
There are problems in the plugin tabs:
- the name of the plugin is not readable on the tab. what I can read is "imple Script"
- if the simple script tab is not active, the simple script tab is empty, no icon
- the simple script tab is taking almost the whole width of the plugin tab bar.
why don't you put only an "S" inside the tab (active and not active).
The menu with the various functions (changing case, clipboard functions, loading and saving files etc) is too small. I cannot work in it on my screen.
I still don't know how to close your plugin.
In explorer pluging there is a "v" sign in the plugin menu.
Clicking again the plugin is disabled.
Why don't you do the same with the simple script plugin?
As always, thanks for this great plugin!
>There are problems in the plugin tabs
Yep. I'm still working on these. One of the next things I'm planning to do is add an icon, which should fix most of the tab issues. I might shorten "Simple Script" to just "Script" or possibly "SScript" on the tab.
>The menu with the various functions (changing case, clipboard functions, loading and saving files etc) is too small.
Do you mean the font size, or the window? There's not much I can do about the font size; it's already tight for space, and expanding it may do more harm than good. If you're concerned about the window, I can add a splitter that will allow you to make it bigger.
>I still don't know how to close your plugin.
Click the "X" in the upper right if it's the only one docked, or middle-click the Simple Script tab if there are others docked.
>In explorer pluging there is a "v" sign in the plugin menu.
It's a good idea, and maybe I'll add it eventually. The only problem is I don't know how to capture events from Notepad++, such as the event that fires when the window is closed from another method, which I would need in order to update the check mark on the menu.
I'm planning to fix all of these. I just haven't had time to work on Simple Script lately. Version 1.13 was mainly to address the docking issues.
As for the closing, you have to explicitly call
SendMessage(nppData._nppHandle,NPPM_DMMHIDE,0,(LPARAM)HANDLE_OF_YOUR_FORM);
I dont know how your form worked, but looking at the results of the close button I guess the window did close but the pane was left open, leaving a grey area. To show your dialog again call
SendMessage(nppData._nppHandle,NPPM_DMMSHOW,0,(LPARAM)HANDLE_OF_YOUR_FORM);
I work with c++ so it goes probably a bit different. I find it most convienient to create a non visible window (in win32 its CreateWindow with the visible flag not set) and then register it, and letting notepad++ do all the other work (in fact, as soon as notepad calls for the dialog to show, it gets created first if it doesnt exist, then it explicitly calls the show function).
If you ever going to make a toolbar icon or support checking the menu item, use
SendMessage(nppData._nppHandle,NPPM_SETMENUITEMCHECK,(WPARAM)funcItem[0]._cmdID,(LPARAM)FALSE);
(again c++, the import thing to keep in mind is the index of the array with funcItems, currently with your plugin its 0).
Currently I think a close button is convienient if the menu function isnt a toggle, but if you were to make it a toggle option and/or add a toolbar icon, I think it isnt that badle needed. Thats how most of the dockable plugins work atm I think (though obviously that does not have to mean its a standard ;])
Thanks.
I'll have to look into this. I was considering making the menu function a toggle, but it runs into the same problems as a close button: How to write a function to close it.
I'll experiment a little with the SendMessage calls you mentioned above. I'm familiar enough with the Delphi versions of the functions that I think I can translate them easily enough.
Thanks.
fidvo
Fidvo.
Check the TNppDockingForm class. This should already be implemented (Show and Hide). I guess just the override is messed up.
-Zobo