Thread: [Iup-users] docs improvement
Brought to you by:
scuri
From: Karagy <ka...@ma...> - 2013-10-11 19:34:24
|
Hi, all. Suggestions for documentation improvement. 1. IupColorBrowser priority: several Description is terminated at the line about the RGB attribute. Affected chm for 3.8. chm for 3.6 and 3.7 - is ok. priority: low CHANGE_CB and DRAG_CB In this callbacks you must use r,g,b params, you must not use self.rgb. For sample, under WinXP self.rgb is correct. But under Win7 (32 or 64 bit) - it always return "255 255 255" 2. IupPPlot priority: low Many typos for "Auxiliary Functions" with extra prefix "Iup" in function names for call from Lua. Incorrect paramlist for some functions. For sample: iup.IupPPlotAddPoints(ih: ihandle, index, x, y: table of number) [in Lua] Correct variant: iup.PPlotAddPoints(ih: ihandle, index: dataset number, x, y: table of number, count: dataset size) [in Lua] priority: very low Restrictions for PREDRAW_CB: It is bad idea to change axs_ymax inside this callback while axs_yautomax == "YES". It caused incorrect result for iup.PPlotTransform function (by incorrect margins counting). With Best Regards, Karagy. |
From: Antonio S. <ant...@gm...> - 2013-10-13 01:07:50
|
> 1. IupColorBrowser > priority: several > Description is terminated at the line about the RGB attribute. > Affected chm for 3.8. chm for 3.6 and 3.7 - is ok. This is already fixed. > priority: low > CHANGE_CB and DRAG_CB > In this callbacks you must use r,g,b params, you must not use self.rgb. > For sample, under WinXP self.rgb is correct. > But under Win7 (32 or 64 bit) - it always return "255 255 255" That's weird. I checked the code and there is no reason for this to happen. I will try a test code. > 2. IupPPlot > priority: low > Many typos for "Auxiliary Functions" with extra prefix "Iup" in function > names for call from Lua. > Incorrect paramlist for some functions. > For sample: > iup.IupPPlotAddPoints(ih: ihandle, index, x, y: table of number) [in Lua] > Correct variant: > iup.PPlotAddPoints(ih: ihandle, index: dataset number, x, y: > table of number, count: dataset size) [in Lua] Fixed them all. Thanks for pointing that. > priority: very low > Restrictions for PREDRAW_CB: > It is bad idea to change axs_ymax inside this callback while axs_yautomax > == "YES". > It caused incorrect result for iup.PPlotTransform function (by incorrect > margins counting). That's expected. The "restrictions" mentioned in the documentation are for the drawing area, since the posdraw_cb have clipping restrictions. Best, Scuri |
From: Karagy <ka...@ma...> - 2013-10-13 15:04:01
|
>> priority: low >> CHANGE_CB and DRAG_CB >> In this callbacks you must use r,g,b params, you must not use self.rgb. >> For sample, under WinXP self.rgb is correct. >> But under Win7 (32 or 64 bit) - it always return "255 255 255" > > That's weird. I checked the code and there is no reason for this to > happen. I will try a test code. For win7, I continue to receive information about the incorrect values for self.rgb and for params r,g,b too. Unfortunately, the effect can not be reproduced stably. I'll send the report as soon as the information will be able to organize. WBR, Karagy. |
From: Antonio S. <sc...@te...> - 2013-10-13 16:43:37
|
If you could reproduce this is a small sample then it is quite forward for me to fix any problems. Thanks, Scuri On Sun, Oct 13, 2013 at 12:03 PM, Karagy <ka...@ma...> wrote: > >> priority: low > >> CHANGE_CB and DRAG_CB > >> In this callbacks you must use r,g,b params, you must not use > self.rgb. > >> For sample, under WinXP self.rgb is correct. > >> But under Win7 (32 or 64 bit) - it always return "255 255 255" > > > > That's weird. I checked the code and there is no reason for this to > > happen. I will try a test code. > > For win7, I continue to receive information about the incorrect values > for self.rgb and for params r,g,b too. > Unfortunately, the effect can not be reproduced stably. > I'll send the report as soon as the information will be able to organize. > > > WBR, Karagy. > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk > _______________________________________________ > Iup-users mailing list > Iup...@li... > https://lists.sourceforge.net/lists/listinfo/iup-users > |
From: Karagy <ka...@ma...> - 2013-10-16 15:20:44
|
Hi. I confirm, for both win7 - x32 and x64 - the IupColorBrowser is working properly. Best, Karagy |
From: Antonio S. <ant...@gm...> - 2013-10-16 17:01:17
|
Ok. Thanks, Scuri > -----Original Message----- > From: Karagy [mailto:ka...@ma...] > Sent: quarta-feira, 16 de outubro de 2013 12:20 > To: IUP discussion list. > Subject: Re: [Iup-users] docs improvement > > Hi. > > I confirm, for both win7 - x32 and x64 - the IupColorBrowser is working > properly. > > Best, > Karagy > > ---------------------------------------------------------------------------- -- > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clk > trk > _______________________________________________ > Iup-users mailing list > Iup...@li... > https://lists.sourceforge.net/lists/listinfo/iup-users |