July 2008 - Wine-Devel - list.winehq.org

Re: dinput: the DIK_ keycode is not the same as the scancode.

by Aric Stewart

Well the main problem is with Japanese keyboards I was testing with. Often the scan codes, nor the vkey of the keyboards did not line up the characters in the other keyboards. Yet dinput on windows correctly set the DIK codes to represent the character being pressed. An example is the key to the right of 'P'. It is scancode 0x1a on both qwerty_us and the Japanese keyboard. However on the us keyboard it is '[' while on the Japanese keyboard it is '@' (it is vkey VKEY_OEM_3, which is '`' on the us keyboard) I saw similar problems with scan 0x1B ('[' in Japanese and ']' on qwerty) 0x2b (']' vs '\') I did pretty extensive testing with shift on windows and with my code and do not recall any specific problems though most of those tests where with the Japanese keyboard. I can try some more. I am curious what SHIFT+'2' (qwerty) produces as that is '@' I am not sure of a better way to try to solve this problem without having a bunch of special case situations which struck me as bad. -aric Vitaliy Margolen wrote: > Aric Stewart wrote: >> It is mapped with the keyboard mapping to the resulting character. so >> the key 'A' is DIK_A nomatter what its scancode or vkey would be. This >> is relevent to Japanese keymapping where the '@' key is in the '[' >> location the scancode for both is 0x22 but dinput generates DIK_AT in >> japanese and DIK_LBRACKET in us_qwerty >> >> reworked to remove the giant case statement and hopefully be more clear. >> remove japan specific stuff as with the proper keyboard scancodes it >> works out. > > I'm still not clear why do you need to translate the v_key into char? This > involves a round trip to the X server for each key press. > > Besides this will depend on the state of the num-lock, shift, etc. Which > should not be the case for dinput. It should always return the same code for > the key regardless of anything else. > > Vitaliy. > >

July 30, 2008

Re: WWN announcements on WineHQ

by Francois Gouget

On Wed, 30 Jul 2008, Jeremy Newman wrote: > Not to mention, for people who subscribe to the RSS feed, it is a great > way to let them know an Issue has been released. I'm not using RSS for WineHQ so I just discovered that they are broken. The behavior I'm expecting is the same as for Slashdot's RSS feed: if I click on 'Nasa Turns 50' I get to the page for that story. But if I click on 'Wine Weekly News Issue 348', I get to the top of Wine's news page (essentially http://www.winehq.org/?news=archive) There's two issues with that: * when the page opens on my laptop the news item about WWN 348 is not even visible. So for general news items we should at least link to the relevant entry. That means adding anchors as currently there are none. * for news about WWN issues the link should point straight to the issue, rather than to the news about it. The same as clicking on a Slashodt story does not point you to the main index but to the story itself. That probably means that news items should have a url field to specify where the RSS entry should point to. -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Computers are like airconditioners They stop working properly if you open WINDOWS

July 30, 2008

Re: WWN announcements on WineHQ

by Alexandre Julliard

"Zachary Goldberg" <zgold(a)bluesata.com> writes: > How then would people find the index of WWNs? I think having that box > on the side is really convenient actually and is the only way I > usually go to get to issues. There would be a link to a separate WWN index page (the existing back issues page would do nicely). -- Alexandre Julliard julliard(a)winehq.org

July 30, 2008

Re: WWN announcements on WineHQ

by Zachary Goldberg

On Wed, Jul 30, 2008 at 10:56 AM, Alexandre Julliard <julliard(a)winehq.org> wrote: > "Zachary Goldberg" <zgold(a)bluesata.com> writes: > >> As long as we are okay that for the for the duration of time in which >> the news item is on the front page it will be redundant with the side >> box I am alright with this as well (I think this is mitigated by the >> fact that in the RSS it won't be redundant and instead will be very >> useful). > > Well, I think the side box could then be removed as Francois > suggested. That would help uncluttering the main page, and allow us to > use more space to point to FAQs etc. > > -- > Alexandre Julliard > julliard(a)winehq.org > How then would people find the index of WWNs? I think having that box on the side is really convenient actually and is the only way I usually go to get to issues.

July 30, 2008

Re: WWN announcements on WineHQ

by Alexandre Julliard

"Zachary Goldberg" <zgold(a)bluesata.com> writes: > As long as we are okay that for the for the duration of time in which > the news item is on the front page it will be redundant with the side > box I am alright with this as well (I think this is mitigated by the > fact that in the RSS it won't be redundant and instead will be very > useful). Well, I think the side box could then be removed as Francois suggested. That would help uncluttering the main page, and allow us to use more space to point to FAQs etc. -- Alexandre Julliard julliard(a)winehq.org

July 30, 2008

Re: WWN announcements on WineHQ

by Zachary Goldberg

On Wed, Jul 30, 2008 at 10:38 AM, Alexandre Julliard <julliard(a)winehq.org> wrote: > Francois Gouget <fgouget(a)free.fr> writes: > >> On http://www.winehq.org/ we have the following news items: >> >> July 13, 2008: Wine Weekly News Issue 349 >> >> WWN Issue 349 was released today. >> >> June 18, 2008: Wine Weekly News Issue 348 >> >> WWN Issue 348 was released today. >> >> >> That's pretty lame. Should either have a 2 or 3 sentence summary for the >> WWN releases, or simply reuse the index we show in the 'Weekly >> Newsletters' box. > > I think reusing the index is a good idea, it's short enough to include > in a news item and it gives a good overview of the contents of that > issue. > > -- > Alexandre Julliard > julliard(a)winehq.org > > > As long as we are okay that for the for the duration of time in which the news item is on the front page it will be redundant with the side box I am alright with this as well (I think this is mitigated by the fact that in the RSS it won't be redundant and instead will be very useful). I can modify my scripts to include the index in the news item that I send in with the patch. Zachary Goldberg Computer Science & Engineering Electrical Captain of Penn Electric Race Team School of Engineering at the University of Pennsylvania

July 30, 2008

Re: WWN announcements on WineHQ

by Alexandre Julliard

Francois Gouget <fgouget(a)free.fr> writes: > On http://www.winehq.org/ we have the following news items: > > July 13, 2008: Wine Weekly News Issue 349 > > WWN Issue 349 was released today. > > June 18, 2008: Wine Weekly News Issue 348 > > WWN Issue 348 was released today. > > > That's pretty lame. Should either have a 2 or 3 sentence summary for the > WWN releases, or simply reuse the index we show in the 'Weekly > Newsletters' box. I think reusing the index is a good idea, it's short enough to include in a news item and it gives a good overview of the contents of that issue. -- Alexandre Julliard julliard(a)winehq.org

July 30, 2008

d3dx9: Add stubs for the ID3DXSprite functions

by David Adam

Since the prototype for D3DXCreateSprite in d3dx9 and d3dx8 are not compatible, it would be worth to do the implementation in parallel (that is in the same patch), instead of duplicating the d3dx9 patch into the d3dx8 one. David

July 30, 2008

Re: WWN announcements on WineHQ

by Jeremy Newman

Not to mention, for people who subscribe to the RSS feed, it is a great way to let them know an Issue has been released. I'm not opposed to adding more of a summary of the issue though. While we are on this topic, I have thought about renaming WWN - Wine Weekly News to: * drum roll * World Wine News Thoughts? Zachary Goldberg wrote: > On Wed, Jul 30, 2008 at 4:53 AM, Francois Gouget <fgouget(a)free.fr> wrote: >> On http://www.winehq.org/ we have the following news items: >> >> July 13, 2008: Wine Weekly News Issue 349 >> >> WWN Issue 349 was released today. >> >> June 18, 2008: Wine Weekly News Issue 348 >> >> WWN Issue 348 was released today. >> >> >> That's pretty lame. Should either have a 2 or 3 sentence summary for the >> WWN releases, or simply reuse the index we show in the 'Weekly >> Newsletters' box. > > I actually think that while very trite, the updates are fairly > appropriate. An "at a glance" view of the homepage (and in the RSS > Feeds) you can tell a new WWN was released. And if your actually at > the winehq homepage you can see if you're interested in reading it > (you always should be :) ) by checking out the ToC in the WWN Box on > the right. > >> Actually with the combination of proper news items and the back issues >> page, that box would be pretty redundant. Maybe we should remove it? >> > > I agree listing ToC would be redundant, perhaps listing the weekly > "purpose of this issue" in that box would add some flare while being > less boring and not replicating the side box? > > -Zach > >

July 30, 2008

RE: ddraw/tests: Skip cubemap tests when cubemap isn't supported.

by Stefan Dösinger

> There are some tests after that block not related to cubemap which I > don't want > to skip. Other options are moving cubemap block of code to the end (so > that I > can return then) or skipping the block by goto, but none of this are > really > better IMO. DeviceLoadTest is quite big, does splitting up make sense? Otherwise, what you say is fair enough - I do not care too much about code beauty in the tests as long as the tests work(since one hardly ever reads the test or does lots of work on it, and the Windows apps we run are often crappy as well)

July 30, 2008