About Gaussian curvature computation
Dear Openflipper developer, We saw that, in openflipper, the initial Guassian curvature for each vetex is : double gauss_curv( 2.0*M_PI); However, in lots of papers, they set the initial value to M_PI, if it is a boundary vertex. Could you please explain such difference? Thank you for your great work in graphics community! Best Regards, Xianyong Liu Shanghai JiaoTong University Office: +86 021 34204586 E-mail: xyliu80@gmail.com Address: 504 Room, SEIEE buiding 3#, 800 Dongchuan Rd,Min Hang,Shanghai,200240,China
Dear Openflipper developer, Suppose we have built up a plugin, but we want to split it into a classes and other slaved ones. Every inherits from QObject, BaseInterface, LoggingInterface, StatusbarInterface, RPCInterface such that they can call other plugin functions, like log, rpc::callFunction, by themselves. The problem is that we found such design does not work, because they can not work as we imagine; Only the primary one works fine. Therefore, we want to ask for suggestions for the support team! Best Regards, Xianyong Liu Shanghai JiaoTong University Office: +86 021 34204586 E-mail: xyliu80@gmail.com Address: 504 Room, SEIEE buiding 3#, 800 Dongchuan Rd,Min Hang,Shanghai,200240,China
Dear Openflipper developer, Suppose we have built up a plugin, but we want to split it into a classes and other slaved ones. Every inherits from QObject, BaseInterface, LoggingInterface, StatusbarInterface, RPCInterface such that they can call other plugin functions, like log, rpc::callFunction, by themselves. This setup is fine. Usually we also split the functionality into basic
Hi, On 18.10.2012 06:15, xyliu80@gmail.com wrote: plugins. You have to put the plugins into separate folders at OpenFlippers top level directory. Additionally you have to make sure, that they have different names (especially the plugin name returned has to be different). You can only have one class handling the interfaces in your plugin. All other classes can be derived from QObject but have to communicate to the core via the main plugin class (But you can connect the signals of your subclass directly to the signals of your ain class).
The problem is that we found such design does not work, because they can not work as we imagine; Do you get any error message?
Only the primary one works fine. Take a look at the log window. When OpenFlipper starts, it shows which plugins get loaded in the log window. Check for messages regarding plugins that are not loaded. If you use linux, you can start OpenFlipper with the command line option "-c" which will print the full log to your console.
Best, Jan Möbius -- Dipl.Inform. Jan Möbius Department of Computer Science VIII Aachen University of Technology (RWTH) Ahornstrasse 55, 52074 Aachen, Germany Phone ++49 (0)241 80-21817 Fax ++49 (0)241 80-22899 mailto:moebius@cs.rwth-aachen.de http://www.rwth-graphics.de
On 17.10.2012 17:01, xyliu80@gmail.com wrote:
Dear Openflipper developer,
We saw that, in openflipper, the initial Guassian curvature for each vetex is : double gauss_curv( 2.0*M_PI); However, in lots of papers, they set the initial value to M_PI, if it is a boundary vertex.
Could you please explain such difference?
Was a bug. Boundary vertices where not handled at all. -> Fixed in svn. Best, Jan Möbius -- Dipl.Inform. Jan Möbius Department of Computer Science VIII Aachen University of Technology (RWTH) Ahornstrasse 55, 52074 Aachen, Germany Phone ++49 (0)241 80-21817 Fax ++49 (0)241 80-22899 mailto:moebius@cs.rwth-aachen.de http://www.rwth-graphics.de
participants (2)
-
Jan Möbius -
xyliu80＠gmail.com