Re: [warzone2100-dev] Qt merge results + what to do on the mac
On 5/18/10, buginator wrote:
> Actually, looking at the examples, none of those do what we do, so
> that isn't really a valid comparison. Possible Qt bug, or driver, or
> it is just a quirk that it works on windows & linux.
>
Possibly related?
http://bugreports.qt.nokia.com/browse/QTBUG-9706
https://bugs.launchpad.net/stellarium/+bug/521134
So far, it seems that in wzapp.cpp, line 206
bold.setFamily("DejaVu Sans");
bold.setPixelSize(21);
bold.setBold(true);
if you do
bold.setFamily("DejaVu Sans");
bold.setPixelSize(21);
// bold.setBold(true);
It is a bit better, but it is looking more & more like a mac Qt bug.
I also am curious if Dak and or Zarel could try:
bold.setFamily("DejaVuSans");
bold.setPixelSize(21);
// bold.setBold(true);
and see if the issue is still there or not, if not, re-enable the
setBold line, and see if that works.
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Qt merge results + what to do on the mac
On May 18, 2010, at 8:05 PM, buginator wrote: > The reserved key issues is also troublesome, and we are getting into > more mac specific hacks to avoid those (if that is possible). All we really need to do is make sure that we do not use any of them by default as those key combos will never actually get to us. -- My Web Sites: http://dak180.dynalias.com:8080/ smime.p7s Description: S/MIME cryptographic signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Qt merge results + what to do on the mac
On 5/18/10, dak180 wrote: > On the font corruption issue, as the Qt example programs seem to have on > issues on the mac and that it only effects the menu title text and not any of > the others I doubt that it is a driver issue. > Actually, looking at the examples, none of those do what we do, so that isn't really a valid comparison. Possible Qt bug, or driver, or it is just a quirk that it works on windows & linux. > On the mater of input issues my take is that the way Qt does things is the > right way to go. > Where one would use the ctrl key on other operating systems one uses the cmd > key on the mac; for example to paste on the mac one uses cmd+v, not ctrl+v. > Since this is working right now and making it work otherwise would involve > ugly hacks I do not think this should be changed. > The only thing to keep in mind is that there are three reserved shortcuts: > cmd+q (quits the program), cmd+h (hides the program) & opt+cmd+h (hides all > other programs). > > The mac option (⌥) key is traditionally a tricky beast as it preforms the > functions of both the alt key and the altgr key, as such the option key is > never used by its self in a shortcut but rather in combination with the cmd > (⌘). > Either way, we will have to have mac specific hacks, and if we go the non SDL way, then we need to update the docs for mac users. The reserved key issues is also troublesome, and we are getting into more mac specific hacks to avoid those (if that is possible). ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [warzone2100-dev] Qt merge results + what to do on the mac
On May 17, 2010, at 8:31 PM, buginator wrote: > Now, for the mac, the main issues left are, the font textures get > corrupted as can be seen in this ticket: > http://developer.wz2100.net/ticket/1549 > > Dak's screen shot with the corruption is here: > http://developer.wz2100.net/attachment/ticket/1549/2010-05-15at3.44.04PM.png > > Speaking of corruption, Segg2 also posted a corrupted image here: > http://developer.wz2100.net/attachment/ticket/1549/qt-ss02.png > > I *think* the issue in both of those might be driver related, it > doesn't happen on linux or windows. Well, Segg2 is also on linux, but > I still think that is driver related. > > The input issues for the mac are a bit more confusing. > The issue is, on macs (using Qt), ctrl key = cmd key, and cmd key = > ctrl key, and alt key = option key. On the font corruption issue, as the Qt example programs seem to have on issues on the mac and that it only effects the menu title text and not any of the others I doubt that it is a driver issue. On the mater of input issues my take is that the way Qt does things is the right way to go. Where one would use the ctrl key on other operating systems one uses the cmd key on the mac; for example to paste on the mac one uses cmd+v, not ctrl+v. Since this is working right now and making it work otherwise would involve ugly hacks I do not think this should be changed. The only thing to keep in mind is that there are three reserved shortcuts: cmd+q (quits the program), cmd+h (hides the program) & opt+cmd+h (hides all other programs). The mac option (⌥) key is traditionally a tricky beast as it preforms the functions of both the alt key and the altgr key, as such the option key is never used by its self in a shortcut but rather in combination with the cmd (⌘). The ctrl key is primarily used on the mac with the mouse to generate a right-click event; which I can tell you already works as expected on the mac. On the topic of what do other game do, particularly ones that are cross platform, my experience has been that if they use modifier keys at all they do not use them as modifier keys, only as normal key presses. -- My Web Sites: http://dak180.users.sourceforge.net/ smime.p7s Description: S/MIME cryptographic signature ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
[warzone2100-dev] Qt merge results + what to do on the mac
For those that haven't been looking at the commit logs, we have two new branches. qt-trunk = svn/trunk + svn/qt (imagine that!) codename = svn/trunk @ r10808 Both need to be kept in sync with svn/trunk, until we can kill off qt-trunk when the mac issues are fixed. The main reason for the codename is, we do not know if we will use SDL or if we will just use Qt, then once we decide, we can branch into 3.0 or whatever. Now, for the mac, the main issues left are, the font textures get corrupted as can be seen in this ticket: http://developer.wz2100.net/ticket/1549 Dak's screen shot with the corruption is here: http://developer.wz2100.net/attachment/ticket/1549/2010-05-15at3.44.04PM.png Speaking of corruption, Segg2 also posted a corrupted image here: http://developer.wz2100.net/attachment/ticket/1549/qt-ss02.png I *think* the issue in both of those might be driver related, it doesn't happen on linux or windows. Well, Segg2 is also on linux, but I still think that is driver related. The input issues for the mac are a bit more confusing. The issue is, on macs (using Qt), ctrl key = cmd key, and cmd key = ctrl key, and alt key = option key. This is NOT the way SDL had it, SDL had it ctrl=ctrl and alt=alt on the macs. If we stick with the SDL way, then we must remap the input key so ctrl = ctrl. If not, then we remap cmd=ctrl and ctrl = cmd. I prefer we keep the SDL way, since that requires less code changes, but I am not a mac user. Mac users, speak up on what you want, or the default will be the SDL way. Lastly, the final (and most important) issue for the mac is, it don't seem to handle ALT+h (for example), it shows the alt key was down, but the h key gets lost...ctrl +1 works (cmd+1) ... and it works OK on windows & linux so ? ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
