Hi
I'm manually filling a webExplorerBar, and it draws perfectly, the user can remove some items on the explorer bar by pressing a button, when this happens i want to redraw the ExplorerBar to show the new items but i got the Groups been duplicated and the new duplacated group show no visual style
I call this code the first time the ExplorerBar is shown and also when i need to refresh it.
webOpciones.Groups.Clear()
For Each drGrupo As DataRow In OpcionesUsuario.dtGrupos.Rows
oGrupo = New ExplorerBarGroup(drGrupo("GroupName"), drGrupo("id_Group")) webOpciones.Groups.Add(oGrupo)
For Each drOpcion As DataRowView In dvOpciones New ExplorerBarItem(drOpcion("Name"), "", drOpcion("URL"), drOpcion("Image"))
lOpcion = lOpcion.DataItem = drOpcion
oGrupo.Items.Add(lOpcion) NextNext
Regards.
Hi,
this was fixed with bug 60713. You can contact developer support to get more information when it will be released.
Thanks,
Lubomir
I am also see errant behaviour when trying to reload items in a group with a very simple routine that clears the existing items and then adds the new items:
'Load list of records into explorer bar Private Sub LoadExplorer() With WebExplorerBar1 With .Groups(0) .Items.Clear() For i As Integer = 0 To 10 .Items.Add(i.ToString, i.ToString, "", "") Next End With End With End Sub
Hello Daniel,
I have created a support ticket on your behalf in order to investigate your issue further. The case number is CAS-55984-BKZDYR.
Please could you attach your sample to the support ticket.
Thanks
jaddington said: Lubomir, We are trying to do this scenario on purpose. We are using the ExplorerBar as a set of grouped filters. When we 'apply' a filter we want to completely rebuild the explorerbar to reflect the new set of available options. Groups.Clear doesn't clear what sounds like is the data in the ViewState. I'm assumming I could do something so that the Explorerbar doesn't use ViewState but then I would have to build it on every postback. That isn't terrible except the logic to generate the data for the toolbar could take a while. I suppose we could cache the data between 'DoFilterAction' clicks but that just adds more compexitity. Any advice? I would think that Clearing the groups should be smart enough to push the right data back to the client side and fix the issue. thanks jack
Lubomir,
We are trying to do this scenario on purpose. We are using the ExplorerBar as a set of grouped filters. When we 'apply' a filter we want to completely rebuild the explorerbar to reflect the new set of available options.
Groups.Clear doesn't clear what sounds like is the data in the ViewState.
I'm assumming I could do something so that the Explorerbar doesn't use ViewState but then I would have to build it on every postback. That isn't terrible except the logic to generate the data for the toolbar could take a while. I suppose we could cache the data between 'DoFilterAction' clicks but that just adds more compexitity.
Any advice? I would think that Clearing the groups should be smart enough to push the right data back to the client side and fix the issue.
thanks
jack
Further to this we tried disabling the ViewState for the control but then the itemClicked event didn't fire on the server. This killed that plan. What we are seeing is that on the first post back we clear and add and then on the client we end up with the original groups (formatted and styled) then a new set of groups not formatted or styled.
If we loop again via ItemClicked then we get a formatted set of groups for the first 2 iterations and our 3rd iteration is not formatted.
So we are stuck if we want to stay with the WebExplorerBar. The logic works with a tree view but it isn't nearly as nice as we have the matching Explorerbar without the need to refresh on another page so it will look silly to have it different.! We are using version 10.2.20102.2101
Please advise! Does 10.3 fix or modify this scenario?