let's say I have this in my dialog:



Is it possible to hide tab 3 only?
I tried and the answer is no, all tabs will be hidden.

so I suggest that I could hide one tab

Yes I'd like to see this, when using the hide switch I think it should set the focus on just one tab ID, each tab has it's own ID so should be able to hide... (as you have 3 ID's in your code above)

If it can be implemented I'd like to see it, if it can be coded somehow I'd like to see that too..

Nice suggestion!

-Andy

Just curious why would you want to hide a tab? I do not see a real purpose in that.

Maybe you only want the tab to show up when specific conditions are met. For example, let's say I have an "away system" tab in a dialog, maybe I'll only want that to show up when I actually have an away system script loaded.

I do like this idea. The one thing I see as an issue with it is probably the reason it isn't a feature...

When tabs are created, they are set in a specific place:

_________________________
| TAB1 | TAB2 | TAB3 | TAB4 |

Ok, so if you hide Tab 3, should it look like this?

________________________
| TAB1 | TAB2 | ___ | TAB4 |

Or this?

___________________
| TAB1 | TAB2 | TAB4 |


The second example would make more sense, but that would require re-arranging how things are displayed rather than just hiding it. If you hide something else, nothing else has to move around.

I still say it's a good idea. Just thought I'd point out what is probably an issue with it.

Although I'm positive it's suggested before, I'll add it here too since it's a tab thing... I think it would also be nice to have nested Tabs.

__________________
| TAB1 | TAB2 | TAB4 |

thats how it looks in any other language that can hide tabs

i think its a good idea and can be very useful

...even though there are many things about dialogs that can be useful and should be added, so im not surprised.

The main problem with tabs in mIRC is that they aren't "real" tabs. For 16 bit compliance (which isn't needed anymore), mIRC has been owner-drawing all of it's dialog controls (and that approach is probably keeping them from inserting new ones).

Tabs are simply a static control which draws the "tabs" on it's client part. In theory it could be possible to hide one of them, but I really think that dialogs (especially controls) need an overhaul to be back to Win32 API behavior and support more of the common controls.

But now I'm dreaming and that's why I'm in the process of creating a DLL that will add more of those (like MDX, but different approach with more possibilities).

Yes, it would be helpful to have all 16bit stuff replaced with 32bit stuff.

Btw, send your DLL my way when you complete it.