With Xailer 2.0.0 (January 2009), when you add a new component to a form,
and its variable name is similar to a pre-existing component on another part
of the form, it seems that the original component is lost. I wish I could be
more specific about this problem, but I only discover the problem when I
attempt to compile the project and Xailer tells me that a component is
missing. The component still exists on the form, so if I go back and
manually add the component statement in the .prg file, everything compiles
correctly.
Xailer does not warn if the new component name is the same as a component
that already exists on the form. That would be helpful. Of course, in this
case, the new component I am adding does not have the same name, but a
similar name, such as:
Original component: oButtonEdit
New component: oButtonEditCase
Perhaps the part of the program that is generating and updating the .prg
file and keeping it in sync with the .xfm file is only comparing the first
10 characters of the component name or something like that, but, in my
humble opinion, Xailer should warn you at the time the component is named if
there is a problem with the component name.
Thanks,
Gary
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
New Components on a form overwrite existing components in some cases
-
g.s.rogers
- Mensajes: 202
- Registrado: Dom Feb 17, 2008 3:35 am
-
g.s.rogers
- Mensajes: 202
- Registrado: Dom Feb 17, 2008 3:35 am
New Components on a form overwrite existing components in some cases
I think that the problem is entirely related to unintentionally naming a new
component to the same name as an existing component. When that is done, the
older component is overwritten in the component list section of the .prg
file without warning. If the new component is then renamed to avoid
duplication, the old component name has to be manually added back to the
component list.
Therefore, I would suggest that Xailer warn you when you name a control the
same as an existing control. It would be a nice feature to prevent this
problem.
Gary
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:[email=4a5e2785@svctag-j7w3v3j....]4a5e2785@svctag-j7w3v3j....[/email]
> With Xailer 2.0.0 (January 2009), when you add a new component to a form,
> and its variable name is similar to a pre-existing component on another
> part of the form, it seems that the original component is lost. I wish I
> could be more specific about this problem, but I only discover the problem
> when I attempt to compile the project and Xailer tells me that a component
> is missing. The component still exists on the form, so if I go back and
> manually add the component statement in the .prg file, everything compiles
> correctly.
>
> Xailer does not warn if the new component name is the same as a component
> that already exists on the form. That would be helpful. Of course, in this
> case, the new component I am adding does not have the same name, but a
> similar name, such as:
>
> Original component: oButtonEdit
> New component: oButtonEditCase
>
> Perhaps the part of the program that is generating and updating the .prg
> file and keeping it in sync with the .xfm file is only comparing the first
> 10 characters of the component name or something like that, but, in my
> humble opinion, Xailer should warn you at the time the component is named
> if there is a problem with the component name.
>
> Thanks,
> Gary
component to the same name as an existing component. When that is done, the
older component is overwritten in the component list section of the .prg
file without warning. If the new component is then renamed to avoid
duplication, the old component name has to be manually added back to the
component list.
Therefore, I would suggest that Xailer warn you when you name a control the
same as an existing control. It would be a nice feature to prevent this
problem.
Gary
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:[email=4a5e2785@svctag-j7w3v3j....]4a5e2785@svctag-j7w3v3j....[/email]
> With Xailer 2.0.0 (January 2009), when you add a new component to a form,
> and its variable name is similar to a pre-existing component on another
> part of the form, it seems that the original component is lost. I wish I
> could be more specific about this problem, but I only discover the problem
> when I attempt to compile the project and Xailer tells me that a component
> is missing. The component still exists on the form, so if I go back and
> manually add the component statement in the .prg file, everything compiles
> correctly.
>
> Xailer does not warn if the new component name is the same as a component
> that already exists on the form. That would be helpful. Of course, in this
> case, the new component I am adding does not have the same name, but a
> similar name, such as:
>
> Original component: oButtonEdit
> New component: oButtonEditCase
>
> Perhaps the part of the program that is generating and updating the .prg
> file and keeping it in sync with the .xfm file is only comparing the first
> 10 characters of the component name or something like that, but, in my
> humble opinion, Xailer should warn you at the time the component is named
> if there is a problem with the component name.
>
> Thanks,
> Gary
-
g.s.rogers
- Mensajes: 202
- Registrado: Dom Feb 17, 2008 3:35 am
New Components on a form overwrite existing components in some cases
I think that the problem is entirely related to unintentionally naming a new
component to the same name as an existing component. When that is done, the
older component is overwritten in the component list section of the .prg
file without warning. If the new component is then renamed to avoid
duplication, the old component name has to be manually added back to the
component list.
Therefore, I would suggest that Xailer warn you when you name a control the
same as an existing control. It would be a nice feature to prevent this
problem.
Gary
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:[email=4a5e2785@svctag-j7w3v3j....]4a5e2785@svctag-j7w3v3j....[/email]
> With Xailer 2.0.0 (January 2009), when you add a new component to a form,
> and its variable name is similar to a pre-existing component on another
> part of the form, it seems that the original component is lost. I wish I
> could be more specific about this problem, but I only discover the problem
> when I attempt to compile the project and Xailer tells me that a component
> is missing. The component still exists on the form, so if I go back and
> manually add the component statement in the .prg file, everything compiles
> correctly.
>
> Xailer does not warn if the new component name is the same as a component
> that already exists on the form. That would be helpful. Of course, in this
> case, the new component I am adding does not have the same name, but a
> similar name, such as:
>
> Original component: oButtonEdit
> New component: oButtonEditCase
>
> Perhaps the part of the program that is generating and updating the .prg
> file and keeping it in sync with the .xfm file is only comparing the first
> 10 characters of the component name or something like that, but, in my
> humble opinion, Xailer should warn you at the time the component is named
> if there is a problem with the component name.
>
> Thanks,
> Gary
component to the same name as an existing component. When that is done, the
older component is overwritten in the component list section of the .prg
file without warning. If the new component is then renamed to avoid
duplication, the old component name has to be manually added back to the
component list.
Therefore, I would suggest that Xailer warn you when you name a control the
same as an existing control. It would be a nice feature to prevent this
problem.
Gary
"Gary S. Rogers" <g.s.rogers@att.net> wrote in message
news:[email=4a5e2785@svctag-j7w3v3j....]4a5e2785@svctag-j7w3v3j....[/email]
> With Xailer 2.0.0 (January 2009), when you add a new component to a form,
> and its variable name is similar to a pre-existing component on another
> part of the form, it seems that the original component is lost. I wish I
> could be more specific about this problem, but I only discover the problem
> when I attempt to compile the project and Xailer tells me that a component
> is missing. The component still exists on the form, so if I go back and
> manually add the component statement in the .prg file, everything compiles
> correctly.
>
> Xailer does not warn if the new component name is the same as a component
> that already exists on the form. That would be helpful. Of course, in this
> case, the new component I am adding does not have the same name, but a
> similar name, such as:
>
> Original component: oButtonEdit
> New component: oButtonEditCase
>
> Perhaps the part of the program that is generating and updating the .prg
> file and keeping it in sync with the .xfm file is only comparing the first
> 10 characters of the component name or something like that, but, in my
> humble opinion, Xailer should warn you at the time the component is named
> if there is a problem with the component name.
>
> Thanks,
> Gary