| Q: |
Can the different GroupHeader's have
different borders |
| A: |
Yes, the borders of different
GroupHeaders's can be different with respect to width, style
and color. |
| Q: |
Can different Group's slide with
different speed |
| A: |
No. |
| Q: |
Can I have multiple SlidingMenues at the
same page |
| A: |
Yes. |
| Q: |
Can I nest SlidingMenues |
| A: |
Yes, in any manner and depth you would
like |
| Q: |
How do I set a specific Group to open
then the page is loaded first time |
| A: |
Set the GroupHeaderStyle.OpenGroupAtStartup
attribute to true for the Group you want to open. |
| Q: |
How do I secure that a specific Group
allways open automatically also after a PostBack |
| A: |
Set the SlidingMenuStyle.RememberOpenGroup
attribute to false and the GroupHeaderStyle.OpenThisGroupAtStartup
attribute to true for the specific Group you want to open each
time the page load. |
| Q: |
How do I secure that the currently open
Group opens again after a PostBack |
| A: |
Set the SlidingMenuStyle.RememberOpenGroup
attribute to true (default). |
| Q: |
Can I have ASP.Net Server Controls inside
both GroupHeader's and GroupCanvas'es |
| A: |
Yes, however then nesting Server Controls
you will sometimes have to declare types and hooking up
events, that the VS.NET IDE will otherwise write for you. This
has nothing to do with the SlidingMenu and applies equally
well for say nested DataGrid's. |
| Q: |
Can I have both databound Group's and
manually added Group's within the same
SlidingMenu |
| A: |
Yes. You can have 1 DataBound tag (that
is: you can have one DataSource) and multiple AddManualGroup
tags before and after the DataBound tag. |
| Q: |
If I specify default properties in
top-level <GroupHeaderStyle ...> and
<GroupCanvasStyle ...> tags, will these default
properties also apply for databound Group's |
| A: |
Yes. |
| Q: |
How do I specify a say green canvas
background for a specific mannually added Group |
| A: |
You will need to add a
<GroupCanvasStyle BackgroundColor="green" /> tag beneath
the <AddManualGroup> where you want the canvas to have a
green background. |
| Q: |
How do I specify a say green canvas
background for a specific databound Group |
| A: |
This must be done in the GroupDataBound
eventhandler. First test for the specific Group you want to
style different from your default styles and then set the
BackgroundColor property of the GroupCanvas.GroupCanvasStyle
object.
| protected void
slidingmenu1_GroupDataBound(object sender,
Webmodelling.Controls.Menues.SlidingMenuGroupEventArgs e){ |
| ... |
| if
([condition to test you have your specific
group]){ |
| e.GroupCanvas.GroupCanvasStyle.BackgroundColor
= "green"; |
| } |
| ... |
| } | |
| Q: |
How do I reference ASP.Net Server
Controls within manually added
Group's |
| A: |
The technic is no different as for
referencing nestet not databound ASP.Net Server Controls. If
you want to set in say a DataGrid in the GroupCanvas, just
nest it in the <GroupCanvas> tag, declare it in the
code-behind file and hook up the necessary
events. |
| Q: |
How do I reference ASP.Net Server
Controls within databound
Group's |
| A: |
The technic is the same as for
referencing ASP.Net Server Controls within databound items of
other ASP.Net Server Controls. Lets say you have an ASP.Net
Label within the databound headers called lblHeader, then
inside the GroupDatabound eventhandler, you can get the
lblHeader Label for each Group by writing
| protected void
slidingmenu1_GroupDataBound(object sender,
Webmodelling.Controls.Menues.SlidingMenuGroupEventArgs
e){ |
| ... |
| Label
lblHeader =
(Label)e.GroupHeader.FindControl("lblHeader"); |
| ... |
| } | |
| Q: |
Why can't I set the width of the
GroupHeader in the <GroupHeaderStyle ...>
tag |
| A: |
Because the width of the GroupHeader
(GroupHeader content area) is a calculated value equal to
SlidingMenuStyle.Width -
SlidingMenuStyle.BorderWidth -
GroupHeaderStyle.BorderWidth. |
| Q: |
Why do I need to drag the SlidingMenu in
from the ToolBox, why can't I just write the xml-tag in the
html-view |
| A: |
You don't need to, but it is a very good
idea to drag especially the first SlidingMenu from the
ToolBox, because first time you drag the SlidingMenu from the
ToolBox to the Designer (design-view) of a Web Form page, the
following will happen automatically
| 1. |
The Webmodelling.SlidingMenu.dll will be copied to your
web project bin folder and added to your web project reference list - if not
already there. |
| 2. |
a @Register directive will be
written at the top of your Web Form page - if not already there.
<%@ Register TagPrefix="wm"
Namespace="Webmodelling.Controls.Menues"
Assembly="Webmodelling.SlidingMenu"
%> |
| 3. |
Namespace enabling IntelliSense XSD background for
SlidingMenu will be written to the BODY tag of your Web Form page - if not
already there.
<body xmlns:wm="http://www.menulab.com/schemas/SlidingMenu-v-1-1-IntelliSense"
...> |
| 4. |
the SlidingMenu will be
instantiated in the code-behind file of your Web Form
page
protected
Webmodelling.Controls.Menues.SlidingMenu
slidingmenu1; |
| 5. |
an xml-tag will be inserted at your
Web Form page (html-view)
<wm:SlidingMenu id="slidingmenu1" runat="server" style="[some
style]"></wm:SlidingMenu> |
However if you are comfortable with these
operations, there is no reason you should not write the code
yourself and anyway the second SlidingMenu (in the same Web
Form page) will be easy to add manually in html-view.
|
| Q: |
Why for some topics in Dynamic Help will
the topic disappear from the Menulab linkgroup if I place the
cursor of the corresponding xml tag in xml
markup. |
| A: |
If you place your cursor on eg. a
GroupHeaderStyle tag, the GroupHeaderStyle help topic will
disappear from the Menulab linkgroup, but it will appear on
the top in the Help linkgroup. This has to do with 2 causes,
first the Dynamic Help xml parser do not support the same link
in 2 different linkgroups, second to ensure that the element
definitions of the SlidingMenu is readily available in the
Dynamic Help default linkgroup - Help - if you choose to
either remove the Menulab linkgroup or just collaps the
Menulab linkgroup. You can remove the Menulab linkgroup by
unmarking it in "Tools | Options | Environment | Dynamic Help
| Categories" (be aware that the Menulab linkgroup will
support also future Server Controls from Menulab and that not
all the links of the Menulab linkgroup will be available in
the default Help linkgroup).
|
| Q: |
Why is there a <wm ...> tag in my
UserControl (ascx) files. |
| A: |
This happens then you drag a SlidingMenu
onto a UserControl. It was the best way I could find to enable
IntelliSense background on UserControls. There are to my
knowledge only 2 alternatives, either write IntelliSense
background support directly into VS.NET IDE own IntelliSense
XSD, which is bad for 2 reasons (fifling with things not to be
fifled with and if you upgrade your VS, you will loose
SlidingMenu IntelliSense) and to put the namespace declaration
inside an ordinary html tag, which I did not want because I
don't want to put html tags in your code as also in fact it
would not be possible to do without making your html not
wellformed in an xml context unless I put some severe
restrictions upon you. All in all I find the <wm> tag
the best solution.
|
| Q: |
Is it possible to have ALL GroupHeaders
in the bottom. |
| A: |
No, at least the first GroupHeader (index
= 0) will ALWAYS render at the top and cannot move. In more
advanced scenaries it is possible to set the Height of one,
more or all GroupHeaders to zero (remember to set the border
to zero too) and make your own list of keys to substitute the
GroupHeaders - in that case you MUST use the wm_3_SMPlay
function, see the Tips
& Tricks - Open Groups from JavaScript for a code
example or the Client
API Documentation - Predefined Functionality for the
theory.
|