Re: [MSEide-MSEgui-talk] property & keywords

2018-02-03 Thread code dz
i think so -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ mseide-msegui-talk mailing list mseide

Re: [MSEide-MSEgui-talk] property & keywords

2018-02-03 Thread Martin Schreiber
On 03.02.2018 09:57, code dz wrote: i think so MSEide does not treat "string" as a keyword but as a type. If you like to have "string" in bold add it to 'keyworddefs pascal' and 'keyworddefs property' in apps/ide/syntaxdefs/pascal.sdef. Martin ---

Re: [MSEide-MSEgui-talk] MSEcoupon ready for testing

2018-02-03 Thread code dz
now i hear a female voice . but the voice engine take long time to initialize , it makes the form freezing for about 5sec . but in the second run it works fast , i mean this happen only once per boot -- Check out the vibr

Re: [MSEide-MSEgui-talk] property & keywords

2018-02-03 Thread code dz
2018-02-03 9:17 UTC+01:00, Martin Schreiber : > On 03.02.2018 09:57, code dz wrote: >> i think so >> > MSEide does not treat "string" as a keyword but as a type. If you like > to have "string" in bold add it to 'keyworddefs pascal' and 'keyworddefs > property' in apps/ide/syntaxdefs/pascal.sdef. >

Re: [MSEide-MSEgui-talk] property & keywords

2018-02-03 Thread Martin Schreiber
i added it already , you can see the first screenshot , it looks bold in the declaration of fname field but the in the property type it apears without bold and that is the issue Add it to 'keyworddefs property' too. Martin

Re: [MSEide-MSEgui-talk] property & keywords

2018-02-03 Thread code dz
2018-02-03 10:17 UTC+01:00, Martin Schreiber : > > >> i added it already , you can see the first screenshot , it looks bold >> in the declaration of fname field but the in the property type it >> apears without bold and that is the issue > Add it to 'keyworddefs property' too. > > Martin > ah , i

Re: [MSEide-MSEgui-talk] MSEcoupon ready for testing

2018-02-03 Thread fredvs
> The demo is GPL, so it can use the eSpeakNG library. Huh, Martin,... you did not answer to the question... So, if I understand ok, the demo uses eSpeakNG-library directly, not via eSpeakNG-executable. If it is the case, do you have plan, like we did for sak, to also provide a " eSpeakNG-execu

Re: [MSEide-MSEgui-talk] MSEcoupon ready for testing

2018-02-03 Thread Martin Schreiber
On 03.02.2018 13:02, fredvs wrote: The demo is GPL, so it can use the eSpeakNG library. > > Huh, Martin,... you did not answer to the question... > > So, if I understand ok, the demo uses eSpeakNG-library directly, not > via eSpeakNG-executable. Correct. > If it is the case, do you have plan

Re: [MSEide-MSEgui-talk] MSEcoupon ready for testing

2018-02-03 Thread fredvs
> The eSpeakNG executable is not well suited for the purpose. What are you missing ? I did use also espeak library and did not find exported methods useful that executable can not manage. The only thing that I noted is that all was slower (yes, trust me), problems for user to install libraries a

Re: [MSEide-MSEgui-talk] MSEcoupon ready for testing

2018-02-03 Thread Martin Schreiber
On 03.02.2018 20:15, fredvs wrote: The eSpeakNG executable is not well suited for the purpose. What are you missing ? I did use also espeak library and did not find exported methods useful that executable can not manage. Starting a new process for every voice doesn't look optimal to me. Also

Re: [MSEide-MSEgui-talk] MSEcoupon ready for testing

2018-02-03 Thread fredvs
>> Also, using high definition of voice-synth (disponible when compiling the >> library) does not have any difference with the "standard" one. > I don't understand, please explain. There is a option at compiling to choose the audio driver. And if you choose portaudio, you may choose float reso

Re: [MSEide-MSEgui-talk] MSEcoupon ready for testing

2018-02-03 Thread Martin Schreiber
On 03.02.2018 21:21, Martin Schreiber wrote: Currently I am adding support for Windows waveOUT API instead of Xaudio2 to eSpeakNG which should simplify the dll problem a bit. It even sounds better because eSpeakNG Xaudio2 interface does not double buffer it seems. Done: " On Windows --