Thanks Ton, Do you mean an dynamically allocated struct? I will try to make the modifications. :D
Rafael Ortis 2011/1/1 Ton Roosendaal <t...@blender.org>: > Hi, > > OH; forgot for point 1) > Just make it point to an allocated struct, that way things don't get > saved in files. > > -Ton- > > ------------------------------------------------------------------------ > Ton Roosendaal Blender Foundation t...@blender.org www.blender.org > Blender Institute Entrepotdok 57A 1018AD Amsterdam The Netherlands > > On 1 Jan, 2011, at 17:12, Ton Roosendaal wrote: > >> Hi, >> >> Good news! >> >> 1) That's Ok for now, but mark it with /* XXX hack */ to point at that >> this is potentially wip stuff. Making a struct would be nice too, >> probably each float has a real meaning, that makes the code readable. >> >> 2) If aligning fails, always add variables with a name like "pad". In >> your case a single "int pad;" is sufficient >> >> General note: in 2.49 the code for ndof was spread all around, with >> exception handling for tools and view manipulations. We really don't >> want this back, but have the NDOF device deliver nice and well defined >> events instead. These then can become keymappable. >> >> In order to have a NDOF device work *while* using tools (paint, rotate >> view), we need to add still a parallel queue handling in Blender. >> Multitouch devices need this too, and there's already been some work >> on it. I'd advice to not try this for now, I rather have this work >> done after we've put wm_eventsystem.c completely in sane design. >> There's too many loose ends there now. :) >> >> -Ton- >> >> ------------------------------------------------------------------------ >> Ton Roosendaal Blender Foundation t...@blender.org >> www.blender.org >> Blender Institute Entrepotdok 57A 1018AD Amsterdam The >> Netherlands >> >> On 1 Jan, 2011, at 14:54, Rafael Ortis wrote: >> >>> I am working on a patch to restore 3d Connexion ndof feature in >>> blender 2.5. >>> >>> My patch is based on the 2.49b version and right now i have been able >>> to restore only the original mode. The other limitation is that >>> blender will only seek for the "3DxNdofBlender.plug" in the current >>> installation folder and not in the user's ~./blender/plugins folder. >>> >>> Since I'm really new to blender code i have some questions: >>> >>> 1. In version 2.49b the last known ndof device state was on window >>> struct : >>> ... >>> float ndof[7]; >>> ... >>> >>> I have placed this in wmWindow. Was this the right place? >>> >>> 2. This modification in wmWindow breaks the alignment of the struct >>> so >>> i have added a 4 bytes with: >>> >>> short ndofAlign[2]; >>> >>> Is this OK? >>> >>> >>> I'm using: >>> >>> Linux (Ubuntu 10.10) >>> gcc version: (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5 >>> 3DConnexion device: Space Navigator >>> 3DConnexion driver: 3DConnecion linux version >>> >>> Happy new year!!! >>> >>> att. >>> Rafael Ortis >>> <patch.txt>_______________________________________________ >>> Bf-committers mailing list >>> Bf-committers@blender.org >>> http://lists.blender.org/mailman/listinfo/bf-committers >> >> _______________________________________________ >> Bf-committers mailing list >> Bf-committers@blender.org >> http://lists.blender.org/mailman/listinfo/bf-committers > > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list Bf-committers@blender.org http://lists.blender.org/mailman/listinfo/bf-committers
