Re: [SailfishDevel] Dialog/ListView/Menu/Search

2020-01-04 Thread Slava Monich

How about this?

Dialog {
SilicaListView {
anchors.fill: parent
PullDownMenu { /* MenuItems */ }
header: Column {
width: parent.width
DialogHeader {
title: "Title"
}
SearchField {
width: parent.width
}
}
}
}


I must be possible to do, but maybe my head is just wired wrong - well, I do
have that one paper already, so... :D

How to have a SilicaListView with a SearchField inside a Dialog with a
DialogHeader and a menu, where the SearchField is below the DialogHeader,
the list starts below both?

Every even semi-logical way to do this ends up, for me at least, with an
unholy mess.

What for me would seem logical is be a variation of:

Dialog {
 SilicaListView {
 PullDownMenu { /* MenuItems */ }
 header: DialogHeader {
 id: dialogHeader
 }
 SearchField {
 parent: dialogHeader.extraContent
 }
 }
}

or:

Dialog {
 SilicaListView {
 PullDownMenu { /* MenuItems */ }
 header: Column {
  DialogHeader {}
  SearchField {}
 }
 }
}

Neither works, but as coderus wrote to me in a PR 4-5 years ago, I do weird
stuff ;)

I could write all the variations I've tried, but that would just be a parade
of more weird stuff with variations over missing or misplaced header, menu,
search field or list.


___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Dialog/ListView/Menu/Search

2020-01-04 Thread Thomas Tanghus
On Saturday, 4 January 2020 16.10 Thomas Tanghus wrote:
> Yes. Annoyingly DialogHeader.extraContent doesn't work like e.g.
> ListView.header/footer, so the above was how I tried.

Forgot to write that it resulted in the search field being *inside* the 
header, which is somewhat logical, but not what I was aiming for.

-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?


signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Dialog/ListView/Menu/Search

2020-01-04 Thread Thomas Tanghus
On Saturday, 4 January 2020 16.04 Michael Fuchs wrote:
> did you try extraContent?
 
> > Dialog {
> > SilicaListView {
> > PullDownMenu { /* MenuItems */ }
> > header: DialogHeader {
> > id: dialogHeader
> > }
> > SearchField {
> > parent: dialogHeader.extraContent
> > }
> > }
> > 

Yes. Annoyingly DialogHeader.extraContent doesn't work like e.g. 
ListView.header/footer, so the above was how I tried.

-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?


signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Dialog/ListView/Menu/Search

2020-01-04 Thread Michael Fuchs
Hi,

did you try extraContent?

https://sailfishos.org/develop/docs/silica/qml-sailfishsilica-sailfish-silica-dialogheader.html/#extraContent-prop

lG, Michael.

On Samstag, 4. Jänner 2020 16:00:29 CET Thomas Tanghus wrote:
> I must be possible to do, but maybe my head is just wired wrong - well, I do
> have that one paper already, so... :D
> 
> How to have a SilicaListView with a SearchField inside a Dialog with a
> DialogHeader and a menu, where the SearchField is below the DialogHeader,
> the list starts below both?
> 
> Every even semi-logical way to do this ends up, for me at least, with an
> unholy mess.
> 
> What for me would seem logical is be a variation of:
> 
> Dialog {
> SilicaListView {
> PullDownMenu { /* MenuItems */ }
> header: DialogHeader {
> id: dialogHeader
> }
> SearchField {
> parent: dialogHeader.extraContent
> }
> }
> }
> 
> or:
> 
> Dialog {
> SilicaListView {
> PullDownMenu { /* MenuItems */ }
> header: Column {
>  DialogHeader {}
>  SearchField {}
> }
> }
> }
> 
> Neither works, but as coderus wrote to me in a PR 4-5 years ago, I do weird
> stuff ;)
> 
> I could write all the variations I've tried, but that would just be a parade
> of more weird stuff with variations over missing or misplaced header, menu,
> search field or list.



___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Dialog/ListView/Menu/Search

2020-01-04 Thread Thomas Tanghus
I must be possible to do, but maybe my head is just wired wrong - well, I do 
have that one paper already, so... :D

How to have a SilicaListView with a SearchField inside a Dialog with a 
DialogHeader and a menu, where the SearchField is below the DialogHeader, 
the list starts below both?

Every even semi-logical way to do this ends up, for me at least, with an 
unholy mess.

What for me would seem logical is be a variation of:

Dialog {
SilicaListView {
PullDownMenu { /* MenuItems */ }
header: DialogHeader {
id: dialogHeader
}
SearchField {
parent: dialogHeader.extraContent
}
}
}

or:

Dialog {
SilicaListView {
PullDownMenu { /* MenuItems */ }
header: Column {
 DialogHeader {}
 SearchField {}
}
}
}

Neither works, but as coderus wrote to me in a PR 4-5 years ago, I do weird 
stuff ;)

I could write all the variations I've tried, but that would just be a parade 
of more weird stuff with variations over missing or misplaced header, menu, 
search field or list.

-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?


signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org