-
Posts
57 -
Joined
-
Last visited
-
Days Won
7
Content Type
Events
Profiles
Forums
Downloads
Posts posted by Konstantin Maslyuk
-
-
-
1. Your building_from_source.rst does not mention that on Windows you have to install windows-build-tools and grunt. I did it globally.
2. I didn't managed to start debug with following command, log attached
grunt debug --family=CC2018
3. you still have no issue reporting platform((
-
Also ftrackWidget is not suitable to handle action widgets as it does not handle content.selection in onWidgetLoad(), is there chance this to be fixed?
-
I got it myself, it look like some dependencies missed in production configuration in ftrack-spark-components.
-
Hello I attempted to use `<DroppableArea session={session} />` in ftrack-spark-base/example/Component and got
```
MESSAGE: Uncaught TypeError: Cannot read property 'isRequired' of undefined LINE: 246 IN: webpack-internal:///./node_modules/ftrack-spark-components/lib/droppable_area/component.js LEVEL: ERROR
```
Am I missed any initialization step? Missed parameter is React's intl.
Also I expected git hub issue reporting workflow but didn't found something similar on bitbucket, is it correct place to report issues?
-
By the way I found that importing ftrack_connect_pipeline module require implicit dependency to initialized QApplication that is not good when I make non gui pipeline blocks.
-
Hello, just noticed activity at ftrack-connect-pipeline/new-framework and would like to know the problems that framework aim to solve. And how solid it is, could I base my solutions on top of that frame work, report problems?
-
I do not see a mention of task's tracked time breakdown here. When i see a negative "+/- hours" on particular task i want to see who is responsible for that and when that happen. Assignee would be changed and task would be done in time but polishing took too long. Popup window on task's "Worked hours" value would be nice.
Building from sources on Windows
in Adobe Creative Cloud
Posted
Actually i managed to got working extension with npm in development mode (with two modifications).
But, yarn is a good point i will keep trying to build with it. Actual log attached.
And my message was about to update documentation so modification of Adobe extension for others would not be so painful.