At 01:37 AM 5/4/2013, Javier Valencia wrote:

R:azzak,

I have a couple of question that I have asked before but I don't believe I
got an answer.
The standard theme for all of our forms us Longhorn; however, users can
select any other theme they want and it is stored with their login
information. I have code in the "After Start EEP" of every form that checks
if the user's selected theme is different from Longhorn, and if it is, then
the new theme is enabled via PROPERTY command.

Javier,

When and which communication channel was used to ask your specific questions?


Can I embed just the Longhorn theme and maybe a couple of other popular
themes in the executable, but if a user selects one that is not embedded,
will the system default to the RBThemes9.DLL file? If the RBThemes9.DLL
is present, will it override the embedded theme?

In an R:Compiled application, when a THEMENAME option is used, either using
the PROPERTY command (PROPERTY RBASE_FORM THEMENAME 'value'), or as option
for CHOOSE, DIALOG, or PAUSE commands, if the theme file in not embedded,
it will look for the RBThemes9.DLL in the "same folder" with compiled EXE.


Currently, we update some forms periodically and we can load them on the
fly, even if users are connected (very handy). However, If a standard form
is embedded with the application and I need to update that specific form,
Is the only way to do it to recompile the application?

Correct!

First you will need to update the specific embedded resource(s) and then
recompile the application.

To reiterate ...

If you have selected to embedded form(s) as additional resources in your
compiled application, and if the form definition, EEPs, and controls are
changed, you must update the resource(s), the form in your case, and then
recompile the application.

Finally, any embedded resource file, if modified, MUST be updated using
the enhanced techniques, as stated in the original topic, and then the
application must be recompiled.

With great power, comes great responsibility!

Very Best R:egards,

Razzak.

www.rbase.com
www.facebook.com/rbase

Reply via email to