Hiding runtime in CA-Realizer
| Author |
Message |
|
Scott Wadd
#1 / 13
|
 Hiding runtime in CA-Realizer Howdy y'all.
I just picked up CA-Realizer 2.0 for what I thought to be an excellent
price, and, although I haven't had the chance to make anything too
wonderful with it yet, it really does seem great. However, I've
noticed one problem which, for me at least, is quite serious.
This is simply the fact that no mater what application I create, it's
always a child window of either the development environment or of the
runtime. For the development environment, this is fine, but I belive
that this looks quite unprofessional, and seems like a clumsy way to
do things. If the runtime window isn't maximized, it may cut off a
good portion of the application. Also, maximizing your programs means
maximizing the runtime window first. Is there any way to hide the
runtime window and have the application still visible? I noticed
something in the Users Guide, which says I should check the
APPLICATION INVISIBLE option in the .EXE options of Project Builder,
and put "SetSys(_Size,{_Restore}) in my program after the interface is
drawn. However, this doesn't appear to work. Am I doing it wrong, or
is this describing something different then what I'm attempting?
A few more things. I'm interested in CA-Realizer 3.0, specifically if
will also compile OS/2 applications, like version 2.0, and if it has a
feature that will solve my problem, if it's impossible in 2.0. Does
anyone know of a web page that describes it? If not, would someone
out there who uses it be kind enough to answer them for me?
Featurewise, CA-Realizer appears to be VASTLY superior to all versions
of Visual Basic. I'd hate to have to stop using it because of
something so stupid.
|
| Sun, 31 Jan 1999 03:00:00 GMT |
|
 |
