[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    khtml/historyprovider question
From:       Bart Symons <bart.symons () skynet ! be>
Date:       2001-11-01 12:38:10
[Download RAW message or body]


I implemented a small application that uses both the KHTMLPart and 
HistoryProvider classes.

The structure is as follows:
() means "contains"
-> means "instantiates"

mywidget(KHTMLPart+HistoryProvider) -> KDialogBase(mywidget(KHTMLPart + 
HistoryProvider).

The reason why a separate modeless dialog box is used is simple: when a 
hyperlink contains the "_blank" parameter than it is expected to start show 
the URL in a new window.

Everything works fine except the URL history (used for the "prev" and "next" 
buttons like in Konqueror). Although I create a second instance of the widget 
that itself contains new instances of KHTMLPart and HistoryProvider, the 
history if the pop-up window doesn't work but instead gets absorbed in the 
history of the main browser window.

So, how is one supposed to use HistoryProvider? Do all KHTMLPart within an 
application share the same HistoryProvider? How can I prevent this? I want 
each browser window to have its own history.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]