plib-devel Mailing List for PLIB
Brought to you by:
sjbaker
Menu
▾
▴
plib-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
(80) |
Mar
(128) |
Apr
(111) |
May
(157) |
Jun
(70) |
Jul
(116) |
Aug
(465) |
Sep
(574) |
Oct
(325) |
Nov
(163) |
Dec
(182) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(167) |
Feb
(191) |
Mar
(319) |
Apr
(118) |
May
(252) |
Jun
(427) |
Jul
(187) |
Aug
(96) |
Sep
(219) |
Oct
(161) |
Nov
(109) |
Dec
(210) |
| 2002 |
Jan
(97) |
Feb
(80) |
Mar
(143) |
Apr
(234) |
May
(72) |
Jun
(246) |
Jul
(155) |
Aug
(280) |
Sep
(418) |
Oct
(81) |
Nov
(72) |
Dec
(88) |
| 2003 |
Jan
(59) |
Feb
(63) |
Mar
(33) |
Apr
(27) |
May
(87) |
Jun
(50) |
Jul
(97) |
Aug
(45) |
Sep
(35) |
Oct
(67) |
Nov
(78) |
Dec
(13) |
| 2004 |
Jan
(167) |
Feb
(144) |
Mar
(172) |
Apr
(93) |
May
(43) |
Jun
(7) |
Jul
(27) |
Aug
(36) |
Sep
(48) |
Oct
(54) |
Nov
(5) |
Dec
(44) |
| 2005 |
Jan
(53) |
Feb
(36) |
Mar
(13) |
Apr
(3) |
May
(19) |
Jun
|
Jul
(49) |
Aug
(39) |
Sep
(8) |
Oct
(8) |
Nov
(51) |
Dec
(23) |
| 2006 |
Jan
(26) |
Feb
(5) |
Mar
(26) |
Apr
(26) |
May
(52) |
Jun
(36) |
Jul
(8) |
Aug
(12) |
Sep
(6) |
Oct
(75) |
Nov
(34) |
Dec
(25) |
| 2007 |
Jan
(46) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(7) |
Jul
(2) |
Aug
|
Sep
(40) |
Oct
(9) |
Nov
(3) |
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
(26) |
Apr
|
May
|
Jun
(2) |
Jul
(4) |
Aug
(6) |
Sep
|
Oct
|
Nov
(5) |
Dec
(2) |
| 2009 |
Jan
(63) |
Feb
(4) |
Mar
(12) |
Apr
|
May
(5) |
Jun
(1) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(14) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
(2) |
Feb
(1) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
| 2012 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Kevin Z. <kev...@gm...> - 2013-05-25 23:01:22
|
Hi there, Today I decided to start playing around with the plib sources to try to get my joystick working correctly on my FreeBSD system. Whether I will be successful or not is another discussion. I got annoyed at the warning messages that autoconf was throwing at me every time I regenerated the build system via `autogen.sh`, so I decided that I should get rid of them. Attached is a patch of my results as a svn-diff to the latest revision in the repository. Here is a short summary of the changes made: - Rename "configure.in" to "configure.ac" - Split up AM_INIT_AUTOMAKE into AC_INIT and another AM_INIT_AUTOMAKE - Add svn:ignore entries to each directory to ignore build system - Substitute all cases of "INCLUDES" in Makefile.am to "AM_CPPFLAGS" These changes shouldn't be too drastic, would somebody please commit this patch? Thanks! Also, while I was doing my hacking, I realized that using version control would be very helpful. Given that I'm not ready to commit stuff, I still nevertheless want to plan out how to send stuff upstream once I'm done. Ideally, I'd like to mess around with something like Git, but if nobody has any objections I may just send in a bunch of patch files. That's assuming I get somewhere, though. Thanks, Kevin Zheng |
|
From: Steve B. <st...@sj...> - 2012-11-08 20:40:44
|
> Questions: (There are ten questions.) > > 1. How long have you been a software developer? 40 years. > 2. How long have you been affiliated with PLIB? Were you part of > the original development team for this software? I was the original author. I wrote it 16 years ago. > 3. What is the size of the current code base? 40,000 lines of code. > 4. Did you follow a coding standard when developing this > software? Is it a standard determined by your group? No. > 5. What did you use to manage bug reports in your software? Does > it satisfy your requirements? Are there other software options that > you would consider switching to? We used email to the development team and nothing else. These days, I'd use bugzilla. > 6. Did you use any compiler options to detect integer overflow > vulnerabilities? Do you think that they are useful? No. Graphics software needs as much raw speed as it can get - I turn off everything like that. > 7. Did you use any automated (static or dynamic analysis) tools > to detect buffer overflows, integer overflows, or any other bugs? > Which tools did you use? Why these tools? No. We did not use any tools like that. > 8. Did you use fuzzing? Which tools did you use and why? If you > wrote your own fuzzer, why did you write it yourself? Was it written > from scratch or by extending some other fuzzing tools? No. > 9. Did you have specific phases during development where you > concentrated on fixing security issues? Did you have a test suite, > unit tests, or regression tests? No. > 10. Buffer overflows often result from the use of unsafe functions, > such as strcpy. Does your software use those? If you use a different > string library, why is it used? Is it an in-house library or an > off-the-shelf library? Did you migrate your code to use the string > library? Probably - it's a graphics package so there is almost zero string manipulation. -- Steve |
|
From: Auburn S. <sse...@gm...> - 2012-11-08 17:38:42
|
Hi All, I am a graduate student at Auburn University, working with Dr. Munawar Hafiz. We are working on an empirical study project to understand the software engineering practices used in companies that produce secure software. In particular, we are concentrating on how developers write code to prevent buffer overflow and integer overflow vulnerabilities. We are interested in the software development process: how you develop software, how you test and analyze programs to detect vulnerabilities, and what processes you follow to remove bugs. We are looking into automated tools that software developers use, and are expecting that there is a common insight in the security engineering process that can be reusable. We request your assistance by participating in this research study. We would greatly appreciate it if you would share your experience with us by answering the questions at the end of this email. We may send some follow up questions based on your response in future. Your response(s) will be kept confidential, and will only be aggregated with those of other responders. Please let us know if you have any questions or concerns regarding the study. Thanks in advance for your support. Yasmeen Rawajfih Software Analysis, Transformations and Security Group Auburn University Working under the supervision of: Dr. Munawar Hafiz Assistant Professor Dept. of Computer Science and Software Engineering Auburn University Auburn, AL http://munawarhafiz.com/ Questions: (There are ten questions.) 1. How long have you been a software developer? 2. How long have you been affiliated with PLIB? Were you part of the original development team for this software? 3. What is the size of the current code base? 4. Did you follow a coding standard when developing this software? Is it a standard determined by your group? 5. What did you use to manage bug reports in your software? Does it satisfy your requirements? Are there other software options that you would consider switching to? 6. Did you use any compiler options to detect integer overflow vulnerabilities? Do you think that they are useful? 7. Did you use any automated (static or dynamic analysis) tools to detect buffer overflows, integer overflows, or any other bugs? Which tools did you use? Why these tools? 8. Did you use fuzzing? Which tools did you use and why? If you wrote your own fuzzer, why did you write it yourself? Was it written from scratch or by extending some other fuzzing tools? 9. Did you have specific phases during development where you concentrated on fixing security issues? Did you have a test suite, unit tests, or regression tests? 10. Buffer overflows often result from the use of unsafe functions, such as strcpy. Does your software use those? If you use a different string library, why is it used? Is it an in-house library or an off-the-shelf library? Did you migrate your code to use the string library? |
|
From: Alex D-H. <fg...@be...> - 2012-08-24 22:49:15
|
Hi Wolfram, thank you very much, compilation works like a charm again. Alex |
|
From: Wolfram K. <w_...@rz...> - 2012-08-24 13:56:15
|
Thanks for the report. Both the "diagnose" and "therapie" are correct and I committed a fixed version. Bye bye, Wolfram. |
|
From: Alex D-H. <fg...@be...> - 2012-08-19 20:30:28
|
Hi, one of the latest commits broke compilation for me. Make aborts with error: g++ -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"plib\" -DVERSION=\"1.8.5\" -DHAVE_LIBPTHREAD=1 -DHAVE_LIBGL=1 -DHAVE_LIBDL=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -I. -I../../src/sg -I../../src/util -g -O2 -Wall -MT ssgAnimation.o -MD -MP -MF .deps/ssgAnimation.Tpo -c -o ssgAnimation.o ssgAnimation.cxx In file included from ssgLocal.h:27, from ssg.cxx:26: ssg.h:2879:6: error: #elif with no expression In file included from ssgLocal.h:27, from ssgAnimation.cxx:25: ssg.h:2879:6: error: #elif with no expression make[2]: *** [ssgAnimation.o] Fehler 1 The guys on flightgear irc pointed out that changing line 2879 of file src/ssg/ssg.h from "#elif" to "#else" fixes the issue. Thank you Alex |
|
From: Phil <ph...@ca...> - 2012-02-23 21:35:05
|
Hi, Even if plib is no longer maintained, I think a warning of some sort on the web page regarding the deletion of dialogbox objets and derivative would spare a lot of efforts to coders like me following the guidelines. http://plib.sourceforge.net/pui/index.html#puDialogBox /puDeleteObject/ did the trick. But how much can I trust this will run any time ? --Phil |
|
From: Paolo L. <p.l...@ci...> - 2011-12-23 15:35:27
|
Dears, If you are interested in, I can in extremis contribute a VBO kind of leaf. Since I have it ready and debugged it would take few days in the Christmas holidays, yet what should be discussed and agreed is how to propose it in the API, i.e. a new leaf type or replacement of the ssgVtxArray (presently the leaf type is still ssgVtxArray yet the underlying mechanism is VBO. Anyway we'd need to complete ssgVtxArray's methods with a new one dealing with update/usage strategy, or it could even be set globally (e.g. ssgSetVBOUsageMode). I can also contribute with a pair of shaders (vertex, fragment) which actually emulates standard fixed-function rendering pipeline functionalities (+ bump mapping, spherical env mapping, and hardware shadow mapping), but presently I manage shaders by pre/post draw callbacks, so some work would be necessary to integrate this mechanism at state application. Just let me know if we want to offer the gloriuos Plib this last effort, yet I realize that the shader one has a large impact and could leave the library with insufficient debug in its last version. Paolo PS: I can also contribute interfaces to the CyberX3D (VRML2/97, X3D) and to the Assimp (many) model loading libraries. They significantly enlarge the SSG 3D format loading capabilities with modern, more reliable or witha more complete support loaders. Do 'contrib' section in the SVN? > -----Messaggio originale----- > Da: Steve Baker [mailto:st...@sj...] > Inviato: giovedì 22 dicembre 2011 17.35 > A: PLIB Developers > Oggetto: Re: [Plib-devel] Is there any plan to release 1.8.6? > > PLIB is no longer being maintained - it would take too much > work to bring it up to the latest OpenGL standards. > > I don't plan any more releases. I recommend that FlightGear > pulls their current version into their repository and make it > a part of FlightGear itself. > > -- Steve > > Jari Häkkinen wrote: > > Hi all, > > > > PLIB development is slow and it is a long time since the > 1.8.5 release. > > It would be nice to have a 1.8.6 version released since > there are some > > fixes in the source code repository that resolves issues for > > flightgear > > (http://www.flightgear.org) users. The flightgear project > is preparing > > for a new release after new year. > > > > Can someone of the maintainers please release 1.8.6? It should be > > fairly straightforward and I am willing to you with the release. > > > > > > Cheers, > > > > Jari > > > > > ---------------------------------------------------------------------- > > -------- > > Write once. Port to many. > > Get the SDK and tools to simplify cross-platform app development. > > Create new or port existing apps to sell to consumers worldwide. > > Explore the Intel AppUpSM program developer opportunity. > > appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev > > _______________________________________________ > > plib-devel mailing list > > pli...@li... > > https://lists.sourceforge.net/lists/listinfo/plib-devel > > > > > -- Steve > > > -------------------------------------------------------------- > ---------------- > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app > development. Create new or port existing apps to sell to > consumers worldwide. Explore the Intel AppUpSM program > developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > plib-devel mailing list > pli...@li... > https://lists.sourceforge.net/lists/listinfo/plib-devel > |
|
From: Martin S. <Mar...@mg...> - 2011-12-22 17:42:07
|
"Steve Baker" wrote: > I don't plan any more releases. I recommend that FlightGear pulls their > current version into their repository and make it a part of FlightGear > itself. That's already been pursued in certain parts, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- |
|
From: Fay, J. F Dr C. U. A. AAC/X. <joh...@eg...> - 2011-12-22 17:27:25
|
Sic transit gloria mundi. John F. Fay Technical Fellow, Modeling and Simulation Jacobs Technology / TEAS Group P.O. Box 1935, Eglin AFB, FL 32542-5000 850-883-3496 -----Original Message----- From: Steve Baker [mailto:st...@sj...] Sent: Thursday, December 22, 2011 10:35 AM To: PLIB Developers Subject: Re: [Plib-devel] Is there any plan to release 1.8.6? PLIB is no longer being maintained - it would take too much work to bring it up to the latest OpenGL standards. I don't plan any more releases. I recommend that FlightGear pulls their current version into their repository and make it a part of FlightGear itself. -- Steve Jari Häkkinen wrote: > Hi all, > > PLIB development is slow and it is a long time since the 1.8.5 release. > It would be nice to have a 1.8.6 version released since there are some > fixes in the source code repository that resolves issues for flightgear > (http://www.flightgear.org) users. The flightgear project is preparing > for a new release after new year. > > Can someone of the maintainers please release 1.8.6? It should be fairly > straightforward and I am willing to you with the release. > > > Cheers, > > Jari > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > plib-devel mailing list > pli...@li... > https://lists.sourceforge.net/lists/listinfo/plib-devel > -- Steve ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ plib-devel mailing list pli...@li... https://lists.sourceforge.net/lists/listinfo/plib-devel |
|
From: Steve B. <st...@sj...> - 2011-12-22 17:08:35
|
PLIB is no longer being maintained - it would take too much work to bring it up to the latest OpenGL standards. I don't plan any more releases. I recommend that FlightGear pulls their current version into their repository and make it a part of FlightGear itself. -- Steve Jari Häkkinen wrote: > Hi all, > > PLIB development is slow and it is a long time since the 1.8.5 release. > It would be nice to have a 1.8.6 version released since there are some > fixes in the source code repository that resolves issues for flightgear > (http://www.flightgear.org) users. The flightgear project is preparing > for a new release after new year. > > Can someone of the maintainers please release 1.8.6? It should be fairly > straightforward and I am willing to you with the release. > > > Cheers, > > Jari > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > plib-devel mailing list > pli...@li... > https://lists.sourceforge.net/lists/listinfo/plib-devel > -- Steve |
|
From: Jari H. <ja...@fl...> - 2011-12-22 13:01:50
|
Hi all, PLIB development is slow and it is a long time since the 1.8.5 release. It would be nice to have a 1.8.6 version released since there are some fixes in the source code repository that resolves issues for flightgear (http://www.flightgear.org) users. The flightgear project is preparing for a new release after new year. Can someone of the maintainers please release 1.8.6? It should be fairly straightforward and I am willing to you with the release. Cheers, Jari |
|
From: Ralf H. <ra...@ha...> - 2011-04-29 09:52:45
|
Hi, the appended patch adds cmake support http://www.cmake.org to plib. cmake supports allows to build static plib out of the box on windows for several compilers . The following generators are available on this platform: Borland Makefiles = Generates Borland makefiles. MSYS Makefiles = Generates MSYS makefiles. MinGW Makefiles = Generates a make file for use with mingw32-make. NMake Makefiles = Generates NMake makefiles. NMake Makefiles JOM = Generates JOM makefiles. Unix Makefiles = Generates standard UNIX makefiles. Visual Studio 10 = Generates Visual Studio 10 project files. Visual Studio 10 Win64 = Generates Visual Studio 10 Win64 project files. Visual Studio 6 = Generates Visual Studio 6 project files. Visual Studio 7 = Generates Visual Studio .NET 2002 project files. Visual Studio 7 .NET 2003 = Generates Visual Studio .NET 2003 project files. Visual Studio 8 2005 = Generates Visual Studio .NET 2005 project files. Visual Studio 8 2005 Win64 = Generates Visual Studio .NET 2005 Win64 project files. Visual Studio 9 2008 = Generates Visual Studio 9 2008 project files. Visual Studio 9 2008 Win64 = Generates Visual Studio 9 2008 Win64 project files. Watcom WMake = Generates Watcom WMake makefiles. CodeBlocks - MinGW Makefiles= Generates CodeBlocks project files. CodeBlocks - NMake Makefiles= Generates CodeBlocks project files. CodeBlocks - Unix Makefiles = Generates CodeBlocks project files. Eclipse CDT4 - MinGW Makefiles = Generates Eclipse CDT 4.0 project files. Eclipse CDT4 - NMake Makefiles = Generates Eclipse CDT 4.0 project files. Eclipse CDT4 - Unix Makefiles = Generates Eclipse CDT 4.0 project files. This patch obsolates the recently used *.dsp and *.dsw files, because they could be generated by a specific cmake generator (=Visual Studio xxx) It would be nice if cmake support would be a part of further releases of plib. Regards Ralf |
|
From: Paolo L. <p.l...@ci...> - 2011-03-23 08:40:30
|
John,
you did a good job, thanks
Paolo
_____
Da: John Fay [mailto:joh...@cy...]
Inviato: martedì 22 marzo 2011 13.02
A: PLIB Developers
Oggetto: Re: [Plib-devel] Padding support in the SSG BMP loader
Paolo,
Under the heading of "better late than never," I have put your patch in.
It was a "diff" rather than a "svn diff" file so I had to massage it a bit,
so please make sure I have done it right.
- John
On 2/26/2011 2:17 AM, p.l...@ci... wrote:
Dears,
in the subject loader the attached patch manages the case in which padding
bytes
are added to each row data for 32-bit alignment.
The problem of the missing support arose since when the case of
non-power-of-two
texture were supported in Plib, so that a non-multiple-of-four image width
needs
1, 2, or 3 padding bytes on each row. They have to be read so to be skip.
I kindly ask someone (John?) to patch it against the current (2109) revision
in
SVN.
Thanks a lot,
Paolo Leoncini
----------------------------------------------------------------------------
--
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT
data
generated by your applications, servers and devices whether physical,
virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
plib-devel mailing list
pli...@li...
https://lists.sourceforge.net/lists/listinfo/plib-devel
|
|
From: John F. <joh...@cy...> - 2011-03-22 12:01:45
|
Paolo,
Under the heading of "better late than never," I have put your
patch in. It was a "diff" rather than a "svn diff" file so I had to
massage it a bit, so please make sure I have done it right.
- John
On 2/26/2011 2:17 AM, p.l...@ci... wrote:
> Dears,
>
> in the subject loader the attached patch manages the case in which padding bytes
> are added to each row data for 32-bit alignment.
>
> The problem of the missing support arose since when the case of non-power-of-two
> texture were supported in Plib, so that a non-multiple-of-four image width needs
> 1, 2, or 3 padding bytes on each row. They have to be read so to be skip.
>
> I kindly ask someone (John?) to patch it against the current (2109) revision in
> SVN.
>
> Thanks a lot,
>
> Paolo Leoncini
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Free Software Download: Index, Search& Analyze Logs and other IT data in
> Real-Time with Splunk. Collect, index and harness all the fast moving IT data
> generated by your applications, servers and devices whether physical, virtual
> or in the cloud. Deliver compliance at lower cost and gain new business
> insights. http://p.sf.net/sfu/splunk-dev2dev
>
>
> _______________________________________________
> plib-devel mailing list
> pli...@li...
> https://lists.sourceforge.net/lists/listinfo/plib-devel
>
|
|
From: <p.l...@ci...> - 2011-02-26 08:18:04
|
Dears, in the subject loader the attached patch manages the case in which padding bytes are added to each row data for 32-bit alignment. The problem of the missing support arose since when the case of non-power-of-two texture were supported in Plib, so that a non-multiple-of-four image width needs 1, 2, or 3 padding bytes on each row. They have to be read so to be skip. I kindly ask someone (John?) to patch it against the current (2109) revision in SVN. Thanks a lot, Paolo Leoncini |
|
From: John F. <joh...@cy...> - 2011-01-22 22:48:57
|
OK, I've put the patch in. Let me know how it works.
- John
On 1/15/2011 4:40 PM, Olaf Flebbe wrote:
> (Sorry if you see it twice: I got a reject by the mailsystem first)
>
> Hi,
>
> there is an bug in the plib-svn head. plib may not recognize joystick in
> Vista/Win7 correctly.
>
> You can find a patch and more explanations in the Bugtracker at
> sorceforge on # plib-Bugs-3159032.
>
> Please do not hesitate to ask for more informations. Please apply it,
> since it is currently needed for the next release of FlightGear.
>
> Olaf
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> plib-devel mailing list
> pli...@li...
> https://lists.sourceforge.net/lists/listinfo/plib-devel
>
>
>
|
|
From: Olaf F. <fg...@of...> - 2011-01-15 22:40:23
|
(Sorry if you see it twice: I got a reject by the mailsystem first) Hi, there is an bug in the plib-svn head. plib may not recognize joystick in Vista/Win7 correctly. You can find a patch and more explanations in the Bugtracker at sorceforge on # plib-Bugs-3159032. Please do not hesitate to ask for more informations. Please apply it, since it is currently needed for the next release of FlightGear. Olaf |
|
From: John F. F. <joh...@cy...> - 2010-05-31 12:35:53
|
Gentlemen,
I have just put the below-mentioned
patch into PLIB. It uses the functions
"_isnan" and "_isfinite" which are just fine on
my Windows/MSVC platform. Please check it out on
other platforms and let me know of any problems.
- John
At 09:40 AM 4/21/2010, you wrote:
>John,
>
>Please find attached the patch.
>
>This patch also include a fix to the function sgQuatToAxisAngle which
>manages cases of Quat's W outside the range [-1:1] (acos undefined). For
>this I used _isnan and _finite functions in MS Visual C++, whose
>availability I ask all of you to verify on other Plib-supported platforms.
>Otherwise just ignore this second part of the patch.
>
>Thanks a lot,
>
>Paolo Leoncini
>
>
> > -----Messaggio originale-----
> > Da: Fay, John F Dr CTR USAF AFMC 46 SK
> > [mailto:joh...@eg...]
> > Inviato: sabato 17 aprile 2010 18.33
> > A: PLIB Users
> > Oggetto: Re: [Plib-users] R: culling problems w/ off-axis projection
> >
> > Paolo,
> >
> > Congratulations and very good on having solved the
> > problem. Is there a code change that you want me to put into
> > Subversion?
> >
> > Dr. John F. Fay
> > Technical Fellow
> > Jacobs Technology TEAS Group
> > 850-883-1294
> >
> >
> > -----Original Message-----
> > From: Paolo Leoncini [mailto:p.l...@ci...]
> > Sent: Monday, April 12, 2010 3:21 AM
> > To: 'PLIB Users'
> > Subject: [Plib-users] R: culling problems w/ off-axis projection
> >
> > Dear friends,
> >
> > I think to have solved the problem.
> >
> > > -----Messaggio originale-----
> > > Da: p.l...@ci... [mailto:p.l...@ci...]
> > > Inviato: martedì 6 aprile 2010 11.19
> > > A: pli...@li...
> > > Oggetto: [Plib-users] culling problems w/ off-axis projection
> > >
> > > Dear all,
> > >
> > > I'm doing off-axis projection (the most general form of
> > > projection) by translating the four corners of the screen into a
> > > projection matrix, for which I added a new method to the sgFrustum
> > > class and to the Context too. The only difference with
> > giving the six
> > > frustum extrema values is that no calculation occurs.
> > Culling seems to
> > > rely only on the projection matrix values, so, apparently, no
> > > difference w/ the on-axis standard case.
> > >
> > > As far as the projection is not far from the on-axis case
> > the culling
> > > gives no problem. Instead when screen position definition
> > results in a
> > > large rotation in the projection matrix objects suddenly
> > disappear and
> > > reappear by apparently no rule.
> > >
> > > Are culling calculations based on a particular form of the
> > projection
> > > matrix?
> > > should culling planes be extracted in a different way to
> > support the
> > > more general case?
> >
> > In sgFrustum::contains( const sgSphere *s ) (sg.cxx), the for
> > the non-ortho case which is presently done this way:
> >
> > sp1 = plane[ SG_LEFT_PLANE ][0] * center[0] + plane[
> > SG_LEFT_PLANE ][2] * center[2] ;
> > sp2 = plane[ SG_RIGHT_PLANE ][0] * center[0] + plane[
> > SG_RIGHT_PLANE ][2] * center[2] ;
> > sp3 = plane[ SG_BOT_PLANE ][1] * center[1] + plane[ SG_BOT_PLANE
> > ][2] * center[2] ;
> > sp4 = plane[ SG_TOP_PLANE ][1] * center[1] + plane[ SG_TOP_PLANE
> > ][2] * center[2] ;
> >
> > should be substituted by the following general form:
> >
> > sp1 = sgScalarProductVec3 ( plane[ SG_LEFT_PLANE ],
> > center ) + plane[ SG_LEFT_PLANE ][3] ;
> > sp2 = sgScalarProductVec3 ( plane[ SG_RIGHT_PLANE ],
> > center ) + plane[ SG_RIGHT_PLANE ][3] ;
> > sp3 = sgScalarProductVec3 ( plane[ SG_BOT_PLANE ],
> > center ) + plane[
> > SG_BOT_PLANE ][3] ;
> > sp4 = sgScalarProductVec3 ( plane[ SG_TOP_PLANE ],
> > center ) + plane[
> > SG_TOP_PLANE ][3] ;
> >
> > The hint were just below there (see comment "Note: in the
> > general case, we would have to do:").
> > I propose to patch it since this general form also manages
> > the default on-axis case, but Steve should definitely give
> > the go-ahead.
> > Should someone be concerned about performances I could supply
> > a bit larger patch for introducing the ability to supply the
> > Context a general perspective matrix, so to have the general
> > case only calculated in this eventuality.
> >
> > > Thanks a lot,
> > >
> > > Paolo Leoncini
> >
> > Thanks in advance to a good will updater (John, it's you as usual?).
> >
> > Paolo Leoncini
> >
> >
> > > --------------------------------------------------------------
> > > ----------------
> > > Download Intel® Parallel Studio Eval Try the new
> > software tools
> > > for yourself. Speed compiling, find bugs proactively, and fine-tune
> > > applications for parallel performance.
> > > See why Intel Parallel Studio got high marks during beta.
> > > http://p.sf.net/sfu/intel-sw-dev
> > > _______________________________________________
> > > plib-users mailing list
> > > pli...@li...
> > > https://lists.sourceforge.net/lists/listinfo/plib-users
> > >
> >
> >
> > --------------------------------------------------------------
> > ----------------
> > Download Intel® Parallel Studio Eval Try the new
> > software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > plib-users mailing list
> > pli...@li...
> > https://lists.sourceforge.net/lists/listinfo/plib-users
> >
> > --------------------------------------------------------------
> > ----------------
> > Download Intel® Parallel Studio Eval Try the new
> > software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > _______________________________________________
> > plib-users mailing list
> > pli...@li...
> > https://lists.sourceforge.net/lists/listinfo/plib-users
> >
>
>
>------------------------------------------------------------------------------
>
>_______________________________________________
>plib-users mailing list
>pli...@li...
>https://lists.sourceforge.net/lists/listinfo/plib-users
|
|
From: Melchior F. <mf...@us...> - 2010-02-27 15:56:54
|
* Melchior FRANZ -- Saturday 27 February 2010: > The file selector should now also be converted to using puaScrollBar Pfff ... forget that! Just triggering the buttons like in puaLlist is much nicer. :-} m. |
|
From: Melchior F. <mf...@us...> - 2010-02-27 15:34:55
|
* John F. Fay -- Saturday 27 February 2010: > OK, that's gone into SVN. Please make sure it's done correctly. Perfect, thanks! I didn't mention it before, but it was hard to miss, anyway: puaScrollBar does now have mouse scroll support, too. And puaLargeInput does just tell its own puaScrollBar instance "please deal with that". Hence the ++sx/++sy. The file selector should now also be converted to using puaScrollBar with the same scroll events forwarding, rather than using separate slider and arrow buttons. I'll put that on my list. :-) m. |
|
From: John F. F. <joh...@cy...> - 2010-02-27 04:11:46
|
Haven't a clue.
- John
At 11:18 AM 2/17/2010, you wrote:
>Since we're all waking up from hypersleep:
>
>Has anyone managed to port PLIB to the iPhone?
>
>
>Best,
>-joshua
|
|
From: John F. F. <joh...@cy...> - 2010-02-27 04:07:36
|
Oh yes, and I declare this project alive.
- John
At 04:24 PM 2/15/2010, you wrote:
>* jo...@sp... -- Monday 15 February 2010:
> > Wow, nice to see that this project is still alive!
>
>No life sign yet, though. Just an external organism poking. :-)
>
>m.
>
>------------------------------------------------------------------------------
>SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>http://p.sf.net/sfu/solaris-dev2dev
>_______________________________________________
>plib-devel mailing list
>pli...@li...
>https://lists.sourceforge.net/lists/listinfo/plib-devel
|
|
From: John F. F. <joh...@cy...> - 2010-02-27 04:06:44
|
OK, I think I was able to take the previous one out and put this
in. Please check to make sure I've done it right.
- John
At 04:59 AM 2/15/2010, you wrote:
>* Melchior FRANZ -- Monday 15 February 2010:
> > the attached patch implements mouse up/down scroll events for puaList
> > and puaLargeInput (which need it the most).
>
>... would also be nice for the file selector, I guess.
>
>
>Unfortunately, the patch had a minor problem: the active widget was also
>scrolled when the mouse wasn't hovering over it, which is bad. Find an
>improved version attached.
>
>m.
>
>
>------------------------------------------------------------------------------
>SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>http://p.sf.net/sfu/solaris-dev2dev
>_______________________________________________
>plib-devel mailing list
>pli...@li...
>https://lists.sourceforge.net/lists/listinfo/plib-devel
|
|
From: John F. F. <joh...@cy...> - 2010-02-27 03:49:32
|
OK, that's gone into SVN. Please make sure it's done correctly.
- John
At 07:03 PM 2/14/2010, you wrote:
>Hi,
>
>the attached patch implements mouse up/down scroll events for puaList
>and puaLargeInput (which need it the most). Other widgets may follow
>later (combobox, slider).
>
>puaList simply calls the arrow button's callbacks for scroll events.
>In the case of puaLargeInput this is a bit more complicated, as this
>widget doesn't use regular arrow buttons.
>
>m.
>
>
>
>Resending, because I chose the wrong sender address first. :-)
>
>PS: The scroll step size isn't configurable -- it's the same as a
> "line step". Also, holding the shift key down doesn't increase
> the step size ATM.
>
>
>------------------------------------------------------------------------------
>SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>http://p.sf.net/sfu/solaris-dev2dev
>_______________________________________________
>plib-devel mailing list
>pli...@li...
>https://lists.sourceforge.net/lists/listinfo/plib-devel
|
34 messages has been excluded from this view by a project administrator.