|
John Scammacc
#2 / 13
|
Hiding runtime in CA-Realizer Quote:
><snip>
> This is simply the fact that no mater what application I create, it's
> always a child window of either the development environment or of the
> runtime. For the development environment, this is fine, but I belive
> that this looks quite unprofessional, and seems like a clumsy way to
> do things. If the runtime window isn't maximized, it may cut off a
> good portion of the application. Also, maximizing your programs means
> maximizing the runtime window first. Is there any way to hide the
> runtime window and have the application still visible? I noticed
> something in the Users Guide, which says I should check the
> APPLICATION INVISIBLE option in the .EXE options of Project Builder,
> and put "SetSys(_Size,{_Restore}) in my program after the interface is
> drawn. However, this doesn't appear to work. Am I doing it wrong, or
> is this describing something different then what I'm attempting?
> <snip>
I myself am new to Realizer, and GUI programming myself. I agree with you that Realizer is a very good product, however I too have noticed that not all of the commands and pre-defined constants do what they are supposed to do. I really can't help you with your question (I have about the same problem -- I just dabble right now, so it's not too important to me). Unfortunately The CA home page has no info. on Realizer, but you can call one of their 800 #'s and talk to a tech. There is also one tutorial guide for Realizer (that I know of). It's called Programming With CA-Realizer, by Steven Straley (Sirius Press). This book is ok and that's about it, I skimmed through the book, I plan to go back and read it further, I have noticed that the author does point out some tips. He also documents SOME commands and such that the Realizer documentation fails to touch. Try there and see if that helps. Sorry I couldn't help more
|
| Sun, 31 Jan 1999 03:00:00 GMT |
|
|
|
David Ullric
#3 / 13
|
Hiding runtime in CA-Realizer Quote:
> Howdy y'all.
> I just picked up CA-Realizer 2.0 for what I thought to be an excellent
> price, and, although I haven't had the chance to make anything too
> wonderful with it yet, it really does seem great. However, I've
> noticed one problem which, for me at least, is quite serious.
> This is simply the fact that no mater what application I create, it's
> always a child window of either the development environment or of the
> runtime. ...
Right. The default is an MDI application, they don't make it so obvious how to do anything else. You do it like so: 1. Insert the _Popup modifier in the FormNew - this gives you a form that doesn't belong to the main window, it sits on the screen independent of the main window. 2. When you "compile" the program into the "exe" you select Application Invisible under Compiler Options. (Somewhere in the manuals they talk about setting Application Invisible, so that you can get your application set up and then show it. Instead you set Application Invisible and _leave_ it invisible - the _Popup form appears anyway, tada.) --
David Ullrich
?his ?s ?avid ?llrich's ?ig ?ile
(Someone undeleted it for me...)
|
| Sun, 31 Jan 1999 03:00:00 GMT |
|
|
|
Scott Wadd
#4 / 13
|
Hiding runtime in CA-Realizer On Wed, 14 Aug 1996 15:26:15 -0500, David Ullrich
Quote:
> Right. The default is an MDI application, they don't make it so
>obvious how to do anything else. You do it like so:
> 1. Insert the _Popup modifier in the FormNew - this gives you
>a form that doesn't belong to the main window, it sits on the screen
>independent of the main window.
> 2. When you "compile" the program into the "exe" you select
>Application Invisible under Compiler Options. (Somewhere in the manuals
>they talk about setting Application Invisible, so that you can get your
>application set up and then show it. Instead you set Application Invisible
>and _leave_ it invisible - the _Popup form appears anyway, tada.)
Ok, I tried this with the some of the example programs, and the popup thing worked great. However, when I ran the .EXE file it generated, nothing appeared to happen (well, the hard drive started making noise, but nothing showed up on my screen). In my task list, the runtime appeared, but when I clicked on it, the application was no where to be found. It seems like it's loading up the program (the mouse curser changes to the hourglass on apps where it's supposed to happen) but isn't displaying the actual program at all. It also starts up the runtime in a minimized state. The runtime doesn't contain the running application though. I hate to trouble you with this again, because it's likely something silly that I'm going to notice in a little while, but I figured I better take the opportunity to ask while it's available, in case it's not something so simple. The application I first tried this on is WORLD.RLZ. I changed the
formnew line to this, except I didn't have the carriage return in the
middle::
FormNew(FormQUnique; "World Wide Enterprises", _Title + _Close +
_Minimize + _Popup)
And checked the "Application Invisible" box in the EXE options. Other
then that I left it alone.
I tried this on a few other example programs too. Is there something
I'm missing?
|
| Mon, 01 Feb 1999 03:00:00 GMT |
|
|
|
John Scammacc
#5 / 13
|
Hiding runtime in CA-Realizer Quote:
> Maybe they got it fixed in version 3.0.
> Man, I am still watching for the brochures promised me by CA!
> >I tried this on a few other example programs too. Is there something
> >I'm missing?
You too huh?
|
| Mon, 01 Feb 1999 03:00:00 GMT |
|
|
|
David Ullric
#6 / 13
|
Hiding runtime in CA-Realizer Guys, I don't know what you're talking about. For the record
I don't have CAR 3.0 figured out, been doing other things. But it
seems like we're talking about CAR 2.0 here. Do this:
1. Write a file popup.rlz containing the following code:
formnew(10;"",_Popup)
formcontrol(_Show)
idle 5
exit system
2. Start ProjectBuilder, open a New project, select popup.rlz
as the main source file, select ApplicationInvisible under
ProjectOptions, and compile.
3. Double-click on the resulting "exe".
If you don't get a window appearing in the middle of
the screen for five seconds, without seeing the "runtime"
window, then go back and read the instructions more carefully.
--
David Ullrich
?his ?s ?avid ?llrich's ?ig ?ile
(Someone undeleted it for me...)
|
| Mon, 01 Feb 1999 03:00:00 GMT |
|
|
|
Scott Wadd
#7 / 13
|
Hiding runtime in CA-Realizer On Thu, 15 Aug 1996 14:03:41 -0500, David Ullrich
Quote:
>Guys, I don't know what you're talking about. For the record >I don't have CAR 3.0 figured out, been doing other things. But it >seems like we're talking about CAR 2.0 here. Do this: >1. Write a file popup.rlz containing the following code:
>formnew(10;"",_Popup)
>formcontrol(_Show)
>idle 5
>exit system
>2. Start ProjectBuilder, open a New project, select popup.rlz
>as the main source file, select ApplicationInvisible under
>ProjectOptions, and compile.
>3. Double-click on the resulting "exe".
> If you don't get a window appearing in the middle of
>the screen for five seconds, without seeing the "runtime"
>window, then go back and read the instructions more carefully.
Have you applied bug fixes or anything else to your version? I'm also using 2.0 and I just tried this (I cut and pasted the source code to make sure I'm doing it right) It did the same thing again. For 5 seconds "POPUP.EXE" showed up in my task list, but when I clicked on it, only the runtime came up. Unfortunately, although I DID see the window when I ran it from the development environment, nothing came up when I ran the .EXE with Application Invisible checked. Please don't think we're trying to criticize you. I fully believe
that this works for you. However, it just doesn't seem to be working
for me.
|
| Mon, 01 Feb 1999 03:00:00 GMT |
|
|
|
Andrew Benjamin
#8 / 13
|
Hiding runtime in CA-Realizer Maybe they got it fixed in version 3.0.
Man, I am still watching for the brochures promised me by CA!
Quote: >I tried this on a few other example programs too. Is there something
>I'm missing?
|
| Tue, 02 Feb 1999 03:00:00 GMT |
|
|
|
Andrew Benjamin
#9 / 13
|
Hiding runtime in CA-Realizer I found out about CA Realizer 3.0 by someone who bought it
and wrote about it in a newsletter when I had earlier wrote
about version 2.
However, the rest of the world hasn't seen much promotion of the
product.
Hear that it is 32 bit and they made some changes to the editor.
That reminds me, I got to buzz the local CA people for it.
If you know where I can get it at under US100, let me know.
Quotes I got are for about US300.
Quote:
>> Maybe they got it fixed in version 3.0.
>> Man, I am still watching for the brochures promised me by CA!
>> >I tried this on a few other example programs too. Is there something
>> >I'm missing?
>You too huh?
|
| Tue, 02 Feb 1999 03:00:00 GMT |
|
|
|
David Ullric
#10 / 13
|
Hiding runtime in CA-Realizer Quote:
> On Thu, 15 Aug 1996 14:03:41 -0500, David Ullrich
> >Guys, I don't know what you're talking about. For the record
> >I don't have CAR 3.0 figured out, been doing other things. But it
> >seems like we're talking about CAR 2.0 here. Do this:
> >1. Write a file popup.rlz containing the following code:
> >formnew(10;"",_Popup)
> >formcontrol(_Show)
> >idle 5
> >exit system
> >2. Start ProjectBuilder, open a New project, select popup.rlz
> >as the main source file, select ApplicationInvisible under
> >ProjectOptions, and compile.
> >3. Double-click on the resulting "exe".
> > If you don't get a window appearing in the middle of
> >the screen for five seconds, without seeing the "runtime"
> >window, then go back and read the instructions more carefully.
> Have you applied bug fixes or anything else to your version?
Oh yeah, I forgot. Nothing in 2.0 works until you apply the bug patch - sorry about the sarcasm yesterday. I didn't realize that there was a problem with exactly this aspect of things but you really _do_ need that patch. You can get it in the forum on Conmpuserve (GO CAIDEV last I checked, which was a while ago), possibly you can get it elsewhere as well. Every once in a while I get a new machine, I install CAR 2.0, nothing works, then I remember the patch... --
David Ullrich
?his ?s ?avid ?llrich's ?ig ?ile
(Someone undeleted it for me...)
|
| Tue, 02 Feb 1999 03:00:00 GMT |
|
|
|
Dean Shaff
#11 / 13
|
Hiding runtime in CA-Realizer
: Oh yeah, I forgot. Nothing in 2.0 works until you apply
: the bug patch - sorry about the sarcasm yesterday.
: I didn't realize that there was a problem with exactly
: this aspect of things but you really _do_ need that patch. You
: can get it in the forum on Conmpuserve (GO CAIDEV last I checked,
: which was a while ago), possibly you can get it elsewhere as well.
: Every once in a while I get a new machine, I install CAR 2.0,
: nothing works, then I remember the patch...
The patch can be found on the Computer Associates web site. There are
two patches and you need both if you have an original version of 2.0. I
don't remember the URL off hand but I found it useing Yahoo. I't DOES
fix the _PopUp problem among others.
|
| Wed, 03 Feb 1999 03:00:00 GMT |
|
|
|
Neil Gou
#12 / 13
|
Hiding runtime in CA-Realizer
Quote: >Howdy y'all. (snip)
>maximizing the runtime window first. Is there any way to hide the
>runtime window and have the application still visible? I noticed
>something in the Users Guide, which says I should check the
>APPLICATION INVISIBLE option in the .EXE options of Project Builder,
>and put "SetSys(_Size,{_Restore}) in my program after the interface is
>drawn. However, this doesn't appear to work. Am I doing it wrong, or
>is this describing something different then what I'm attempting?
There are a couple of ways to do it, but all of them can only be done by handwriting some of the code in your app. I noticed that Dave Ulrich pointed out one way, so, I'll point out another. Use the SetSys commands to define the window size for your main app. Make your program frameless & borderless, and then size it and position it to exactly fit the program window. If you are going to retain a menu structure (which is optional), allow for the size of the menu in your program's layout. THEN, when compiling, set the application invisible, but NOTE: using this method will require that you use Restore System commands for the application to ever appear! The advantage to this approach is that you can set all system params
prior to the appearance of your app, so that it 'pops' on screen all
at once, instead of building to the screen. The manuals are a bit
sketchy on this method, but it does work well.
Quote: >A few more things. I'm interested in CA-Realizer 3.0, specifically if
>will also compile OS/2 applications, like version 2.0, and if it has a
>feature that will solve my problem, if it's impossible in 2.0. Does
>anyone know of a web page that describes it? If not, would someone
>out there who uses it be kind enough to answer them for me?
Version 3.0 is a massive improvement over 2.0 in all respects but one: it doesn't build OS/2 apps. I've kept 2.0 on my OS/2 partition for just that reason. However, where version 2 'only' had 7 manuals, version 3 has 12, which must be purchased sep- arately -- it ships only with partial docs and the rest on CD. Some may find this suitable, but if you are going to use it exten- sively, I'd suggest popping for the manuals. Quote: >Featurewise, CA-Realizer appears to be VASTLY superior to all versions
>of Visual Basic. I'd hate to have to stop using it because of
>something so stupid.
I find Realizer to be vastly superior to VB, as well. And, con- trary to the claims of some, I've not found any command or function that doesn't work properly. BUT, the learning curve is quite steep, as the manuals are more of a guide than instructional document. It is not only mandatory to 'RTFM', but you will need to establish your own educational procedures to get the most out of CA-R. Good luck!
--
electronic media producer + Terra Tu A\V
SysOp: Video Arts Department; Co-SIGop - Audio Arts SIG
|
| Fri, 05 Feb 1999 03:00:00 GMT |
|
|
|
Andrew Benjamin
#13 / 13
|
Hiding runtime in CA-Realizer Could you give us a review on CA-R 3? (Like its speed, charting, etc)
Getting information about it from CA is a pretty difficult thing.
The local CA office sent me to their distributor who didn't
know a thing about it.
I've email CA and got no response.
Betcha they don't even look in here.
Quote:
>Version 3.0 is a massive improvement over 2.0 in all respects
>but one: it doesn't build OS/2 apps. I've kept 2.0 on my OS/2
>partition for just that reason. However, where version 2 'only'
>had 7 manuals, version 3 has 12, which must be purchased sep-
>arately -- it ships only with partial docs and the rest on CD.
>Some may find this suitable, but if you are going to use it exten-
>sively, I'd suggest popping for the manuals.
|
| Tue, 09 Feb 1999 03:00:00 GMT |
|
| |
|
