Page 1 of 1

Bug in SciLexer

Posted: 18 Feb 2020 13:42
by Vitaly Markov
The deleting HorScrollBar from SciLexer
Image
invoke exception:
===== 2020-02-18 16:40:00 =======================


----------------------------------------
Single fact has no value

error code = 329
ExtraInfo = Single fact 'native' from internal database 'sciLexer::sciLexer@objectDB' has no value

singleFactHasNoValue (runtime_exception)
runtime_exception::runtimeExceptionRaiser
pfc\exception\runtime_exception.pro(21,65)
----------------------------------------
D:\Исходники VIP8\editor16\Exe\editor16.exe (0x004EF325)
D:\Исходники VIP8\editor16\Exe\vipKernel.dll (0x59AD39F9)
D:\Исходники VIP8\editor16\Exe\vipRun.dll (0x592CAD8F)
D:\Исходники VIP8\editor16\Exe\editor16.exe (0x004EF325)
mainform\mainform.pro(57)
mainform\mainform.pro(12)
mainform\mainform.pro(7)
main.pro(8)
d:\program files\visual prolog 8\pfc\windowsapi\exe_api\exe_api.pro(57)
d:\program files\visual prolog 8\pfc\application\exe\mainexe.pro(33)
d:\program files\visual prolog 8\pfc\application\exe\mainexe.pro(20)
d:\program files\visual prolog 8\pfc\gui\formwindow.pro(481)
main.pro(13)
D:\Исходники VIP8\editor16\Exe\vipKernel.dll (0x59AD9144)
D:\Исходники VIP8\editor16\Exe\vipKernel.dll (0x59AD94CD)
D:\Исходники VIP8\editor16\Exe\editor16.exe (0x00559797)
C:\Windows\SYSTEM32\ntdll.dll (0x77EB607D)
C:\Windows\SYSTEM32\ntdll.dll (0x77EB604D)
OS: Windows 10.0 Build 17763 64-bit
My project contains automatically created code only.

Re: Bug in SciLexer

Posted: 19 Feb 2020 16:05
by Thomas Linder Puls
Unfortunately, most of these properties cannot be set like that, because the control does not exist at that place. Currently there is no other way to solve that problem than setting the property manually in a show listener:

Code: Select all

clauses     new(Parent) :-         formWindow::new(Parent),         generatedInitialize(),         addShowListener(             {  :-                 sciLexer_ctl:hScrollbar := false,                 sciLexer_ctl:extraAscent := 12             }),         ...
I will see if we can find a solution to this for the future.

Re: Bug in SciLexer

Posted: 20 Feb 2020 8:12
by Vitaly Markov
Thanks you Thomas!