Hi guys, I've been disturbed by this in the processing IDE, and now that I've upgraded to 0.18 for Arduino, I've got the same behavior, which again is disturbing for me =)
I'm wondering if there's any configuration parameter I can set to prevent the IDE from opening the first sketch in a new window (or any sketch in a new window for that matter...)?
The problem I'm having is that basically every time I'm using the IDE, I'm editing an existing sketch. So, my workflow is always:
Start IDE
Open Sketch
Minimize the new window w/ the sketch that drew over the original IDE window
Close the original IDE window that's doing nothing for me
Maximize the new window
Those steps 3 and 4 seem minimal, but it is frustrating that I always have to do it and spend the extra clicks every time.
Is there any config option to 'Open Sketches in Current Window'? If not, what would it take to add it? It would certainly be a time-saver for those of us that rarely edit two sketches at the exact same time =)
Hi guys, I've been disturbed by this in the processing IDE, and now that I've upgraded to 0.18 for Arduino, I've got the same behavior, which again is disturbing for me =)
I think about 90% of the arduino users are disturbed by this
Opening an existing sketch from the toolbar (the button with the arrow pointing upwards) loads the new sketch into the already open window.
Opening an existing sketch from the toolbar (the button with the arrow pointing upwards) loads the new sketch into the already open window.
This is just plain stupid. The generally accepted practice is for the icon and the menu item to invoke the same code. Having different (radically different) behavior for two seemingly identical functions is insane.
I always open my sketch through the sketchbook thing in the drop-down...
Also opens in a new window, don't like it.
@ PaulS: generally accepted practice... it is nearly mandatory, everybody expects it to behave like that, so I wholeheartedly agree with your statement.
This is just plain stupid. The generally accepted practice is for the icon and the menu item to invoke the same code. Having different (radically different) behavior for two seemingly identical functions is insane.
The insane part for me is that every time I open a Sketch from the File menu an new Window pops up to clutter my desktop. So I'm quite happy the processing devlopers missed to update the code for the toolbar.
So I'm quite happy the processing devlopers missed to update the code for the toolbar.
My point was that the menu selection and the icon selection should invoke the same callback, not have two different callbacks. Whether that callback does the right thing, or not, is less of an issue, in my mind, than the fact that there are (apparently) two different callbacks.
That there are two (apparently) different callbacks indicates some sloppiness, or less than professional coding being accepted. That's the thing that concerns me.
Well, you can all set aside your fears. Got around to testing the "work-around," and no, it does not behave differently. Opening a file from the Up-arrow icon->Open results in the exact same behavior as File->Open.
That is, it opens in a new window.
Apparently Eberhard is opening an example from a library, or something that is displayed from that menu, and not using "Open" to get the file explorer when he experiences that behavior. (Verified, btw, it only opens in the same window if the sketch is somehow listed in that default window.)
I like to keep my sketches organized in my svn folders, and not the sketchbook, so apparently there is no work-around for me, alas.
Edit: well, maybe don't rest so easy -- if you open from the sketchbook or the examples in the File menu, it opens in a new window when the Up-Arrow icon does not for these. So, there's the divergent code path, not in the 'Open' option.
This new window behavior has changed in recent versions of Processing, and I'm in the process of porting those modifications back into Arduino (for 0019). So this problem will be solved.
This new window behavior has changed in recent versions of Processing, and I'm in the process of porting those modifications back into Arduino (for 0019). So this problem will be solved.
This new window behavior has changed in recent versions of Processing, and I'm in the process of porting those modifications back into Arduino (for 0019). So this problem will be solved.
I checked out the processing code from svn recently (0184) and the "Open"-code shows the same behaviour as the current arduino-IDE.
