You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
browser now wraps row content and it results in an overlapped mess #1658
When view the contents of a table the latest release now auto wraps the contents of cells.
It overlaps and results in a mess. Is this by design? Can I change it back?
The latest nightly, or the 3.11.0-beta3 I pushed out a few hours ago? Asking because one is probably just a development thing we can adjust easily, the other I might need to panic about a bit. 😄
@mtissington - you seem to be raising lots of issues recently, which is fantastic - each raised issue means another squished bug, making the application better. Great. However, you don't seem to be supplying the correct information.
When raising an issue, do you go to the issues page? If so, do you click the green 'new issues' button?
Or do you click 'New Issue' in DB4S? Either way, this should create a 'template' here with information to fill in:
The bit at the end is the useful information:
The version you're using and your OS are important - some issues are only apparent on specific operating systems.
If you're raising issues via another method, it would be handy to know how, so we can tailor that method to include the above information.
Again, we appreciate your issues, so this isn't a moan about you raising them - just how you're raising them! 😉
Press the colon key, and type a word. :moneybags: for example. as you type, a list of matches should be displayed. I think somewhere there is a difinitive list.
I just noticed that trigger_uuid field is shown without wrapping - they are all TEXT fields.
The UUID fields have nothing to break a line up - no spaces, commas or other punctuation.
I'm hoping its just a default option that's changed between Qt versions - the old control defaulted to 'one line per cell' while the newer one is 'fit contents in cell'...
Yes, just noticed this with the last few nightlies. 😱
The browser grid is now too busy. Line wrap is not required given the cell editor provides the necessary detail in a larger gadget to the right.
I was searching a bit for one already open and It's surprising that there isn't one, because what we do is nothing particular. The wordWrap attribute is enabled by default for QTableWidget.
It'd be necessary to remove the workaround that I made for disabling
wrapping for Qt greater than 5.12, or maybe better at the short term,
close the version range for which it's applied.
The workaround (disabled word wrap) is now only applied for versions greater or equal than 5.12.0 and lower than 5.12.3. If we compile using 5.12.3 will be able to confirm whether it has been fixed.
Since it seems like to be fixed now (in Qt itself and by a workaround in our code), I'm going to close this issue 😄 If I'm missing anything or if anybody is still having issues with this, please just reopen this issue.
Activity
justinclift commentedon Dec 13, 2018
The latest nightly, or the 3.11.0-beta3 I pushed out a few hours ago? Asking because one is probably just a development thing we can adjust easily, the other I might need to panic about a bit. 😄
mtissington commentedon Dec 13, 2018
nightly - 3.11.99
chrisjlocke commentedon Dec 13, 2018
@mtissington - you seem to be raising lots of issues recently, which is fantastic - each raised issue means another squished bug, making the application better. Great. However, you don't seem to be supplying the correct information.
When raising an issue, do you go to the issues page? If so, do you click the green 'new issues' button?
Or do you click 'New Issue' in DB4S? Either way, this should create a 'template' here with information to fill in:
The bit at the end is the useful information:
The version you're using and your OS are important - some issues are only apparent on specific operating systems.
If you're raising issues via another method, it would be handy to know how, so we can tailor that method to include the above information.
Again, we appreciate your issues, so this isn't a moan about you raising them - just how you're raising them! 😉
mtissington commentedon Dec 13, 2018
Oops - sorry, I'll ready the template next time, heck I'm often moaning at our testers here for lack of correct and full information.
chrisjlocke commentedon Dec 13, 2018
If you click 'Help' and 'About', the version information can be selected, copied and pasted.
v3.11.99 denotes any nightly, so the date you downloaded it would be handier.
Sometimes what you download as the 'latest' may be different by the time we see your report.
No problem, and again, not moaning - it can just speed up the troubleshooting process if we know what you're having a problem with. 🙉
chrisjlocke commentedon Dec 13, 2018
Back to your issue though.
Any chance of a screenshot? I can't see this in the version I'm running.
mtissington commentedon Dec 13, 2018
I'm curious - how do you manage to insert emjois - I see no ability to do so on github.
chrisjlocke commentedon Dec 13, 2018
Press the colon key, and type a word. :moneybags: for example. as you type, a list of matches should be displayed. I think somewhere there is a difinitive list.
mtissington commentedon Dec 13, 2018
Thanks - here is the screen grab

