Wed 04 Mar 2015 08:44:47 PM UTC, comment #34:
Nah, I think the dubious distinction of most comments goes to bug #41699. The comment count is now at 87, and still not resolved.
|
Wed 04 Mar 2015 07:29:24 PM UTC, comment #33:
Does this bug report have more comments than any other?
|
Wed 04 Mar 2015 05:51:55 PM UTC, comment #32:
Patches verified. Closing report (finally).
|
Tue 03 Mar 2015 05:56:10 PM UTC, comment #31:
Pushed:
http://hg.octave.org/mxe-octave/rev/6daa158a7018
http://hg.savannah.gnu.org/hgweb/octave/rev/17d21d68888d
|
Mon 02 Mar 2015 08:05:55 PM UTC, comment #30:
Success!
I used the new welcome wizard patch and re-built octave, then did 'make dist', and finally took the tarball over to MXE and built the nsis-installer.
After installation on the Windows side I added the octave.vbs script which can replace octave.bat to the bin directory of the Octave installation. Finally, I changed the shortcut on the desktop to point to octave.vbs rather than octave.bat.
Upon launching no cmd window appears, nor is there a minimized window in the task bar, until the Octave GUI appears. This is perfect. And I deleted the octave directory under .config/ and re-ran and the Welcome Wizard is correctly displayed.
Please go ahead and commit the pieces when you can.
|
Mon 02 Mar 2015 06:10:11 PM UTC, comment #29:
HACK attached to force display of welcome wizard (when needed) in win32.
(file #33226)
|
Fri 27 Feb 2015 02:45:44 AM UTC, comment #28:
Can anyone else running win7 verify seeing the same thing?
|
Fri 27 Feb 2015 02:26:05 AM UTC, comment #27:
Weirdly, the script has suddenly started flashing the terminal window again, even when running from the original script from comment 14.
|
Fri 27 Feb 2015 12:51:21 AM UTC, comment #26:
I believe this bug was the reason: http://savannah.gnu.org/bugs/?40689
|
Fri 27 Feb 2015 12:19:33 AM UTC, comment #25:
From memory, running octave.exe doesn't work in windows so had to be run as octave-gui.
|
Fri 27 Feb 2015 12:00:30 AM UTC, comment #24:
John,
What is the benefit of having octave-gui --no-gui?
Do we really need so many flavors? Will plain
octave --no-gui with qt available be enough for
CLI users? And just octave for GUI folks?
Michael
|
Thu 26 Feb 2015 11:55:23 PM UTC, comment #23:
John,
With the patch 81dbeb22a28f the current system
runs qt with --no-gui. print 'xxx.pdf' works,
but using the save menu item still does not
(minor issue).
This patch should probably be reviewed, but it
works for me.
Michael
|
Thu 26 Feb 2015 11:14:18 PM UTC, comment #22:
update: My octave.vbs works except for the case of where the config/startup window would be displayed - at that point it started octave, but never shows anything
|
Thu 26 Feb 2015 10:52:32 PM UTC, comment #21:
It might lead to 3 different desktop shortcuts, but I don't see a problem in doing that.
|
Thu 26 Feb 2015 10:23:42 PM UTC, comment #20:
If we patch Octave so that plotting with Qt widgets works when running octave --no-gui, could we also make it possible to run octave-gui --no-gui so that it starts in the terminal mode but can plot with Qt widgets?
It still makes sense to start octave-cli if you want to run a copy of Octave that is not linked with Qt so we should keep that as an option.
|
Thu 26 Feb 2015 08:16:48 PM UTC, comment #19:
This works for me - I will replace octave.bat with octave.vbs
(file #33197)
|
Thu 26 Feb 2015 06:14:22 PM UTC, comment #18:
I agree. It's crazy to have vbs -> cmd.exe -> octave.bat -> start -> octave-gui.exe. If one of the layers could be removed it would be a lot simpler.
|
Thu 26 Feb 2015 06:03:40 PM UTC, comment #17:
Will take a look tonight after my real work.
It might be good to see if we can get rid of octave.bat completely, and set any environment stuff etc in the vbs scripts instead
|
Thu 26 Feb 2015 05:21:17 PM UTC, comment #16:
I'm totally swamped with other release tasks, as well as real work. Could you incorporate the vbs script into MXE? Otherwise, I can probably get to it this weekend, but I want to start trying to get a release candidate out tomorrow.
|
Thu 26 Feb 2015 05:03:31 PM UTC, comment #15:
Script works for me ... now can the script open up a splashscreen whilst it is loading the main program ? :)
|
Thu 26 Feb 2015 04:36:41 PM UTC, comment #14:
So I think the /B is a good thing and I'll at least commit that change.
Final thing to try is a visual basic script which makes itself invisible before launching octave.bat. With this, I don't even get a minimized icon in the taskbar.
See the attached runoctavebat.vbs file.
(file #33195)
|
Thu 26 Feb 2015 01:58:31 PM UTC, comment #13:
Adding /B /MIN in octave.bat appears to show the console minimized (on task bar) and never show it on the main screen.
However, at that point, with I delete the octave config, then the startup/config window is shown minimized.
|
Thu 26 Feb 2015 01:34:01 PM UTC, comment #12:
The shortcuts in the nsis-installer are already minimized.
I started a virus check to put some load on my computer and tried again.
Watching the task bar, without /B I see two console windows applets display so before the main window dislays. On the main screen, it appears only one terminal is shown for a whil, other other flashes briefly.
WIth /B, on the taskbar, there is one terminal displayed - on the main screen, it look like the console starts minimized but then briefly is shown normal just before the main window is shown.
With not minimized, but with the /B, there is only one console displayed, but is shown for a longer time on the screen than when minimized
|
Thu 26 Feb 2015 04:07:58 AM UTC, comment #11:
In comment #5 you found that the Installer Wizard wasn't shown. But this seems to apply only when the shortcut is running the executable directly.
Things seem to be different when the shortcut points to a .bat file, or maybe we fixed how to raise the window for the Wizard. I have tested by removing the ~/.config/octave directory and provoking the Welcome Wizard and it works fine with the /B switch and the shortcut set to run minimized.
Maybe the only remaining issue is that John D. reports in comment #9 that it still doesn't completely eliminate a cmd window display. From what I have read and can understand about Windows, this seems to be the terminal window which is processing the .bat file. People suggest doing as little processing as possible before executing 'start ...' to minimize the time that this window is shown. But I found that just switching the shortcut to run minimized was enough. If John D. can test that then I think that will clear up this final issue.
I do have yet another possibility which is to create a trivial .vbs script which runs octave.bat silently, but this would really be overkill as a vbs script would invoke a .bat script which would invoke an executable.
|
Thu 26 Feb 2015 01:14:52 AM UTC, comment #10:
If /B does work, then great, but I seem to recall discussing it previously and there was some reason to avoid using it but unfortunately I don't remember the details.
What about the -Wl,subsystem,windows option? Or is that just the same as /B?
|
Thu 26 Feb 2015 12:12:26 AM UTC, comment #9:
The extra window always runs quick for me (Win7), making it hard to see - however the amount of time that any console window is shown is halved for me - maybe shown for a 1/4 second.
|
Wed 25 Feb 2015 11:49:04 PM UTC, comment #8:
The Octave shortcuts no longer run the executable files directly. Instead they run octave.bat with the --no-gui or force-gui option. I was able to get rid of the extra terminal window when running the GUI by editing octave.bat to throw the /B option to start.
I'm attaching a patch for the MXE repository. Can someone else test and see if it works for them? I only have a crappy Windows XP VM for testing and it is often different than a Win7 or Win8 machine.
(file #33191)
|
Wed 08 Jan 2014 05:38:20 AM UTC, comment #7:
Unapplied changeset http://hg.octave.org/mxe-octave/rev/c0fe8d735baf
|
Mon 06 Jan 2014 02:21:44 PM UTC, comment #6:
agreed, better to revert the minimization hack.
as for the definitive solution, it seems to involve a linker setting, from "console" to "window", see:
<http://stackoverflow.com/questions/2139637/hide-console-of-windows-application>
|
Mon 06 Jan 2014 12:32:27 PM UTC, comment #5:
I built a new installer to test and put it on a system where I had deleted the previous ~/.config/octave direcotry so I could make sure that the initial welcome wizard was still working properly. With the "run minimized" option selected for the shortcut, the welcome wizard was also minimized, so at first I thought Octave was not working properly. Maybe we are missing some kind of "raise" or "show" call in the wizard? If that's not easy to fix, then I suggest that we switch back to the previous mode. Then the initial terminal window can serve the purpose of the splash screen. But seriously, starting the welcome wizard minimized is worse than briefly showing a terminal window.
|
Fri 03 Jan 2014 03:49:18 PM UTC, comment #4:
Pushed to mxe-octave: http://hg.octave.org/mxe-octave/rev/b5abbada6616
|
Fri 03 Jan 2014 02:51:10 PM UTC, comment #3:
here's a diff as per <http://nsis.sourceforge.net/Docs/Chapter4.html#4.9.3.4>
it's not an hg patch as mxe-octave is not in my tree
(file #30173)
|
Fri 03 Jan 2014 02:48:21 PM UTC, comment #2:
Indeed, "Run minimized" helps.
|
Fri 03 Jan 2014 09:47:05 AM UTC, comment #1:
Yeah this could be annoying, but IMO only slightly.
On my Windows systems (XP & 7) it's easily fixed in the shortcuts (Desktop & Start menu) by selecting "Run minimized" in the shortcut's Properties. I have no more access to Win 8, but IIRC it works similarly there.
Please try this out and report back.
I suppose this could already be fixed in the MXE-built NSIS installer - but I don't know my way around in NSIS, do you?
Hint: have a look in the makeinst-script.sh here:
http://hg.octave.org/mxe-octave
the Start Menu shortcut sections are easily found
|
Fri 03 Jan 2014 03:35:33 AM UTC, original submission:
as per screenshot attached
sorry I have no clue where to search
|