[Bloodlvst]

As some of you know, I'm working on a client settings menu, and I feel like I'm almost ready to start testing the code. However just a question:

For a type of menu like this would you recommend using a menu or a panel? And if it's a panel, is it possible to paginate a panel as well or only a menu? Thanks!

[KMFrog]

I thought menus were panels >_>

[Bloodlvst]

Yes and no. Apparently there's differences according to the Menu API documentation.

[KMFrog]

the only difference is the menu API is higher level..
it gives you stuff like auto-pagination... etc... but the menu API uses the panel API to do its work.

you can still use the panel API direct to create your own menus with, say, custom text at the top of the menu or in the body.. which you cannot do with the menu API

[TFN|Nick]

I don't think it'll matter much to the average gamer unless they can't find what they want... maybe take a page out of the sm_admin menu and create as a top menu as opposed to normal menu.

That way developers can hook onto it... say someone wants deathbeam on the menu; the plugin developer can just use the same method and intergrate the plugin in. Easier for everyone i'd think??

[BAILOPAN]

There is an open feature request for this in SourceMod; I think it's planned for 1.1.

[Bloodlvst]

Yeah I was just curious into what way is better.

This is just something I want to do to fill the gap and allow servers to have one menu (like Mani did) for settings, instead of 5 different public commands. But Nick, thanks for the input, I'll look into trying to make it work that way.

[BAILOPAN]

If your menu will have pagination you should always use menus. Panels are only intended for arbitrary drawing (for example, displaying statistics or information that doesn't need feedback). Menus are guaranteed to give clients a consistent and uniform design.