Source code |
|
1 2 3 4 5 6 7 8 9 |
QPtrStack<KURL>* MyDirOperator::backURLs() const { return backStack; } QPtrStack<KURL>* MyDirOperator::forwardURLs() const { return forwardStack; } |
Source code |
|
1 2 3 4 5 6 7 8 9 10 11 12 |
void KDirOperator::back() { if ( backStack.isEmpty() ) return; forwardStack.push( new KURL(currUrl) ); KURL *s = backStack.pop(); setURL(*s, false); delete s; } |
Quoted
Originally posted by anda_skoa
Hmm, if you can get the URL of the current active operator you could use setURL.
This post has been edited 3 times, last edit by "Krasu" (Jun 3rd 2005, 1:40pm)
Source code |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
void KDirOp::slotFinishedLoading() { const QObject* dirop = QObject::sender(); if (dirop == dirop1) { dirop2->setURL(dirop1->url(), true); } else if (dirop == dirop2) { dirop1->setURL(dirop2->url(), true); } } |
Quoted
Originally posted by Krasu
Right. You synchronized history with some hacks. This code is not looking good
Quoted
Imagine, that I've gone to directory that contains ~5000 files, and all my diroperators start to load it ...
Quoted
As I already said, history stacks must be protected!
Forum Software: Burning Board®, developed by WoltLab® GmbH
Linux Computer - Linux Forum -
Linux Computer und Notebooks - Lastminute - Wasserbetten & Whirlpools