Hi,
I write to you because I used to find very helpfull people on this list while
developping on galaxy.
Can anybody suggest a project management software ? My needs are quite simple.
For each task I have :
- a list of developpeurs
- an initial work load (in days)
- many interruptions for small things to do but not real tasks
- additionnal work load because things changed since beginning
- holidays during this period
- a delivery that is never on time !!
I would prefer a software not too expensive (<100$)
If it could work on Mac, it would be great. I used to use Mac Project, but it
does not fit all needs
and is quite complicated for me. I built my own one, but a lot of things are
lacking ...
Thanks for any information.
--
Riccardo Cohen
Articque
Les Roches
37230 Fondettes
France
web = http://www.articque.com
tel: +33 02 47 49 90 49
fax: +33 02 47 49 91 49
Victor R. Volkman wrote:
> If nobody
> speaks for the manuals, into the great recycling bin in the sky
> they will go.
That's where my two copies went. (I kept the black boxes, though.
They were too cool.)
> * Memorabilia: may include some of the following
> Tech support policy
So... i was contracting through Visix (who took 50% of the bill rate
and doubled up my expenses to the customer).
One day, i had a problem i was sure they could easily answer.
Me: Tech support, please.
She: Valid support license number, please.
Me: Uh, i don't have one, but i work for you.
She: Uh huh. Valid support license number, please.
Me: Can you just pick one of the [fortune 50 company]'s licenses.
She: No. Valid support license number, please.
Me: Look, Visix is charging this guy Latinum for me to be a vexpert.
She: That's nice. Valid support license number, please.
Me: Is there someone else i can talk to about this?
She: No. Valid support license number, please.
So we wasted a day (which made money for Visix ;) hunting for the closet loaded
with black boxes to find a card with a number.
Called with a number (which was a Unix number for an NT problem, but i wasn't
about to tell *her* that ;).
10 minutes later, a guy calls me back and solves my problem in 2 minutes.
(vhelp integration/launching IIRC)
dik
Auction ends August 7th and there have been no bids yet. If nobody
speaks for the manuals, into the great recycling bin in the sky
they will go.
VISIX GALAXY COMPLETE BOOK SET - RARE - NR
You are bidding one one complete lot of Visix Galaxy Application
Environment manuals for the "C" language binding. These are from
Galaxy 2.5 release but really apply just as well to Galaxy 2.6/2.7.
Quality varies, some are shrinkwrapped(!) and some have covers which
are slightly separated from the binding.
Each manual set weighs 19.5 pounds and buyer pays all shipping in
addition to final bid price. Do not bid unless you understand
this. Set includes
* Release notes (154pp)
* Galaxy Distributed Application Services
* Tutorial for Unix
* Tutorial for NT
* Visual Resource Builder User's Guide
* Tools
* Installation Guide: Windows/NT
* Installation Guide: Unix
* Reference Summary (524 pp)
* Reference Manual, Vol 1, 2, and 3 (2100 pp)
* Memorabilia: may include some of the following
Welcome letter signed by Nik Ivancic
Bug report forms
Tech support policy
This offer is in no way to be construed as a sale of software.
Only new/used manuals are being sold here. No media is available,
so don't ask.
<http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3541988443>http://cgi.ebay.c\
om/ws/eBayISAPI.dll?ViewItem&item=3541988443
You are bidding one one complete lot of Visix Galaxy Application
Environment manuals for the "C" language binding. These are from
Galaxy 2.5 release but really apply just as well to Galaxy 2.6/2.7.
Quality varies, some are shrinkwrapped(!) and some have covers which
are slightly separated from the binding.
<P>Each manual set weighs 19.5 pounds and buyer pays all shipping in
addition to final bid price. Do not bid unless you understand
this. Set includes
<UL>
<LI>Release notes (154pp)
<LI>Galaxy Distributed Application Services
<LI>Tutorial for Unix
<LI>Tutorial for NT
<LI>Visual Resource Builder User's Guide
<LI>Tools
<LI>Installation Guide: Windows/NT
<LI>Installation Guide: Unix
<LI>Reference Summary (524 pp)
<LI>Reference Manual, Vol 1, 2, and 3 (2100 pp)
<LI>Memorabilia: may include some of the following
<UL>
<LI>Welcome letter signed by Nik Ivancic
<LI>Bug report forms
<LI>Tech support policy
</UL>
</UL>
<P>This offer is in no way to be construed as a sale of software.
Only new/used manuals are being sold here. No media is available,
so don't ask.
<P>Thank you for bidding!
Domestic UPS Ground shipping is $30. However, US Mail Media Mail
quoted me $10. Don't know whether they would really ship 20 pounds
for that low.
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=3541988443
Click above to bid!
Arthur C H Lee wrote:
>
> We are using the Galaxy 2.6 and 3.0. We have a multiple screens
> setup on a Sun/Solaris/X11 system and it is NOT using the Xinerama
> method. Does anyone know how to create a new vdialog to a different
> screen once the main has been started on one?
Unfortunately, I don't think this is possible.
Galaxy tracks the main display (based on the DISPLAY variable on X11)
internally and just about every graphical object ultimately ends up
being associated with it.
In order to create an object on another screen, you'd need to create a
new display object, and you'd have to duplicate all of the global
structures that are associated with it. Galaxy definitely has no
mechanism for this. I suspect adding this to Galaxy would be extremely
painful.
If you actually need this capability, I suspect you'll be better off
using Xinerama than trying to hack Galaxy into doing it the old
fashioned way.
Note that Xinerama parallels the way multiple screens are supported on
MacOS and (I think) Windows.
> Is it possible to switch or set a different root window for a new
> vdialog? Does anyone have any experience to share in making use of
> multiple screens on a Galaxy / X11 system?
As far as I remember, Galaxy apps that put windows on secondary screens
only do it by making X calls, not by creating actual vdialogs.
-- David
Good day all...
We are using the Galaxy 2.6 and 3.0. We have a multiple screens setup on a
Sun/Solaris/X11 system and it is NOT using the Xinerama method. Does anyone know
how to create a new vdialog to a different screen once the main has been started
on one?
In X11 level, I was able to do this type of operation (like XCreateSimpleWindow)
by getting a different root parent window (RootWindow call) with a specific
screen number.
I could not find any similar interface in the Galaxy package. So far, I found a
few global variables, like _vwindowXDisplay and _vwindowXScreenNumber, from
their example "subwin". The _vwindowXScreenNumber variable gave the correct
number as that of the main dialog. I was silly enough to think that by simply
modifing this variable, any subsequent new dialog would shoot to the screen I
wanted. I have not had any luck yet.
Is it possible to switch or set a different root window for a new vdialog? Does
anyone have any experience to share in making use of multiple screens on a
Galaxy / X11 system?
Thanks,
Arthur
-----------------------------------------------------------------
Arthur Lee, Software Development Manager
Hampson-Russell Software, Veritas DGC
Email: arthur_lee@..., arthur@...http://www.hampson-russell.comhttp://www.veritasdgc.com
-----------------------------------------------------------------
As far as I know, the vname is simply a vstr stored in a global hash. So there
is no reason why it
should be limited, except if the global hash limits the key length.
And I dont see why vrb would limit it also... But I did not check.
Robbert de Groot wrote:
> Added to this, the longest string or tag name that can be set on a vrb
> resource item or value.
>
> At 2003-05-28, 17:24 -0700, gum@yahoogroups.com wrote:
>
>>Just curious...
>>
>>What is the longest string that a vname can represent?
>
>
>
> Robbert de Groot
>
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
>
--
Riccardo Cohen
Articque
Les Roches
37230 Fondettes
France
email = rcohen@...
web = http://www.articque.com
tel: +33 02 47 49 90 49
fax: +33 02 47 49 91 49
Added to this, the longest string or tag name that can be set on a vrb
resource item or value.
At 2003-05-28, 17:24 -0700, gum@yahoogroups.com wrote:
>Just curious...
>
>What is the longest string that a vname can represent?
Robbert de Groot
Can someone please supply me with a copy of lroot? I'm trying to
build Galaxy C++ for Sun CC5.2. The only copy of the source code
we've got remaining from when we bought it from Visix is a partially
complete version which someone built on Windows. We legally have
ownership of the sources but don't have the original CDs!
My copy of lroot in the bin directory is a blank file. I've tried
creating a version from the Windows .bat version but it hasn't been
successful so far.
If someone could provide me with a copy of lroot that would be
great. If they could also provide me with a built version of vbuild
then even better.
If I can't get galaxy built for Sun CC5.2 we're stuck with CC4.2 for
the rest of the life of the application. Ambencia want a loony
amount of money to supply us with the libs which we effectively
alreay own.
Thanks,
Andy
Thanks for the info, Francis & Joey!
I'm happy to say Ambiencia finally responded to our email yesterday
afternoon... so at least I know we can look at getting price quotes
now.
Thanks for your help,
Barb
bsvachak@...
Yes, they are still around. I received a demo copy of Galaxy 3.0 for Linux
from them last month.
Francis Ma
Hampson-Russell
A Veritas Company
-----Original Message-----
From: svachak [mailto:bsvachak@...]
Sent: Wednesday, April 02, 2003 9:20 AM
To: gum@yahoogroups.com
Subject: [gum] Re: Ambiencia Contacts?
Sorry for the typo:
this:
"We've been trying to get in touch with them for the last few weeks
and have had much success."
should have said:
"We've been trying to get in touch with them for the last few weeks
and have NOT had much success."
Barb
bsvachak@...
--- In gum@yahoogroups.com, "svachak" <bsvachak@a...> wrote:
> Hi there!
>
> Does anyone have any current/updated contact information for
> Ambiencia?
>
> We've been trying to get in touch with them for the last few weeks
and
> have had much success. We've tried email addresses from previous
> correspondence as well as all of the email addresses noted on the
> website - no response. We've also called the phone number listed on
> the website for fax/voice mail, but it seems to ring about 10 times
> and eventually disconnects.
>
> Any ideas if the company is still around?
>
> Thanks!
>
> Barb
> bsvachak@w...
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
I last heard from them over a year ago. They were in theory going to
purchase the rights to my Galaxy based widgets but backed out of the deal at
the last minute (after they have received the source code mind you, so keep
you eyes open).
joey
hot-n-GUI, Inc.
----- Original Message -----
From: "svachak" <bsvachak@...>
To: <gum@yahoogroups.com>
Sent: Wednesday, April 02, 2003 8:19 AM
Subject: [gum] Re: Ambiencia Contacts?
>
> Sorry for the typo:
>
> this:
> "We've been trying to get in touch with them for the last few weeks
> and have had much success."
>
> should have said:
> "We've been trying to get in touch with them for the last few weeks
> and have NOT had much success."
>
> Barb
> bsvachak@...
>
> --- In gum@yahoogroups.com, "svachak" <bsvachak@a...> wrote:
> > Hi there!
> >
> > Does anyone have any current/updated contact information for
> > Ambiencia?
> >
> > We've been trying to get in touch with them for the last few weeks
> and
> > have had much success. We've tried email addresses from previous
> > correspondence as well as all of the email addresses noted on the
> > website - no response. We've also called the phone number listed on
> > the website for fax/voice mail, but it seems to ring about 10 times
> > and eventually disconnects.
> >
> > Any ideas if the company is still around?
> >
> > Thanks!
> >
> > Barb
> > bsvachak@w...
>
>
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
Sorry for the typo:
this:
"We've been trying to get in touch with them for the last few weeks
and have had much success."
should have said:
"We've been trying to get in touch with them for the last few weeks
and have NOT had much success."
Barb
bsvachak@...
--- In gum@yahoogroups.com, "svachak" <bsvachak@a...> wrote:
> Hi there!
>
> Does anyone have any current/updated contact information for
> Ambiencia?
>
> We've been trying to get in touch with them for the last few weeks
and
> have had much success. We've tried email addresses from previous
> correspondence as well as all of the email addresses noted on the
> website - no response. We've also called the phone number listed on
> the website for fax/voice mail, but it seems to ring about 10 times
> and eventually disconnects.
>
> Any ideas if the company is still around?
>
> Thanks!
>
> Barb
> bsvachak@w...
Hi there!
Does anyone have any current/updated contact information for
Ambiencia?
We've been trying to get in touch with them for the last few weeks and
have had much success. We've tried email addresses from previous
correspondence as well as all of the email addresses noted on the
website - no response. We've also called the phone number listed on
the website for fax/voice mail, but it seems to ring about 10 times
and eventually disconnects.
Any ideas if the company is still around?
Thanks!
Barb
bsvachak@...
My Galaxy application crashed after standing idle for several
minutes, giving the following error on my terminal window...
"An error has occurred
Error 1: /Return/
Message: X error: BadLength (poly request too large or
internal Xlib length error);
serial: 45302; major: 74; minor: 0; resource: 0;"
From experience, this format of error message has been related to
issues with the .vr file that is associated with the application.
However, I have not seen this particular error before, and am not
sure what could be causing it.. (the X libraries appear fine).
Any words of wisdom that would shed some light on this issue?
Chris Barnes
United Space Alliance
NASA Johnson Space Center
We've seen this all the time! VRE, VRB are known to be unstable and have
some gotchas.
The best way I found out to work around this problem is to make a copy of
the changed dialog/container/whatever and delete the old one. Then rename
the copy to the proper name. This seems to work.
Or try to save to a new vr file and that might also work. I do this every
now and then when vr2vrx dumps on the vr I was working on.
Either that or grab the nearest chicken and make a sacrifice to the silicon
god. You must have angered her somehow. :)
At 2003-02-24, 18:35 +0000, Chris Barnes <dadawgpounddude@...> wrote:
>I had a wierd experience using vre..
>
>I was changing the features of a button in my Galaxy application. I
>went to the menu afterwards and clicked on 'Save file', which was
>enabled after I made my changes. After saving the file, the menu
>choice was disabled, as expected. I then exited vre normally. The
>next time I went into vre for the same file, I noticed that the
>changes that I saved were reverted (!!) and that the name of the
>container that contained the changed button had been somehow erased
>(!!).
>
>This was a normal procedure that always had worked before until
>Friday afternoon, when this happened. Nobody else accesses that file
>but me.
>
>I checked the permissions of the file and directory and had read-
>write permissions for both. I then went back, made the changes again
>and tried to save, and this time it saved the names, but not the
>button changes (!). I had to do a 'Save As' to get the changes in.
>
>I have never seen vre act this way before. Is there a bug in Galaxy
>C++ regarding this? Is there a way I can get around this, or was
>this a fluke? What gives??
>
>Chris Barnes
>Lead Engineer
>United Space Alliance - NASA JSC
>
>
>
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Robbert de Groot
I had a wierd experience using vre..
I was changing the features of a button in my Galaxy application. I
went to the menu afterwards and clicked on 'Save file', which was
enabled after I made my changes. After saving the file, the menu
choice was disabled, as expected. I then exited vre normally. The
next time I went into vre for the same file, I noticed that the
changes that I saved were reverted (!!) and that the name of the
container that contained the changed button had been somehow erased
(!!).
This was a normal procedure that always had worked before until
Friday afternoon, when this happened. Nobody else accesses that file
but me.
I checked the permissions of the file and directory and had read-
write permissions for both. I then went back, made the changes again
and tried to save, and this time it saved the names, but not the
button changes (!). I had to do a 'Save As' to get the changes in.
I have never seen vre act this way before. Is there a bug in Galaxy
C++ regarding this? Is there a way I can get around this, or was
this a fluke? What gives??
Chris Barnes
Lead Engineer
United Space Alliance - NASA JSC
Does anyone know anthing about this addendum to
the source CD?
(referred to by Dave Postill in message 210)
> # install the addendum files -- that this step may not be necessary
once a
> new CD containing
> these files in the correct place is burnt
>
> %md /visix/vsx/msa
> %cd /visix/vsx/msa/dt
> %tar xv /{addendum}/dt.tar
Thanks David!
i had figured out i needed to rebuild it, but got
bogged down trying to figure out what to do with it
once it was built.
dan
David Charlap wrote:
>
> Dan Norberg wrote:
> >
> > cd dn
> > lroot -defaults
> > /visix/vsx/arch/make/RCS/Environ_Sun4_5.4,v -->
> > /proj/aises_p/dn/visix/vsx/dn/Environ_Sun4_5.4
> > revision 1.7
> > done
> > Configuring libraries...
> > Done
> > Configuring environment file...
> > Done
> > Configuring buildenv file...
> > Done
> >
> > make
> > ln -s ./msa/./build .
> > ln -s ./msa/./BuiltinsSrc .
> > ln -s ./msa/./Builtins.nt .
> > creating include
> > creating install
> > creating lib
> > mkdir -p lib/vgalaxy1
> > mkdir -p lib/vgalaxy2
> > mkdir -p lib/vgalaxy3
> > mkdir -p lib/vgalaxy4
> > mkdir -p lib/vgalaxy5
> > mkdir -p lib/vgalaxy6
> > mkdir -p lib/vgalaxy7
> > creating src
> > creating src/build
> > creating fake src/Dependencies
> > creating src/makefile
> > making in ./src
> > Make_build (Make_link, makefile) is broken! No default rule.
> >
> > cd src
> >
> > make vbuild
> > make: Fatal error: Don't know how to make target `vbuild'
>
> mkdir ~/tmp
> cd ~/tmp
> cp ~/dn/msa/src/vbuild/* .
> gcc -o vbuild *.c
>
> cd ~/dn/src
> mkdir vbuild
> cd vbuild
> ~/tmp/vbuild -m
> make
>
> At this point, you should have a proper vbuild (in ~/dn/bin) Your
> builds will use that. I'd recommend copying this vbuild to someplace
> on
> your path (perhaps a ~/bin directory or something) so you'll have it
> when making new build trees in the future.
>
> You can discard the ~/tmp/* files at this point - they are only used
> for
> making a quick-and-dirty vbuild. It'll work for everything else, but
> it's better to use the one that is made using the vbuild-generated
> makefile. The quick-and-dirty one may include source files that are
> unnecessary for your platform.
>
> -- David
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Dan Norberg wrote:
>
> cd dn
> lroot -defaults
> /visix/vsx/arch/make/RCS/Environ_Sun4_5.4,v -->
> /proj/aises_p/dn/visix/vsx/dn/Environ_Sun4_5.4
> revision 1.7
> done
> Configuring libraries...
> Done
> Configuring environment file...
> Done
> Configuring buildenv file...
> Done
>
> make
> ln -s ./msa/./build .
> ln -s ./msa/./BuiltinsSrc .
> ln -s ./msa/./Builtins.nt .
> creating include
> creating install
> creating lib
> mkdir -p lib/vgalaxy1
> mkdir -p lib/vgalaxy2
> mkdir -p lib/vgalaxy3
> mkdir -p lib/vgalaxy4
> mkdir -p lib/vgalaxy5
> mkdir -p lib/vgalaxy6
> mkdir -p lib/vgalaxy7
> creating src
> creating src/build
> creating fake src/Dependencies
> creating src/makefile
> making in ./src
> Make_build (Make_link, makefile) is broken! No default rule.
>
> cd src
>
> make vbuild
> make: Fatal error: Don't know how to make target `vbuild'
mkdir ~/tmp
cd ~/tmp
cp ~/dn/msa/src/vbuild/* .
gcc -o vbuild *.c
cd ~/dn/src
mkdir vbuild
cd vbuild
~/tmp/vbuild -m
make
At this point, you should have a proper vbuild (in ~/dn/bin) Your
builds will use that. I'd recommend copying this vbuild to someplace on
your path (perhaps a ~/bin directory or something) so you'll have it
when making new build trees in the future.
You can discard the ~/tmp/* files at this point - they are only used for
making a quick-and-dirty vbuild. It'll work for everything else, but
it's better to use the one that is made using the vbuild-generated
makefile. The quick-and-dirty one may include source files that are
unnecessary for your platform.
-- David
Hi all,
This is very similar to message 387 except that i'll
be building the C version for NT, not C++
Following the readme instructions, i get the output as at the
end of this message.
The Source CD we have is dated Mar 28 1998. Apparently there
was an update to it later on which i don't have. eg. I don't have
the makefile.src and makefile.vbuild files i've seen referred to
elsewhere.
I suspect the update contains what i need to get things working.
Can anyone tell me more about it and what's on it?
Or where i can get it?
Or at least the contents of makefile.src and makefile.vbuild?
thanks in advance
dan
cd dn
lroot -defaults
/visix/vsx/arch/make/RCS/Environ_Sun4_5.4,v -->
/proj/aises_p/dn/visix/vsx/dn/Environ_Sun4_5.4
revision 1.7
done
Configuring libraries...
Done
Configuring environment file...
Done
Configuring buildenv file...
Done
make
ln -s ./msa/./build .
ln -s ./msa/./BuiltinsSrc .
ln -s ./msa/./Builtins.nt .
creating include
creating install
creating lib
mkdir -p lib/vgalaxy1
mkdir -p lib/vgalaxy2
mkdir -p lib/vgalaxy3
mkdir -p lib/vgalaxy4
mkdir -p lib/vgalaxy5
mkdir -p lib/vgalaxy6
mkdir -p lib/vgalaxy7
creating src
creating src/build
creating fake src/Dependencies
creating src/makefile
making in ./src
Make_build (Make_link, makefile) is broken! No default rule.
cd src
make vbuild
make: Fatal error: Don't know how to make target `vbuild'
David Charlap wrote:
>
> Kim Andersen wrote:
> > Hi David,
> >
> > Your suggestion worked thanks!
> >
> > I changed the linker option from:
> > "/SUBSYSTEM:WINDOWS" to "/SUBSYSTEM:CONSOLE"
> >
> > Now the console appears automatically and displays the output. I
> > didn't think this option was allowed for a graphical program but it
> > seems to work.
>
> I'm glad to hear that this seems to have worked.
>
> I would not recommend using this for a shipping app, however, since
> there may be other side effects of changing the application type that
> I'm unaware of.
This is how fltk switches the console off and on. I've used this technique
for years. Amazingly, it does what it appears to do and no other mamboM$magic.
dik
Kim Andersen wrote:
> Hi David,
>
> Your suggestion worked thanks!
>
> I changed the linker option from:
> "/SUBSYSTEM:WINDOWS" to "/SUBSYSTEM:CONSOLE"
>
> Now the console appears automatically and displays the output. I
> didn't think this option was allowed for a graphical program but it
> seems to work.
I'm glad to hear that this seems to have worked.
I would not recommend using this for a shipping app, however, since
there may be other side effects of changing the application type that
I'm unaware of.
Given the fact that this works, then we know that Galaxy is still
generating the output, and what you really need to do is create a
console window. You should be able to leave the app type as graphical
and explicitly create a console, which is probably a better idea. I
don't know the APIs offhand, but after browsing through the MSDN library
web site, I would start by trying the AllocConsole call (in Windows.h
and Kernel32.lib):
http://msdn.microsoft.com/library/en-us/dllproc/base/allocconsole.asp
If that doesn't work, browsing through the list of Console function may
reveal something that will work:
http://msdn.microsoft.com/library/en-us/dllproc/base/console_functions.asp
-- David
>> What happens if you launch your app from a DOS prompt?
>
> It makes no difference. The program starts and the DOS prompt is ready
> for another command but no messages appear.
>
> I know that when we re-compile and link the exact code using Galaxy
> 2.6 (Release) we have the "Galaxy Debug" window. With the exact same
> code and environment under Galaxy 3.0 (Release) it does not appear. The
> only difference is in the version of Galaxy used.
That's what I was afraid of.
On NT-derived systems (NT, 2K, XP), graphical applications must
explicitly open a console device for console output. Obviously, the
code to do this is only compiled in the debug libraries. I remember
that much.
I had thought that applications launched from a DOS prompt would
automatically inherit the DOS window as their console.
There's one other possibility that I remember working on NT4, which
might work on XP. In the compiler's settings, there's an option to tell
the linker that you're making a GUI app. If you leave this option out,
it will compile a console app. Unless XP has changed this (which may be
true), a console app can still open windows and do everything a GUI app
does. The difference will be that stdout/stderr will remain attached to
the DOS prompt window you launch from, and a DOS window will
automatically open if you launch from the GUI.
But I don't know if XP works this way, and I don't remember if the
Galaxy debug output will go to the window if you do this (but I think it
will.)
Best of luck.
-- David
>What happens if you launch your app from a DOS prompt?
>
>David
It makes no
difference. The program starts and the DOS prompt is ready for another command
but no messages appear.
I know that when we re-compile and link the
exact code using Galaxy 2.6 (Release) we have the “Galaxy Debug”
window. With the exact same code and environment under Galaxy 3.0 (Release) it
does not appear. The only difference is in the version of Galaxy used.
Kim Andersen
>>
>>We
recently upgraded to use Galaxy 3.0 from 2.6. Now the Galaxy Debug
>> window only appears for the
Debug version but not the optimized
>> (Release) versions. (vdebugDEBUG=0 etc.). Is there a way to
turn this
>> window on again as it worked in
Galaxy 2.6? It is very useful for
>> tracking error messages etc. in the release version.
>>
>>Note that I am running
on Windows XP if that is relevant
Kim Andersen wrote:
>
> We recently upgraded to use Galaxy 3.0 from 2.6. Now the Galaxy Debug
> window only appears for the Debug version but not the optimized
> (Release) versions. (vdebugDEBUG=0 etc.). Is there a way to turn this
> window on again as it worked in Galaxy 2.6? It is very useful for
> tracking error messages etc. in the release version.
>
> Note that I am running on Windows XP if that is relevant.
What happens if you launch your app from a DOS prompt?
-- David
We recently upgraded
to use Galaxy 3.0 from 2.6. Now the Galaxy Debug window only appears for the Debug
version but not the optimized (Release) versions. (vdebugDEBUG=0
etc.). Is there a way to turn this window on again as it worked in Galaxy 2.6?
It is very useful for tracking error messages etc. in the release version.
Note that I am running on Windows XP if
that is relevant.