Anyone knows how to use "context"? I don't even know what is used for...
Thanks
It's just the first release, don't panic =)efyx wrote:I have already checked Pie Menu and I have two questions:
1) shouldn't icons changed depending on which module I am?
2) isn't that a good idea to "close" Pie Menu also by clicking anywhere?
I will keep this in mind and if i will find suitable solution i will try to make close PieMenu and show QuickMenu operation more distinct and intuitive to use in the future.flokart wrote:Unfortunatly the little arow to get acces to the edit features are not showing.
Not yet. Currently you can change/set active PieMenu only by selecting it from QuickMenu.flokart wrote:Is there a option to add new additional buttons(shortcut keys) for new created pies ?
I researched this a bit and if i remember correctly there is similar issue in drawing workbench? Currently QGLWidget is used to display "3D View" and after FreeCAD will gain Qt5 support things could improve. That is if transition from QGLWidget to QOpenGLWidget will be made. Once and if this happens i guess there is a good chance issues observed on macOS could be resolved. PieMenu buttons could probably use round corners as transparency wouldn't be a problem anymore... Anyway that i guess is distant future.pablogil wrote:I'm trying it out on OSX and it doesn't overlay the 3D View:
...
I guess is something related to how FreeCAD renders on OSX cause it happens the same when expanding a toolbar "show more" button:
Code: Select all
from PySide import QtGui ,QtCore
app = QtGui.qApp
app.setAttribute(QtCore.Qt.AA_DontCreateNativeWidgetSiblings, True)
You can add context sensitivity to individual PieMenu by enabling the option in context tab. After you set condition for example:pablogil wrote:Anyone knows how to use "context"? I don't even know what is used for...
In the future PieMenu selection management will improve. Some discussions were made in the past but nothing has been decided yet. Currently Tab key will show/hide PieMenu and pressing the center button will hide PieMenu as explained by @pablogil. As for adding the possibility to hide PieMenu by clicking anywhere i guess this could be evaluated in the future.efyx wrote:I have already checked Pie Menu and I have two questions:
1) shouldn't icons changed depending on which module I am?
2) isn't that a good idea to "close" Pie Menu also by clicking anywhere?
I evaluated this and for now i won't implement it. I feel both keyboard key combination and mouse click use case are supported. Introducing another way to hide PieMenu could interfere with Context sensitivity or could make implementing features in the future harder.As for adding the possibility to hide PieMenu by clicking anywhere i guess this could be evaluated in the future.
Based on my research it won’t be as simple as that. Qt5 by itself wont resolve the mentioned issues. Only after migration to QOpenGLWidget or some other approach will be used we can expect the mentioned issues to be resolved.pablogil wrote:Yes, I did also investigate it and I found the problem is that FreeCAD uses QT4 and while it doesn't move to QT5 these issues will persist.
Over the weekend i will likely have more time and i will add the needed changes to alter behaviour on macOS. That should improve the situation.Anyway, I found a way to use the pie:in macOS it doesn't show at all ever the 3D view but it works, that is, I'm able to launch it pressing TAB and move the mouse along the direction I want and when it hovers the button the command is run
- pie radius = 70
- icon size = 32
- Trigger = hover
Code: Select all
from PySide import QtGui
btn0 = QtGui.QToolButton()
btn0.setGeometry(0, 0, 48, 48)
btn1 = QtGui.QToolButton()
btn1.setGeometry(52, 0, 48, 48)
mw = FreeCADGui.getMainWindow()
mdi = mw.findChild(QtGui.QMdiArea)
sw = mdi.currentSubWindow().widget()
btn0.setParent(mdi)
btn1.setParent(sw)
btn0.show()
btn1.show()
No buttons...triplus wrote:@pablogil
Do you see one or two or no buttons on the screen?
From our researches, I think the problem is almost unreachable from our side. I mean, it should be solved at FreeCAD rendering system level and probably we cannot access that...triplus wrote:I see. Therefore i don't yet know how i will approach this. The main problem is i don't have access to macOS to test things out.
Will try to think of something in the following days.