Yep, I did see the gizmo pref. That’s a welcome addition. I’m also intrigued by your comment over in the modo to Blender thread about enabling the gizmo on the GSR keys as well. I’d love to see that added.
I totally understand regarding the crossover; not all functions can be replicated. I was wondering if it’s even helpful to have Element in the list. The addition of the the cursor axis/center seems to negate the need for the element mode doesn’t it?
It could be removed but I wanted to try it with some other ideas before removing. I actually want to make a new add-on based on what I put in Modo-Me and call it something else since I want it to be Modo-Me++ but with new functionality. However I still want to make one more Modo-Me release with bugs or features. The element/selection issue needs some close attention.
My initial thinking was that the selection is calculated based on the whole selection, while element is individual elements, as in islands of selection has their own axis. And exchange behaviours of “local” with “element” And keep the “local” only an object level transformation, which will be grayed out.
Ah. Makes more sense that way. Would the ++ version include some workplane type emulation? 
Yeah that is one of those for sure.
Excellent! I’ll be looking for that one for sure!
Awesome to hear that. Please add your wish lists and bed bugs here as you go, so I can try to implement them as much as I can into this.
I’ve been using this since yesterday. It’s great! Probably only thing missing for me would be a selection mode where it locks the axis, so it could be used as a work plane. Something like this 
Hi
I am glad to see another happy user here. Couple of the modes actually lock the “transform orientations” which is basically a custom axis system. I will take a look at the code later to see which ones I implemented with.
If the selection one is missing it I will add that for the next release.
Now that you mention it … while the addon works fine for me in 2.80, I haven’t had any luck getting it installed for 2.79b. When I attempt to install from the zip the latest version (1.25), nothing is loaded. When I tried 1.2 the addon loaded, but I got a traceback error when I enabled it.
Hi
I am sorry that you are having that issue. I naturally tested it with 2.79b before the release so it should normally work. Can you please message me the error log you see in the terminal? I will take a look at it when I have time later today.
thanks
Here’s the error I get when loading v 1.25 into 2.79b:
SyntaxError: invalid syntax
fake_module: addon missing 'bl_info' gives bad performance!: 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons\\modo-me\\__init__.py'
Modules Installed () from 'C:\\Users\\uscokebr\\Creative Cloud Files\\BlenderPlugins\\2.7\\Modo-Me_2.79_v1.25_02092019.zip' into 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons'
Hi
Thanks for the report. I just investigated the issue. I can’t make sense of the error you are getting, it could be coming from the add-on that is loaded just before modo-me. The addon is not missing bl-info so it actually registers.
Please see the lines above that message on your terminal to see if you have troubled add-ons that might be causing the issue.
I also uninstalled it, refreshed scripts (F8) from my Blender 2.79b (nightly) and installed it using the zip method and it installs fine here.
Maybe try downloading it again please? Also it would be better if you paste lines above and below those ones so I can see if it is the addon.
Here is a screenshot from 2.79b (after reinstlaling with zip)
Here’s a copy of the entire console after loading up Blender and then attempting to install ModoMe (newly downloaded):
Read prefs: C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.79\config\userpref.blend
found bundled python: C:\Program Files\Blender Foundation\Blender\2.79\python
Registered Blender Light Studio with 10 modules
_______REgister previews
.. .ao
.. .ao_legacy
.. .bevel_mask
.. .cavity
.. .curvature
.. .diffuse
.. .displacment
.. .dust
.. .id_element
.. .id_material
.. .normal_object
.. .normal_object_bevel
.. .normal_tangent
.. .normal_tangent_bevel
.. .paint_base
.. .position
.. .selection
.. .wireframe
Registered Hard Ops 9 with 126 modules
RetopoFlow Options path: C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\RetopoFlow\RetopoFlow_options.json
RetopoFlow Options path: C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\RetopoFlow\retopoflow_updater\backup\RetopoFlow_options.json
Caught exception while attempting to search for classes
cls: RFTool: RFTool_Tweak, RFTool_Stretch, RFTool_Patches, RFTool_PolyStrips, RFTool_Loops, RFTool_Relax, RFTool_Stretch, RFTool_Strokes, RFTool_PolyPen, RFTool_Contours
pyfile: tools.watch_profile
No module named 'Levenshtein'
RetopoFlow updater verbose is enabled
RetopoFlow Updater: Read in json settings from file
search for unknown operator 'PENFINITY_OT_smart_bevel', 'PENFINITY_OT_smart_bevel'
search for unknown operator 'PENFINITY_OT_smart_bevel', 'PENFINITY_OT_smart_bevel'
search for unknown operator 'PENFINITY_OT_smart_bevel', 'PENFINITY_OT_smart_bevel'
Syntax error 'ast.parse' can't read 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons\\modo-me\\__init__.py'
Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\modules\addon_utils.py", line 117, in fake_module
ast_data = ast.parse(data, filename=mod_path)
File "C:\Program Files\Blender Foundation\Blender\2.79\python\lib\ast.py", line 35, in parse
return compile(source, filename, mode, PyCF_ONLY_AST)
File "C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\modo-me\__init__.py", line 6
"version": ( 1, 2_5_02092019 ),
^
SyntaxError: invalid syntax
fake_module: addon missing 'bl_info' gives bad performance!: 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons\\modo-me\\__init__.py'
Modules Installed () from 'C:\\Users\\uscokebr\\Downloads\\Modo-Me_2.79_v1.25_02092019.zip' into 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons'
There are a couple of missing operators there for an old addon (no idea why), but the first syntax error shows up after attempting to load ModoMe. I’m not certain, but I think I loaded it successfully on my home system. Not sure what’s going on here.
I can confirm that the file “Modo-Me_2.79_v1.25_02092019.zip” on Gumroad that @brandroid is extracting is bad. The version specified in the bl_info yields a syntax error in Python. In fact, the “Modo-Me_2.80_v1.25_02092019.zip” file has the same issue.
Ok sorry about that guys. Since I cant replicate this issue myself I can only speculate about it.
Is it possible if anyone of you can rename the addon folder for Blender 2.79b, start Blender and install the zip file again? I am wondering if it will stil casue the similar issue for you guys.
In @brandroid’s log it says ast cant read the file, which is curious. That is the Python module that API uses to parse the addons.
I will do one more testing and upload a new version.
Are you saying that you can’t even install the 2.80 version in Blender 2.8? It seems to work for others.
Can you actually properly unzip any of those files to somewhere on your drive?
Tried renaming the Addon directory and loading it again. Getting the same error.
Read prefs: C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.79\config\userpref.blend
found bundled python: C:\Program Files\Blender Foundation\Blender\2.79\python
addon not found: 'vtools_saveIncremental'
addon not found: 'blender-light-studio'
addon not found: 'textools'
addon not found: 'blender_cloud'
addon not found: 'amaranth'
addon not found: 'HOps'
addon not found: 'object_drop_to_ground_v01'
addon not found: 'BoxCutter'
addon not found: 'mesh_mesh_align_plus'
addon not found: 'RetopoFlow'
addon not found: 'add_mesh_capsule'
search for unknown operator 'PENFINITY_OT_smart_bevel', 'PENFINITY_OT_smart_bevel'
search for unknown operator 'PENFINITY_OT_smart_bevel', 'PENFINITY_OT_smart_bevel'
search for unknown operator 'PENFINITY_OT_smart_bevel', 'PENFINITY_OT_smart_bevel'
search for unknown operator 'WM_OT_saveincremental', 'WM_OT_saveincremental'
search for unknown operator 'WM_OT_saveincremental', 'WM_OT_saveincremental'
Syntax error 'ast.parse' can't read 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons\\modo-me\\__init__.py'
Traceback (most recent call last):
File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\modules\addon_utils.py", line 117, in fake_module
ast_data = ast.parse(data, filename=mod_path)
File "C:\Program Files\Blender Foundation\Blender\2.79\python\lib\ast.py", line 35, in parse
return compile(source, filename, mode, PyCF_ONLY_AST)
File "C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.79\scripts\addons\modo-me\__init__.py", line 6
"version": ( 1, 2_5_02092019 ),
^
SyntaxError: invalid syntax
fake_module: addon missing 'bl_info' gives bad performance!: 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons\\modo-me\\__init__.py'
Modules Installed () from 'C:\\Users\\uscokebr\\Creative Cloud Files\\BlenderPlugins\\2.7\\Modo-Me_2.79_v1.25_02092019.zip' into 'C:\\Users\\uscokebr\\AppData\\Roaming\\Blender Foundation\\Blender\\2.79\\scripts\\addons'
Just to reiterate, I had no issues loading up the 2.80 version in 2.80. I’ll test 2.79 with my home system tonight.
Thank you for the additional effort there.
Are you using Blender 2.79b nightly or release? Nightlies are using Python3.7 while the release uses 3.5 (althought that might have changed recently)
Nope, not the nightly, just the release.
Actually I think I know the issue, your last log shows me more information. It is the formatting with the version field.
The fix is easy, if you do not want to wait for my fix release you can just change "version": (1, 2_5_02092019), to "version": (1, 25), in __init__.py for now. It is just at the top of the file.