I just noticed that trigger_uuid field is shown without wrapping - they are all TEXT fields.
chrisjlocke commentedon Dec 13, 2018
Aah, you mean a cell now contains about 2 lines of text?
Edit: You beat me to it...
chrisjlocke commentedon Dec 13, 2018
A nightly from Nov showed just one line in a cell.
We've upgraded Qt recently, so assume its something to do with that, and must be an option thats settable.
justinclift commentedon Dec 13, 2018
Uh oh. The new 3.11.0-beta* builds are using Qt 5.12.0 too. I guess we'll need to get this fixed for the main release as well.
chrisjlocke commentedon Dec 17, 2018
The UUID fields have nothing to break a line up - no spaces, commas or other punctuation.
I'm hoping its just a default option that's changed between Qt versions - the old control defaulted to 'one line per cell' while the newer one is 'fit contents in cell'...
justinclift commentedon Dec 19, 2018
Hmmm, maybe the new 3.11.0 release should use Qt 5.11.x instead? That's still very current, and shouldn't have this problem.
sky5walk commentedon Dec 19, 2018
Yes, just noticed this with the last few nightlies. 😱
The browser grid is now too busy. Line wrap is not required given the cell editor provides the necessary detail in a larger gadget to the right.
35 remaining items
chrisjlocke commentedon Dec 25, 2018
Have created an issue (#1688) as its useful to discuss and comment there, but I guess a Wiki page (sans comments and guff) would be useful.
karim commentedon Dec 25, 2018
GitHub added an option to pin issues (up to 3) so they appear on top. Should we pin this issue?
justinclift commentedon Dec 25, 2018
Might as well. It'll probably mostly affect people using 3.11.0-beta3, as the more recent nightlies won't have the problem.
When the final 3.11.0 release is out (soon), we can probably unpin it. 😄
justinclift commentedon Feb 8, 2019
@MKleusberg @mgrojo Would either of you have time to file a bug for this with Qt?
I don't grok the details of QtTableView well enough to really fill out an appropriate bug. 😦
On a side note - I asked about this problem today on the #qt IRC channel, but no response. Doh.
mgrojo commentedon Feb 9, 2019
I've created a Qt bug report for the wrapping problem: https://bugreports.qt.io/browse/QTBUG-73721
I was searching a bit for one already open and It's surprising that there isn't one, because what we do is nothing particular. The wordWrap attribute is enabled by default for QTableWidget.
Disable word wrapping in the Browse Data table when using Qt 5.2.x
justinclift commentedon Mar 9, 2019
The Qt project have marked their bug for this as fixed today (target release is 5.12.3), via this patch:
qt/qtbase@8b3463f
Really hoping it's a complete patch. Not sure how we should go about testing it prior to the release.
Guessing a local build of Qt (using their development code), then compiling DB4S using that.
mgrojo commentedon Mar 9, 2019
justinclift commentedon May 7, 2019
Qt 5.12.3 has been released, so we should probably test if the content wrapping works properly with it.
I won't have time for the next few days though. Hopefully next week. 😄
Close version range to apply workaround for QTBUG-73721
mgrojo commentedon May 7, 2019
The workaround (disabled word wrap) is now only applied for versions greater or equal than 5.12.0 and lower than 5.12.3. If we compile using 5.12.3 will be able to confirm whether it has been fixed.
justinclift commentedon May 8, 2019
Thanks @mgrojo, that's excellent. 😄
MKleusberg commentedon Aug 10, 2019
Looks like we can close this issue then?
MKleusberg commentedon Oct 4, 2019
Since it seems like to be fixed now (in Qt itself and by a workaround in our code), I'm going to close this issue 😄 If I'm missing anything or if anybody is still having issues with this, please just reopen this issue.