Xailer forum

Hi,
If I open a PRG (Form) file with my plugin, when displaying the form in the designer, it will use the font "MS Sans Serif, 8", different from what is defined in the application project properties.

Do I need to do something?

Note:

1. I didn't set a font on any Form, I just set the default font in the project properties.
2. The Xailer wrote in "function Main", the code... Application:oFont := TFont():Create....
3. There is no TFont():Create in any PRG or XFM, only in the MAIN function.
4. If I open a form through "Project Manager", then see in Designer, Form font is correct, the same as defined in FUNCTION MAIN
   So there must be a way to open the PRG via plugin without misconfiguring the font.

Hello,

Check the font on project.xpj

Regards,

Good Morning,

The same in FUNCTION MAIN (I forgot to put it on the list above.)

Hurricane escribió: ↑Lun Oct 11, 2021 5:02 pm Hi,
If I open a PRG (Form) file with my plugin, when displaying the form in the designer, it will use the font "MS Sans Serif, 8", different from what is defined in the application project properties.

Do I need to do something?

Note:

1. I didn't set a font on any Form, I just set the default font in the project properties.
2. The Xailer wrote in "function Main", the code... Application:oFont := TFont():Create....
3. There is no TFont():Create in any PRG or XFM, only in the MAIN function.
4. If I open a form through "Project Manager", then see in Designer, Form font is correct, the same as defined in FUNCTION MAIN
   So there must be a way to open the PRG via plugin without misconfiguring the font.

Check the font is not defined on the XFM your are opening. if is defined, it takes precedence.

There is not. I reported this on the list (item 3).

ignacio escribió: ↑Mié Oct 13, 2021 6:42 pm Check the font is not defined on the XFM your are opening. if is defined, it takes precedence.

Send a sample

only:
a) set a default font in the project properties
b) open a PRG (form) file with PLUGIN
c) display the form in the Designer(see oFont property, wrong)

ignacio escribió: ↑Jue Oct 14, 2021 5:34 pmSend a sample

attachment: application project (default font already defined) and plugin.

to use the plugin with an open project...

• go to the project menu, option test Hurricane
• select a PRG with double click

Hello,

DLL not valid. Please send a very simple plugin source code showing the error.

Regards

Good Morning,

check your email.

Note: This problem also happens with Editor/IDE (topic)

regards,

Hello,

When you open a file via ::oPlgn:IEditor:OpenFile( cFile ) it opens the file without assigning to a project. It does not either control if is already assigned to a project. It just opens the file in the editor. That's all! On that case if the font is not assigned on the XFM file, the default Font on Xailer is Ms San Serif.

You should check if the file you want top open is assigned to any project and then open it from the project itself.

Try this:

::oPlgn:IEditor:Load( cFile ) // Full File Name


Regards,

Hi,

I imagined that. OpenFile is the only method available in the documentation.

if I try with ...LOAD(cFile)...
Error BASE/1004 Message not found: IDEEditor:LOAD

...must be the same mechanism when we click on the file, in Project Manager.

ignacio escribió: ↑Vie Oct 15, 2021 6:35 pm When you open a file via ::oPlgn:IEditor:OpenFile( cFile ) it opens the file without assigning to a project. It does not either control if is already assigned to a project. It just opens the file in the editor. That's all! On that case if the font is not assigned on the XFM file, the default Font on Xailer is Ms San Serif.

You should check if the file you want top open is assigned to any project and then open it from the project itself.

Try this:

::oPlgn:IEditor:Load( cFile ) // Full File Name

???
I've done this. this class does not have this method, see message in red.

ignacio escribió: ↑Vie Oct 15, 2021 7:48 pm

Código: Seleccionar todo

METHOD BrwDblClick( oSender, nKeys, nCol, nRow ) CLASS TFrmVPF2

   ::oPlgn:IEditor:Load( ::oBrw:GetValue(1) )  // Full File Name
   ::Close()
RETURN Nil

I solved it with IDEProjectMan:getModule
I needed to export information from some plugin classes and a lot of intuition.

It is very important to distribute all plugin statements (only CLASS IDE... to ENDCLASS). We are in the dark to use the plugin.
This will be an important addition to the documentation. Because the plugin code also changes, becoming incompatible with the documentation.

Another feature I created, I needed a lot of trial and error (extremely tiring), but I managed to finish.

Thanks