hyyly / csexwb2

Automatically exported from code.google.com/p/csexwb2
0 stars 0 forks source link

history entry problem #37

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Add a csExWB control, a button which makes it navigate to
"http://www.google.com/" and another button that calls it's GoBack() method.
2. Press the first button, and wait until the page loads (~500ms), then
enter anything in the search box and press enter or the Search button.
3. Press the second button to go back one page.

What is the expected output? What do you see instead?
The control does nothing. It should go back to the initial page.

What are the OS and IE versions?
Windows XP Pro. IE7.

What version of the product are you using?
17 Mar 2008 - Version (2.0.0.1)

Please provide any additional information below.
Further tests like searching twice within the page shows that the GoBack()
method works only until the first history entry. It seems the internal
m_TravelLogStg variable is to blame as it doesn't contain the first element
at all.

Original issue reported on code.google.com by manixr...@gmail.com on 29 Apr 2008 at 5:41

GoogleCodeExporter commented 9 years ago
I've stumbled across this while trying to find a way to get the Back and Forward
history to display in a drop-down combo box, like in Firefox. There seems to be 
no
such method implemented, as the GetTraveLogEntries() method returns all the 
entries
(except the first, as stated in the above bug).

I solved this by simply making the TLMENUF a parameter of the function, so 
calling
GetTraveLogEntries(TLMENUF.TLEF_RELATIVE_BACK) gets me what I need to display 
the
back history (again, without the first entry).

It would be of great assistance if you could implement a simple enum instead of 
the
ugly TLMENUF enum, and have that as a parameter for the method.

Thanks for this excellent control!

Original comment by manixr...@gmail.com on 29 Apr 2008 at 5:55

GoogleCodeExporter commented 9 years ago
Seems like it was cause by my code making it, once created, run it's 
NavToBlank()
method. Without it it seems to work fine. But with it it seems to create 
problems for
it's history, so it's still a bug, but it happens when you call NavToBlank() 
first on it.

Also, when would the best event be for updating the back and forward list?

Original comment by manixr...@gmail.com on 29 Apr 2008 at 7:16

GoogleCodeExporter commented 9 years ago
Thank you for reporting this bug. I have posted a temporary solution which will 
be 
part of the next release.

http://groups.google.com/group/csexwb/t/1b8a31a5dec1cf6

Regards,

MH

Original comment by mehr...@gmail.com on 2 May 2008 at 10:46