graphic:python:blender

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revisionBoth sides next revision
graphic:python:blender [2024/01/24 10:02] – [Blender variable naming standards] yinggraphic:python:blender [2024/01/24 10:02] – [Blender variable naming standards] ying
Line 395: Line 395:
   * https://s-nako.work/2020/12/blender-addon-naming-rules/   * https://s-nako.work/2020/12/blender-addon-naming-rules/
  
-  * Class name convention is: UPPER_CASE_{SEPARATOR}_mixed_case+  * **Class name convention**: UPPER_CASE_{SEPARATOR}_mixed_case
     * UPPER_CASE: normally the ADDON_NAME, or a Unique ID_WORD that make it not crashing into other existing class names     * UPPER_CASE: normally the ADDON_NAME, or a Unique ID_WORD that make it not crashing into other existing class names
     * {SEPARATOR}     * {SEPARATOR}
Line 407: Line 407:
       * _Check_Selection       * _Check_Selection
       * _check_selection       * _check_selection
-  * like  [A-Z][A-Z0-9_]*_MT_[A-Za-z0-9_]+ +    * like  [A-Z][A-Z0-9_]*_MT_[A-Za-z0-9_]+ 
-  * if not follow above: you get warning "doesn't contain '_PT_' with prefix & suffix" +    * if not follow above: you get warning "doesn't contain '_PT_' with prefix & suffix"
   * **operator ID name convention** (feel like a username for your operator inside blender )   * **operator ID name convention** (feel like a username for your operator inside blender )
     * category_name.operator_task_like_name     * category_name.operator_task_like_name
  • graphic/python/blender.txt
  • Last modified: 2024/06/12 06:47
  • by ying