1. Release IDE version 0.18.6m
I've released the next IDE (0.18.6m) which may be found at
http://user.txcyber.com/~camping/judith.html and further expands 'layering',
improves Code Editor when user swaps code from control-event or modules in
and out and fixes a number of bugs.
You may view the changes (do a find on What's New ) here:
http://user.txcyber.com/~camping/IDE.htm .
Enjoy!
~judith
2. Re: Release IDE version 0.18.6m
I don't know if you'ved noticed but in IDE for winlib 18.5, when you execute
a program from within IDE 18.5 with multiple layers and the frame window is
set on, say layer 2, (and a user presses 'run') everyting before it (in this
case, layer 1) produces an error message in ex.err
for example:
not declared messages etc...
The problem seems to be, when a user presses 'run' when for example 'layer
3' is in the frame window insted of the main_win in the frame window, IDE
18.5 tries to execute from layer3, instead if executing from the start.
This seems to be a serious problem for layering,
If U like an example, make a window with two layers.
Then have the second layer the frame window view,
then press 'run' from the toolbar.
----- Original Message -----
From: "Judith Evans" <camping at txcyber.com>
To: "Eu Forum" <EUforum at topica.com>
Sent: Monday, February 09, 2004 11:59 PM
Subject: Release IDE version 0.18.6m
>
>
> I've released the next IDE (0.18.6m) which may be found at
> http://user.txcyber.com/~camping/judith.html and further expands
'layering',
> improves Code Editor when user swaps code from control-event or modules in
> and out and fixes a number of bugs.
>
> You may view the changes (do a find on What's New ) here:
> http://user.txcyber.com/~camping/IDE.htm .
>
> Enjoy!
> ~judith
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>
> --
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.580 / Virus Database: 367 - Release Date: 6/02/04
>
---
--
3. Re: Release IDE version 0.18.6m
I reloaded IDE 0.18.5 to test this and have not be able to reproduce the
problem.
I created a project with layer0 with an assortment of controls and layer 1
with a group and two radio controls. With layer 1 active and Menu Run,
everything seems ok. No ex.err. I must be miss understanding something you
are saying.
What version of (tm)Windows are you using and what version of Euphoria and
Win32lib? Or perhaps you can send me a project file that demonstates the
situation.
~judith
Hayden McKay wrote:
I don't know if you'ved noticed but in IDE for winlib 18.5, when you execute
a program from within IDE 18.5 with multiple layers and the frame window is
set on, say layer 2, (and a user presses 'run') everyting before it (in this
case, layer 1) produces an error message in ex.err
for example:
not declared messages etc...
The problem seems to be, when a user presses 'run' when for example 'layer
3' is in the frame window insted of the main_win in the frame window, IDE
18.5 tries to execute from layer3, instead if executing from the start.
This seems to be a serious problem for layering,
If U like an example, make a window with two layers.
Then have the second layer the frame window view,
then press 'run' from the toolbar.
4. Re: Release IDE version 0.18.6m
------=_NextPart_000_000D_01C3F019.45774980
I'm running Win98SE 4.10.2222.A
Euphoria 2.4
Win32lib 0.59.1 8/June/2003
I tried to produce the same errors I was getting before but failed,
I encounted the problem when I made the origional version of Encryption
Utility found in the archives.
I have since removed the layers in the updated version and have completly
remodled it (using a new *.prj).
If anyone has an old copy of it U may be able to parse it to a *.prj file
and test with that. It was that origional *.prj that produced the errors I
mentioned below.
It is also the only layerd prog that I have experimented with sofar.
HOWEVER, I did find something else while trying to get back to the same
errors.
If I launch the attatched file from layer0, Everything works fine.
If I launch it from layer1 then the 'setVisible()' statements seem to
misbehave.
When launched from layer0, on the GotoLayer2 button, Group2 and everything
in it is made invisible
with one call to setVisible(Group2,False)
When lanched from layer1 the same call makes Group2 invisible but everything
in it remains visible.
Not a big problem, I dont mean to be a fuss pot!
----- Original Message -----
From: "Judith Evans" <camping at txcyber.com>
To: "Eu Forum" <EUforum at topica.com>
Sent: Tuesday, February 10, 2004 12:57 AM
Subject: Re: Release IDE version 0.18.6m
>
>
> I reloaded IDE 0.18.5 to test this and have not be able to reproduce the
> problem.
>
> I created a project with layer0 with an assortment of controls and layer 1
> with a group and two radio controls. With layer 1 active and Menu Run,
> everything seems ok. No ex.err. I must be miss understanding something you
> are saying.
>
> What version of (tm)Windows are you using and what version of Euphoria and
> Win32lib? Or perhaps you can send me a project file that demonstates the
> situation.
>
> ~judith
>
> Hayden McKay wrote:
> I don't know if you'ved noticed but in IDE for winlib 18.5, when you
execute
> a program from within IDE 18.5 with multiple layers and the frame window
is
> set on, say layer 2, (and a user presses 'run') everyting before it (in
this
> case, layer 1) produces an error message in ex.err
>
> for example:
> not declared messages etc...
>
> The problem seems to be, when a user presses 'run' when for example 'layer
> 3' is in the frame window insted of the main_win in the frame window, IDE
> 18.5 tries to execute from layer3, instead if executing from the start.
>
> This seems to be a serious problem for layering,
>
> If U like an example, make a window with two layers.
> Then have the second layer the frame window view,
> then press 'run' from the toolbar.
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>
> --
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.580 / Virus Database: 367 - Release Date: 6/02/04
>
---
------=_NextPart_000_000D_01C3F019.45774980
Content-Type: application/octet-stream; name=bug.prj
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="bug.prj"
#Version 0.18.5
#Counter: 7
#WinCounter: 1
#Window 1
#Control: Window1
X : 0
Y : 0
CX : 400
CY : 300
ControlLayer: 0
Title : Window1
Class : Window
Enabled : 0
Checked : 0
Parent :
PClass :
SeqParentName :
SeqParentClass :
SeqChildName :
Visible : 1
BkColor : 0
EnableC : 1
Style : 0
TypStyle:
ExStyle : 0
Local : 1
#Control: Group2
AWindow : 5
X : 16
Y : 12
CX : 360
CY : 212
ControlLayer: 0
Title : Group2
Class : Group
Enabled : 0
Checked : 0
Parent :
PClass :
SeqParentName :
SeqParentClass :
SeqChildName : EditText3
SeqChildName : MleText4
Visible : 1
EnableC : 1
Style :
TypStyle:
ExStyle : 0
TabOrder : 1
Local : 1
#Control: EditText3
AWindow : 5
X : 32
Y : 32
CX : 328
CY : 24
ControlLayer: 0
Title : EditText3
Class : EditText
Enabled : 0
Checked : 0
Parent : Group2
PClass : Group
SeqParentName : Group2
SeqParentClass : Group
SeqChildName :
Visible : 1
EnableC : 1
Style :
TypStyle:
ExStyle : 0
TabOrder : 2
Local : 1
#Control: RichEdit5
AWindow : 5
X : 8
Y : 36
CX : 256
CY : 220
ControlLayer: 1
Title : RichEdit5
Class : RichEdit
Enabled : 0
Checked : 0
Parent :
PClass :
SeqParentName :
SeqParentClass :
SeqChildName :
EnableC : 1
Style : ES_NOHIDESEL
TypStyle:
ExStyle : 0
TabOrder : 4
Local : 1
#Control: MleText4
AWindow : 5
X : 32
Y : 64
CX : 328
CY : 148
ControlLayer: 0
Title : MleText4
Class : MleText
Enabled : 0
Checked : 0
Parent : Group2
PClass : Group
SeqParentName : Group2
SeqParentClass : Group
SeqChildName :
Visible : 1
EnableC : 1
Style :
TypStyle:
ExStyle : 0
TabOrder : 3
Local : 1
#Control: PushButton7
AWindow : 5
X : 280
Y : 168
CX : 88
CY : 28
ControlLayer: 1
Title : Goto Layer1
Class : PushButton
Enabled : 0
Checked : 0
Parent :
PClass :
SeqParentName :
SeqParentClass :
SeqChildName :
EnableC : 1
Style :
TypStyle:
ExStyle : 0
TabOrder : 6
Local : 1
#Proc: onClick
procedure PushButton7_onClick (integer self, integer event, sequence =
params)--params is ()
setVisible(PushButton7,False)
setVisible(Group2,True)
setVisible(RichEdit5,False)
end procedure
setHandler( PushButton7, w32HClick, routine_id("PushButton7_onClick"))
#EndProc
#Control: PushButton6
AWindow : 5
X : 288
Y : 232
CX : 88
CY : 28
ControlLayer: 0
Title : Goto Layer2
Class : PushButton
Enabled : 0
Checked : 0
Parent :
PClass :
SeqParentName :
SeqParentClass :
SeqChildName :
Visible : 1
EnableC : 1
Style :
TypStyle:
ExStyle : 0
TabOrder : 5
Local : 1
#Proc: onClick
procedure PushButton6_onClick (integer self, integer event, sequence =
params)--params is ()
if isVisible(Group2) then
setVisible(Group2,False)
setVisible(RichEdit5,True)
setVisible(PushButton7,True)
end if
end procedure
setHandler( PushButton6, w32HClick, routine_id("PushButton6_onClick"))
#EndProc
------=_NextPart_000_000D_01C3F019.45774980
Content-Type: text/plain; x-avg=cert; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Content-Description: "AVG certification"
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.580 / Virus Database: 367 - Release Date: 6/02/04
5. Re: Release IDE version 0.18.6m
Yes, I see the problem you described now. Thanks for the project file. This
bug is odd since IDE doesn't store the layers any differently than if you
had not used layering. There is something wrong when the exw is generated,
however, because it does not assign Group2 as parent of EditText2 and
MleText4 when layer 1 is active and I do not see the bug right off the bat.
When I find the problem I will post back to Topica and probably release a
patch.
Reporting this bug does not make you a fuss pot and I am sorry if I made you
feel that way! I certainly want IDE bug free. Sometimes I just do not
understand what the problem is and it takes an example to clarify for me.
~judith
Hayden McKay wrote:
I'm running Win98SE 4.10.2222.A
Euphoria 2.4
Win32lib 0.59.1 8/June/2003
I tried to produce the same errors I was getting before but failed,
I encounted the problem when I made the origional version of Encryption
Utility found in the archives.
I have since removed the layers in the updated version and have completly
remodled it (using a new *.prj).
If anyone has an old copy of it U may be able to parse it to a *.prj file
and test with that. It was that origional *.prj that produced the errors I
mentioned below.
It is also the only layerd prog that I have experimented with sofar.
HOWEVER, I did find something else while trying to get back to the same
errors.
If I launch the attatched file from layer0, Everything works fine.
If I launch it from layer1 then the 'setVisible()' statements seem to
misbehave.
When launched from layer0, on the GotoLayer2 button, Group2 and everything
in it is made invisible
with one call to setVisible(Group2,False)
When lanched from layer1 the same call makes Group2 invisible but everything
in it remains visible.
Not a big problem, I dont mean to be a fuss pot!
6. Re: Release IDE version 0.18.6m
The origional bug I found when user selects 'run' when viewing layer1, and
controls in layer0 where producing 'not declared' errors.
eg: In the bug.prj I posted I was expecting to get a
"If isVisible(Group2) then
Group2 has not been declared" error.
When selected run while viewing layer1.
I believe that this has something to do with the same bug we found below.
I dont know much about the IDE structure, but here is a posible fix that
would not require a huge operation to fix it.
Maybee when a user selects 'run' when viewing 'layer1' in the frame, IDE can
default the frame view back to 'layer0' (as if the user clicked the 'layer0'
tab) before produceing the exw. You could even do this silently so the frame
would still have layer1 in the view, but IDE would act like user is viewing
layer0. Then after exw is generated, IDE could return to its previouse state
and lauch the exw as normal.
----- Original Message -----
From: "Judith Evans" <camping at txcyber.com>
To: "Eu Forum" <EUforum at topica.com>
Sent: Tuesday, February 10, 2004 10:51 PM
Subject: Re: Release IDE version 0.18.6m
>
>
> Yes, I see the problem you described now. Thanks for the project file.
This
> bug is odd since IDE doesn't store the layers any differently than if you
> had not used layering. There is something wrong when the exw is generated,
> however, because it does not assign Group2 as parent of EditText2 and
> MleText4 when layer 1 is active and I do not see the bug right off the
bat.
> When I find the problem I will post back to Topica and probably release a
> patch.
>
> Reporting this bug does not make you a fuss pot and I am sorry if I made
you
> feel that way! I certainly want IDE bug free. Sometimes I just do not
> understand what the problem is and it takes an example to clarify for me.
> ~judith
>
> Hayden McKay wrote:
> I'm running Win98SE 4.10.2222.A
> Euphoria 2.4
> Win32lib 0.59.1 8/June/2003
>
> I tried to produce the same errors I was getting before but failed,
> I encounted the problem when I made the origional version of Encryption
> Utility found in the archives.
>
> I have since removed the layers in the updated version and have completly
> remodled it (using a new *.prj).
>
> If anyone has an old copy of it U may be able to parse it to a *.prj file
> and test with that. It was that origional *.prj that produced the errors I
> mentioned below.
> It is also the only layerd prog that I have experimented with sofar.
>
> HOWEVER, I did find something else while trying to get back to the same
> errors.
>
> If I launch the attatched file from layer0, Everything works fine.
> If I launch it from layer1 then the 'setVisible()' statements seem to
> misbehave.
>
> When launched from layer0, on the GotoLayer2 button, Group2 and everything
> in it is made invisible
> with one call to setVisible(Group2,False)
>
> When lanched from layer1 the same call makes Group2 invisible but
everything
> in it remains visible.
>
> Not a big problem, I dont mean to be a fuss pot!
>
>
>
> TOPICA - Start your own email discussion group. FREE!
>
>
> --
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.580 / Virus Database: 367 - Release Date: 6/02/04
>
---
--
7. Re: Release IDE version 0.18.6m
Thanks for the idea, Hayden, but the problem is that IDE wants to figure out
parenting of controls at exw time. Parenting is normally established when
user drops a control onto Design or moves a control into a container
control. There are situations in which it needs to be re-established parent
at exw time. Since your post I found the bug in findDirectParent routine. It
wants to find parent of a control but only when the control is in the same
layer as the active layer. This routine serves a dual purpose (1) when
dropping into a control/moving the control in Design and (2) at exw time
(which I missed.) Since Layer 1 was the active control, IDE did not
re-establish Group2 in Layer 0 as parent of the other 2 controls and used
Window1 as parent. When Layer 0 is active then it worked. But if Layer 1
perhaps had a group control and child controls, and I internally set layer
to Layer 0, then the controls in Layer 1 would not parent to its group
control properly. This is probably more information than you wanted LOL. I
just need to fix findDirectParent to work correctly when fired from the exw
generation routine. Your suggestion would be a good one otherwise.
I'm not sure what the problem was when you got the " not declared" errors.
But, please do not use version 0.18.5 since it was a testing version, with
other bugs, and many testing versions followed until 0.18.6m which is the
official one.
~judith
Hayden McKay wrote:
The origional bug I found when user selects 'run' when viewing layer1, and
controls in layer0 where producing 'not declared' errors.
eg: In the bug.prj I posted I was expecting to get a
"If isVisible(Group2) then
Group2 has not been declared" error.
When selected run while viewing layer1.
I believe that this has something to do with the same bug we found below.
I dont know much about the IDE structure, but here is a posible fix that
would not require a huge operation to fix it.
Maybee when a user selects 'run' when viewing 'layer1' in the frame, IDE can
default the frame view back to 'layer0' (as if the user clicked the 'layer0'
tab) before produceing the exw. You could even do this silently so the frame
would still have layer1 in the view, but IDE would act like user is viewing
layer0. Then after exw is generated, IDE could return to its previouse state
and lauch the exw as normal.
