| Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 3 | |
Hi! I'm very happy with the fact that Qt now works on Windows Mobile platform, making it (Qt) even better than it was. :) However, I have some suggestions: 1) all top-level widgets/windows should be maximized by default -- currently Qt windows tend to be larger than the screen of the device; 2) add small (2-4 px) border inside top-level widgets -- it should look better, IMHO; 3) there should be some way to react on Input Panel state change (on/off) and re-arrange widgets accordingly -- if there're some editable widgets at the bottom of the window, user won't be able to see what [s]he is entering. What do you think about these? P.S.: If anyone wants, I've made a WM5 .cab package (should work with WM6, but I don't have accessible WM6 system around). -- [ signature omitted ]
Hi, thank you for your feedback. The Windows CE team is always glad about feedback, bug reports and suggestions. There is also a mailing list dedicated to the preview if Qt for Windows CE that is still in use: qtce-preview-feedback@xxxxxxxxxxxxx <mailto:qtce-preview-feedback@xxxxxxxxxxxxx> 1) We do maximize top-level widgets that are expanding or have a child widget that is expanding or that have a sizeHint() of at least 40% of the vertical screen size. (You can check autoMaximizeThreshold in the documentation). We do not maximize the widget if the minimumSizeHint is bigger than the screen size, because then the layout breaks. We do think about adding scrollbars automatically in some future release. There some top-level widgets like message boxes or progress dialogs that should not be maximized by default. This is the reason why we implemented this heuristic. 2) Sounds like a valid suggestion. I will check this and compare it to native applications. It could look bad though, if the top-level widget has a scrollbar. 3) We have the sipdialog example which shows how to react to the sip. We do nothing by default, because we cannot properly decide the reaction for all cases. In many cases no reaction is fine because the textfield is still above the sip. To much magic here (Like a check if the sip overlaps the focus-widget), might confuse developers a lot. But I am open for further suggestions. Best Regards, Thomas Hartmann -------- Original Message -------- Subject: [Fwd: Qt/Windows Mobile Suggestions] Date: Thu, 15 May 2008 11:31:27 +0200 From: Kai Koehne <kai.koehne@xxxxxxxxxxxxx> To: Thomas Hartmann <thartman@xxxxxxxxxxxxx> -------- Original Message -------- Subject: Qt/Windows Mobile Suggestions Date: Thu, 15 May 2008 13:10:24 +0400 From: Constantin Makshin <dinosaur-rus@xxxxxxxxxxxxxxxxxxxxx> Organisation: Dinosaur Software To: Qt-interest <qt-interest@xxxxxxxxxxxxx> Hi! I'm very happy with the fact that Qt now works on Windows Mobile platform, making it (Qt) even better than it was. :) However, I have some suggestions: 1) all top-level widgets/windows should be maximized by default -- currently Qt windows tend to be larger than the screen of the device; 2) add small (2-4 px) border inside top-level widgets -- it should look better, IMHO; 3) there should be some way to react on Input Panel state change (on/off) and re-arrange widgets accordingly -- if there're some editable widgets at the bottom of the window, user won't be able to see what [s]he is entering. What do you think about these? P.S.: If anyone wants, I've made a WM5 .cab package (should work with WM6, but I don't have accessible WM6 system around). -- [ signature omitted ]
1) that can be hard to implement, but may be maximize all top-level widgets (except ones like message boxes, of course) that won't get broken? 3) may be add a signal which is emitted when SIP state changes and a slot that'll automatically re-arrange child widgets? Or window flag that'll tell that this widget shouldn't be overlaped by SIP. Then developers could just add one line where they want automatic handling of input panel states. BTW, are QtHelp, QtWebKit and QtXmlPatterns modules not available in Windows CE version of Qt or there was something wrong during my compilation? On Thu, 15 May 2008 13:55:32 +0400, Thomas Hartmann <Thomas.Hartmann@xxxxxxxxxxxxx> wrote: > Hi, > > thank you for your feedback. The Windows CE team is always glad about > feedback, bug reports and suggestions. There is also a mailing list > dedicated to the preview if Qt for Windows CE that is still in use: > qtce-preview-feedback@xxxxxxxxxxxxx > <mailto:qtce-preview-feedback@xxxxxxxxxxxxx> > > 1) > We do maximize top-level widgets that are expanding or have a child > widget that is expanding or that have a sizeHint() of at least 40% of > the vertical screen size. (You can check autoMaximizeThreshold in the > documentation). We do not maximize the widget if the minimumSizeHint is > bigger than the screen size, because then the layout breaks. We do think > about adding scrollbars automatically in some future release. > There some top-level widgets like message boxes or progress dialogs that > should not be maximized by default. This is the reason why we > implemented this heuristic. > 2) > Sounds like a valid suggestion. I will check this and compare it to > native applications. It could look bad though, if the top-level widget > has a scrollbar. > 3) > We have the sipdialog example which shows how to react to the sip. We do > nothing by default, because we cannot properly decide the reaction for > all cases. In many cases no reaction is fine because the textfield is > still above the sip. To much magic here (Like a check if the sip > overlaps the focus-widget), might confuse developers a lot. But I am > open for further suggestions. > > Best Regards, > Thomas Hartmann > > -------- Original Message -------- > Subject: [Fwd: Qt/Windows Mobile Suggestions] > Date: Thu, 15 May 2008 11:31:27 +0200 > From: Kai Koehne <kai.koehne@xxxxxxxxxxxxx> > To: Thomas Hartmann <thartman@xxxxxxxxxxxxx> > > -------- Original Message -------- > Subject: Qt/Windows Mobile Suggestions > Date: Thu, 15 May 2008 13:10:24 +0400 > From: Constantin Makshin <dinosaur-rus@xxxxxxxxxxxxxxxxxxxxx> > Organisation: Dinosaur Software > To: Qt-interest <qt-interest@xxxxxxxxxxxxx> > > Hi! > > I'm very happy with the fact that Qt now works on Windows Mobile > platform, making it (Qt) even better than it was. :) > > However, I have some suggestions: > 1) all top-level widgets/windows should be maximized by default -- > currently Qt windows tend to be larger than the screen of the device; > 2) add small (2-4 px) border inside top-level widgets -- it should look > better, IMHO; > 3) there should be some way to react on Input Panel state change > (on/off) and re-arrange widgets accordingly -- if there're some > editable widgets at the bottom of the window, user won't be able to see > what [s]he is entering. > > What do you think about these? > > P.S.: If anyone wants, I've made a WM5 .cab package (should work with > WM6, but I don't have accessible WM6 system around). -- [ signature omitted ]
On Thursday 15 May 2008 12:34:40 Constantin Makshin wrote: > BTW, are QtHelp, QtWebKit and QtXmlPatterns modules not available in > Windows CE version of Qt or there was something wrong during my > compilation? No, that's the correct behaviour. Qt for Windows CE 4.4 has the Qt 4.3 feature set, plus whatever we had the time to implement. It'll reach feature parity with the rest of Qt probably in the next release. -- [ signature omitted ]
Attachment:
signature.asc
Description: This is a digitally signed message part.
Hi Constantin, > 1) that can be hard to implement, but may be maximize all top-level > widgets (except ones like message boxes, of course) that won't get broken? That automaximizing Thomas wrote about is already implemented. Please have a look at http://doc.trolltech.com/4.4/qapplication.html#autoMaximizeThreshold-prop > 3) may be add a signal which is emitted when SIP state changes and a > slot that'll automatically re-arrange child widgets? Or window flag > that'll tell that this widget shouldn't be overlaped by SIP. Then > developers could just add one line where they want automatic handling of > input panel states. These are quite good ideas we'll take into consideration. BTW the SIP examples resides in %QTDIR%\examples\dialogs\sipdialog > BTW, are QtHelp, QtWebKit and QtXmlPatterns modules not available in > Windows CE version of Qt or there was something wrong during my > compilation? For QtXmlPatterns you must turn on exceptions while configuring Qt. Just add -exceptions to your configure command line. QtWebKit (and also Phonon) is not yet supported for Qt/WinCE (see Thiago's mail). QtHelp isn't built by default because we don't build assistant, designer and all the other tools for embedded platforms. But there shouldn't be problem to build it. Best Regards, Joerg -- [ signature omitted ]
OK, thanks. On Thu, 15 May 2008 15:24:10 +0400, Jörg Bornemann <joerg.bornemann@xxxxxxxxxxxxx> wrote: > Hi Constantin, > >> 1) that can be hard to implement, but may be maximize all top-level >> widgets (except ones like message boxes, of course) that won't get >> broken? > > That automaximizing Thomas wrote about is already implemented. Please > have a look at > http://doc.trolltech.com/4.4/qapplication.html#autoMaximizeThreshold-prop > >> 3) may be add a signal which is emitted when SIP state changes and a >> slot that'll automatically re-arrange child widgets? Or window flag >> that'll tell that this widget shouldn't be overlaped by SIP. Then >> developers could just add one line where they want automatic handling >> of input panel states. > > These are quite good ideas we'll take into consideration. > BTW the SIP examples resides in %QTDIR%\examples\dialogs\sipdialog > >> BTW, are QtHelp, QtWebKit and QtXmlPatterns modules not available in >> Windows CE version of Qt or there was something wrong during my >> compilation? > > For QtXmlPatterns you must turn on exceptions while configuring Qt. Just > add -exceptions to your configure command line. > QtWebKit (and also Phonon) is not yet supported for Qt/WinCE (see > Thiago's mail). > QtHelp isn't built by default because we don't build assistant, designer > and all the other tools for embedded platforms. But there shouldn't be > problem to build it. > > Best Regards, > > Joerg > > -- > To unsubscribe - send a mail to qt-interest-request@xxxxxxxxxxxxx with > "unsubscribe" in the subject or the body. > List archive and information: http://lists.trolltech.com/qt-interest/ -- [ signature omitted ]