Dear sugokuGENKI, you were one of most asked for keynote video person. And now, thanks to misterious vvvvleaks, when we have it finally, you speak about bugs in beta25? Guess, Robot-Santa will not like it
anyway until our next release - a try of a general view onto bugs…
there are those that (should) make you nervous and other that don’t (shouldn’t). the one with open code editors is one that shouldn’t make you nervous, since we it is just implemented that way. in your root is a static editor node showing the text file. the inabilty of pasting also shouldn’t make you nervous, but for sure it is a BUG. right clicking on an input pin: since we are all trained to make pixelprecise clicks, i want to believe - can’t reproduce however. technique bug: sorry for tat
wouldn’t a conventional (forum?) bug tracker, probably interfaced in some way with the already existing (?) internal bugtracker be much more usable/convenient than inventing new solutions to already well-defined and well-solved problems (i.e. bug tracking)?
/me is already itching to find the time to try the new beta! :-)
@kalle: node IDs in finder: e.g. if you know for some reason a node you are looking for has ID 8 and is somewhere in your open patches do as follows:
type: “g # 8”
hover the resulting nodes and check the tooltips to see that they all have ID 8.
doubleclick the one you were looking for. its patch will open and the node will be selected.
indeed kommunikator is thougt to be extended kinda like this. only the target would be exactly the forum with the bug tag set. that is our bugtracker. we’ll not maintain multiple systems (we tried that multiple times and it failed. multiple times).
so for now the kommunikator could be extended to load the website in a second tab and start a new forum thread. not sure though if that is easier than switching to a webbrowser. an api concerning different elements of the website is in our heads also but will still take a while…
Unhandled exception has occured in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.
Object reference not set to an instance of an object.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at VVVV.HDE.Viewer.WinFormsViewer.MapperHierarchyNode.SetColor(Boolean hover)
at VVVV.HDE.Viewer.WinFormsViewer.MapperHierarchyNode.SetHover(Boolean hover)
at VVVV.HDE.Viewer.WinFormsViewer.MapperHierarchyNode.MouseLeave(PointF mousePos, TimeSpan timeSinceEnter)
at VVVV.HDE.GraphicalEditing.GraphElement.GraphElement_MouseLeave(Object sender, PInputEventArgs e)
at UMD.HCIL.Piccolo.PNode.HandleEvent(PInputEventArgs e, PInputEventHandler handler)
at UMD.HCIL.Piccolo.PNode.OnMouseLeave(PInputEventArgs e)
at UMD.HCIL.Piccolo.Event.PInputEventArgs.DispatchTo(Object sender)
at UMD.HCIL.Piccolo.Util.PPickPath.ProcessEvent(PInputEventArgs e)
at UMD.HCIL.Piccolo.PInputManager.DispatchToPath(PInputEventArgs e, PInputType type, PPickPath path)
at UMD.HCIL.Piccolo.PInputManager.CheckForMouseEnteredAndExited(PInputEventArgs e)
at UMD.HCIL.Piccolo.PInputManager.Dispatch(PInputEventArgs e)
at UMD.HCIL.Piccolo.PInputManager.ProcessEventFromCamera(EventArgs e, PInputType type, PCamera camera, PCanvas canvas)
at UMD.HCIL.Piccolo.PCanvas.OnMouseMove(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseMove(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)