Author Topic: New specialization plugin  (Read 7781 times)

Jose-Carlos

  • Member
  • **
  • Posts: 26
Re: New specialization plugin
« Reply #105 on: November 13, 2018, 07:23:00 AM »
Hi Hervé,
is there a way to set a variable name in a littera way?
I would like to set the label property through the form plugin. It means that label text must contain the variable name and not the variable value.
The result should be: label = ${documentation} for example.
But I'm unable to use some escape characters to avoid the replacement of variable name by it's value.
I tried using single quote, backslash,...
Thanks for your help.

Hervé

  • Hero Member
  • *****
  • Posts: 369
Re: New specialization plugin
« Reply #106 on: November 13, 2018, 08:35:07 AM »
Hi Jose-Carlos,

I tried once but messed up with the regexp ... I'll work again on this case ...

Do you mind open a case on the GitHup site ?

Thanks and regards
Hervé

Jose-Carlos

  • Member
  • **
  • Posts: 26
Re: New specialization plugin
« Reply #107 on: November 13, 2018, 21:52:48 PM »
Hi Hervé,
the case is open on github.
Thanks.

rchevallier

  • Newbie
  • *
  • Posts: 4
Re: New specialization plugin
« Reply #108 on: November 23, 2018, 13:40:29 PM »
Great plugin BTW. Just one thing: I have 1.0.10 installed on Archi 4.3 Windows 10. However when I check for update (Preferences / Specialization ), it proposes the 1.0.10_for_mac. Is it normal? Shall I install it ?

Hervé

  • Hero Member
  • *****
  • Posts: 369
Re: New specialization plugin
« Reply #109 on: November 27, 2018, 13:07:42 PM »
Hi,

My apologies for this late answer, I've been very busy those last days ...

In fact, for a reason that I still do not understand, my plugin does not work well on MAC OS and I had to provide a specific version. I haven't had time to change the automatic update procedure about this file.

If you're on Windows, please do not install the MAC version. In the best scenario, it will work but on a worst case scenarion, you may have some unexpected behaviour.

I'll move the MAC version to a specific folder to avoid this in the future.

Thanks and regards
Hervé