On Saturday 29 November 2014, Kai Uwe Broulik wrote:
I migrated the essential parts of PageStack to StackView but now System
Tray is completely broken. Switching to different applets leaves the old
ones there.
According to documentation By default […] StackView will destroy items
pushed
I migrated the essential parts of PageStack to StackView but now System Tray
is completely broken. Switching to different applets leaves the old ones
there.
According to documentation By default […] StackView will destroy items pushed
as components or URLs. Items not destroyed will be re
Qt takes one JS Object and I think we cannot overload them (ie. have a method
foo(bar, baz) call a foo(bla) instead.
API differences (PageStack → StackView)
depth → depth (identical)
currentPage → currentItem (could be alias'd)
toolBar → for some magic toolbar thing, allegedly used in the widget
with JavaScript functions taking a couple of parameters
whereas Qt takes one JS Object and I think we cannot overload them (ie.
have a method foo(bar, baz) call a foo(bla) instead.
API differences (PageStack → StackView)
depth → depth (identical)
currentPage → currentItem (could be alias'd)
toolBar
On Monday 24 November 2014, Marco Martin wrote:
push(page, properties, immediate) → push(item) as a shortcut, or
push({item: someItem, immediate: true, properties: {foo: bar, baz:
bla} }) which cannot be (easily, if at all?) overloaded to provide
legacy support
Uuh, from where the
Am Montag, 24. November 2014, 20:47:26 schrieb Marco Martin:
pageStack.push(someItem, {fgcolor: red, bgcolor: blue}, true) would just
wrap internally
stackView.push({item: someItem, immediate: true, properties: {fgcolor:
red, bgcolor: blue}})
So it seems when I define a
function push(item,
