Re: [MSEide-MSEgui-talk] New release of MSEide.

> > Sorry I do not catch this, what are the coding line markers? OK, fixed in last commit: https://github.com/mse-org/mseide-msegui/commit/255207 Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing

Re: [MSEide-MSEgui-talk] New release of MSEide.

> Sorry I do not catch this, what are the coding line markers? Ha, ok, I get it, indeed the blue point is too big and in the wrong side. I will fix it asap. Thanks to note it. But now that you point it, there may be also a problem with the shortcut icon that is there too. Hum, ok, this need

Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello Sieghard. > The - now - big blue blobs appearing in the left hand "gutter" after ... Sorry but my English is not yet perfect and in this case I fear that only a picture could fresh my mind. Is it not possible to add a screenshot of what you want to describe? Thanks. Fre;D -- Sent

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

@ Med. I think there is problem with mse mailing list. Maybe better use mse-forum for continuing the discussion. http://mse-org.111682.n8.nabble.com/ Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

Hello Mohamed. Did you read my previous mail? I said that ok, it is my fault, it is me that has done the modifs. It was because of range error warning with the enum variable. It was long discussion about this in mse-mailing list and also fpc mailing-list. fpc enum warning

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

> Then Why do I have this AboutForm Form ( See attach.) . Huh yes indeed I dont really understand how Martin assigned the release number. In his source it was last release 4.6.2 and trunk 4.6.3. No sorry I do not understand why he used version 4.7 in about-form and 4.6.2 in source. Anyway,

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

> MseGui Version 4.6.3 Hu, last version from Martin was: Version 4.6.2 2018-11-03 ??? Please do like this to download last msegui source: Go to site: https://github.com/mse-org/mseide-msegui Then click on the green button at middle-top right "Clone or Download" and choose Download zip.

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

Re-hello Med. Now that I did recheck, there was lot of fixes in databases files. The most about enum variables. I did not test databases so it is great that you could test it. If you see other problems, please say it. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

> MseGui Version 4.6.3 Ha, ok, I see, you are used a trunk version so the version was 4.6.3. If so, I do not understand why you did not have the error with 4.6.3, but maybe you are using a old trunk 4.6.3, not the latest. The latest trunk 4.6.3 from

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

Hello Med. TDataSetState is defined in mdb.pas with this: TDataSetState = (dsInactive, dsBrowse, dsEdit, dsInsert, dsSetKey, dsCalcFields, dsFilter, dsNewValue, dsOldValue, dsCurValue, dsBlockRead, dsInternalCalc, dsOpening, dscheckfilter); So in your code is missing last élément

Re: [MSEide-MSEgui-talk] New release of MSEide.

Seems that previous mail did not pass... OK, I retry. Hello Med. TDataSetState is set in mdb.pas with this: TDataSetState = (dsInactive, dsBrowse, dsEdit, dsInsert, dsSetKey, dsCalcFields, dsFilter, dsNewValue, dsOldValue, dsCurValue, dsBlockRead, dsInternalCalc, dsOpening,

Re: [MSEide-MSEgui-talk] New release of MSEide.

> But it seems that it was fixed it you create a new program. No it was not fixed but it is fixed now with last commit: https://github.com/mse-org/mseide-msegui/commit/ff265a6 Thanks to note it. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello Graeme. You did the biggest part of that new release. Without your fixes it will never append. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net

Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello Sieghard. About color, yes I think it was a error in default code, warning should be yellow and error red. But it seems that it was fixed it you create a new program. Of course all old programs-demos have this inversion and it is not difficult to change it (mseide-config-editor-colors). A

Re: [MSEide-MSEgui-talk] Error compiling with 5.0

Hello Med. Please, give more code, how could I understand what is wrong? A little demo would be welcome. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list

Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello Sieghard. > I'll rebuild all of my "private" utilities Nice, it will be welcome. And dont forget to create a GitHub account! ;-) Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list

Re: [MSEide-MSEgui-talk] New release of MSEide.

Salut Roland. Thanks for the links and for the thanks. By the way, did you see that you are administrator of the mse-forum? http://mse-org.111682.n8.nabble.com/ Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___

Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello everybody. The mse-org team is very happy to announce the new release of MSEide+MSEgui. MSEide+MSEgui is a Pascal Cross Platform GUI Development System. - Compiles with FPC 2.6.4, 3.0.0, 3.0.2, 3.0.4 or 3.2.0. - For FreeBSD-x86_64, Linux-i386, Linux-x86_64, Linux-arm(Raspberry Pi),

Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello everybody. > Also, I propose to name the new release 5.0.0, (it seems that Martin > changed > the first number when a new fpc version was allowed). > And change, maybe, the copyright with: > Copyright (c) 1999-2020 by Martin Schreiber and friends. > OK ? I still wait for your green

Re: [MSEide-MSEgui-talk] New release of MSEide.

Hello Sieghard. > Isn't your latest version, adapted for fpc 3.3.1? Yes, yes, and of course also fpc 3.0.X and 3.2.0 compatible. > Yes. Do it, so people see that mseide is still alive! OK, I will do it. But there is a bémol, Martin did add 2 binaries for ARM cpu. Sadly I only have a

Re: [MSEide-MSEgui-talk] New release of MSEide.

-- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

[MSEide-MSEgui-talk] New release of MSEide.

Hello. Now that fpc 3.2.0 has been officially released: http://free-pascal-general.1045716.n5.nabble.com/FPC-3-2-0RC1-released-td5735128.html Maybe we could release also a new binary release of MSEide. The official last release is this:

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Sieghard. OK warning disabled for those 2 cases. I did use {$warnings off}/{$warnings on} vs {$warn 4110 off}. This to isolate the warnings off only for those 2 lines: {$warnings off} result:= (key <> 0) and (key <> word(not modmask)); {$warnings on} {$warnings off} foldlevelmask =

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Ooops, in previous mail, please read: (warning 4110 in place of warning 6060): About range check error: > > msedatalist.pas(891,18) Warning: (4110) Range check error while > > evaluating constants (-193 must be between 0 and 255) Many thanks for your explanations. It seems that the

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Seignard. > Yes I was thinking to do that but it is **lot of work**, +- 500 cases to > fix, sometimes in complicated code. It was terminated yesterday, after lot of cups of coffee, checking every case individually and following your advice: adding a last else statement + comment. > else;

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

The same for the last warning: Changing with this: modmask = abs(shift or ctrl or alt or $1000 or pad); ... result:= (key <> 0) and (key <> word((not modmask))); Gives the warning: mseactions.pas(763,34) Warning: (4110) Range check error while evaluating constants (-63489 must be between 0 and

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

What is very strange is that I get also a warning with this (see abs() added): const foldhiddenbit = 7; foldhiddenmask = abs(1 shl foldhiddenbit); currentfoldhiddenbit = 6; currentfoldhiddenmask = abs(1 shl currentfoldhiddenbit); foldlevelmask = byte(not (foldhiddenmask or

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> why not just replace byte with integer I just try it and with this you get 8 new warnings... -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Sorry I am a never-give-it-up... So, about those famous 2 last warnings: I propose this to make the compiler happy: - First warning: > msedatalist.pas(891,18) Warning: (4110) Range check error while evaluating > constants (-193 must be between 0 and 255) Point to: foldlevelmask =

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> OK,asap, first lots of cups of coffee and then I will jump into it. Top chrono! Done in commit 2da0695 following the Sieghard advises: Not using {$warn 6060 off} but fixed for real, adding this statement at end of case: else; // Case statment added to make compiler happy... Ok now

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> did you try compiling with fpc 3.0.4 with all these changes? Yes and did not find any problem. -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> yes , every things works fine so far ;) Yep, excellent news! So MSEgui will be fully compatible with last generation of ARM devices (that is what promised by FPC team). About trunk-warning fixes, it seems that there is not lot of candidate to do it. OK,asap, first lots of cups of coffee and

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Code DZ. Me too I was desperate, without to make MSEgui compatible with fpc trunk, sure MSEgui will disappear. But thanks to Sven (who knows maybe that I never give up) MSEgui is still on the road. Did you try to compile MSEide with fpc trunk, are layout problems all ok now? Fre;D --

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Re-re-hello Sieghard. > I propose to add a - possibly empty, but AT LEAST commented! - default > (else) clause. You are right. I will revert the last commit (that disabled the warning for many units) and re-commit the code with warning on. And if somebody want to do the fixes adding "else" in

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Re-hello Sieghard. > I propose to add a - possibly empty, but AT LEAST commented! - default > (else) clause. Yes I was thinking to do that but it is **lot of work**, +- 500 cases to fix, sometimes in complicated code. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Sieghard. I totally agree with you, sometimes the warnings helps. I can understand that in a case of the variable is part of the procedure, like this: procedure test; var b: 1..10; begin case b of // here warning 1: writeln('hello'); end end; Here I understand

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

With last fpc 3.3.1 trunk, there are warnings in case like this: procedure test; var b: 1..10; begin case b of // here warning 1: writeln('hello'); end end; " Warning: (6060) Case statement does not handle all possible cases." In MSEgui there is lot of code that is

Re: [MSEide-MSEgui-talk] New release of ideU with Code Beautifier ptop and Jedi.

Hello. Do you have download all the files from: https://github.com/fredvs/ideU Click on the green button "Clone or Download". Then unzip the file and load "ideu/src/ideU.prj" Also use the last version of msegui: https://github.com/mse-org/mseide-msegui Did you try the

Re: [MSEide-MSEgui-talk] New release of ideU with Code Beautifier ptop and Jedi.

Hello everybody. ideU goes theming! Added Silver and Carbon themes. <http://mseide-msegui-talk.13964.n8.nabble.com/file/t2/ide_silver.png> <http://mseide-msegui-talk.13964.n8.nabble.com/file/t2/ide_carbon.png> https://github.com/fredvs/ideU Fre;D -- Sent from: http://mseide

Re: [MSEide-MSEgui-talk] Compilation error with FPC 3.2.0

Hello everybody. I am extremely happy to announce that, thanks to Sven, the mse-stat-file bug with fpc 3.3.1 trunk is fixed. The fixes are in commit b7530e6. Tests are highly welcome, this with fpc 3.0.4, fpc 3.2.0 and fpc 3.3.1 trunk. I did test compiling mseide, ideU and others projects and

Re: [MSEide-MSEgui-talk] Procedure to create the configuration file of MSEide

And for the first msestat file, this is working too: [mainfo.mainstatfile] msedir=/home/fred/msegui A file with only those 2 lines is ok, mseide will fill automatically the missing lines. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] Procedure to create the configuration file of MSEide

I think you have to check in msesettings.pas -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Procedure to create the configuration file of MSEide

Re_hello Roland. Even better. For first time loading, only this is needed (not needed : [actionsmo.shortcuts] and others, it will be updated by meside himself after close.) So only this in mseideli.sta: [mainfo.mainstatfile] fpcdir= fpclibdir= msedir= // here to fill

Re: [MSEide-MSEgui-talk] Procedure to create the configuration file of MSEide

Re-hello Roland: Here a complete "virgo" mseideli.sta file. Only fields msedir=, compiler=, debugger=, exeext=, target=, targetosdir= and printcommand= should be filled by the installer. [[mainfo.mainstatfile] fpcdir= fpclibdir= msedir= mselibdir=${MSEDIR}lib/common/

Re: [MSEide-MSEgui-talk] Procedure to create the configuration file of MSEide

Hello Roland. Good news, it will be very easy, you will have to only change the 4th line of mseideli.sta This is mine: [mainfo.mainstatfile] fpcdir= fpclibdir= msedir=/home/fred/mseide-msegui/ // change msedir=/with/your/directory Fre;D -- Sent from:

Re: [MSEide-MSEgui-talk] Procedure to create the configuration file of MSEide

> The first time you run MSEide, the stat file is created, with the default > value assigned (most of them empty). In Linux, it is saved as mseideli.sta in .mseide (directory hidden) /home/you/.mseide/mseideli.sta In Windows is in (not sure) c:/users/fred/Application Data/.mseide/mseideli.sta

Re: [MSEide-MSEgui-talk] Procedure to create the configuration file of MSEide

Hello Roland > I would like to find the code that is used by MSEide to create the > configuration file. It done by a mse-stat file. The first time you run MSEide, the stat file is created, with the default value assigned (most of them empty). When you load the configuration form and change the

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Sieghard and others. Just by curiosity, do you have try the enum program example with Delphi ? Sadly I dont have delphi installed any more. Here the test program: PROGRAM enumtest; type tabulatorkindty = (tak_none := 1,tak_left,tak_right,tak_centered,tak_decimal); var kind:

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

> But most probabely they were preexisting, I presume? Yes, they were produced maybe by a build process but that build process is not part of mse (imho). > (or compare them with tha originals, or just > dump them and _use_ the originals), Yes, I did tests before to choose what to commit. And,

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

> Wouldn't it be simpler to just rebuild all binaries Not sure to understand. There is no applications-binaries or libraries-binary in mseide-msegui source. All the binaries are about images files, like bmp, png, jpeg, ... Rebuild the images? -- Sent from:

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> What a glaring omission, no? Yes. Also I am not totally convinced by the arguments to defend the choice of 0 as initialization of a enum var. Imho, it would be much more logic to initialize with the first item and I do not see what could be the problems. Here the answer in fpc mailing-list

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

> If you are COMPLETELY SURE that NOT A SINGLE FILE of them all is a binary No, I am not completely sure. It is the reason why, before to apply the patch, I did copy the directories containing binaries and git files in safe place. (Imho, only images and git files are concerned). Then apply the

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> To resume, a enum variable is initialized with the first item of the enum. Fake news, this is true: To resume, a enum variable is initialized with 0. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

> OK, done in 2 last commits. > I hope I did not a disaster. I did use that command (after done a copy of .git and images files): $ find . -type f -name '*.*' -exec sed --in-place 's/[[:space:]]\+$//' {} \+ After that command, I did paste the original copied .git and images files. Fre;D

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

OK, done in 2 last commits. I hope I did not a disaster. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello. An interesting post here: http://free-pascal-general.1045716.n5.nabble.com/Re-New-Warnings-with-fpc-gt-3-2-0-fredvs-td5735027.html To resume, a enum variable is initialized with the first item of the enum list. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Sieghard. > Have a lot of fun! With your code I get this: $ /home/fred/weird/weirdtest low: we_2, value: 2; high: we_decade, value: 20 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 we_2: 2Runtime error 107 at $00401293 $00401293 $0040104F

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

> You are green to go! :-) Aargh, it does not work this time. OK. (but asap). Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

Hello Sieghard. > Do you use Windows (a manualizing tool) or Linux (an automating tool)? I use Linux. > "sed -i 's/[[:blank:]]*$//' " Thanks for the tip! Maybe Graeme is already busy with it. Anyway, I will use the magic words (that works very well with Graeme): "Graeme, if you want, I

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Sieghard. > Why could that drive someone crazy, ? Huh, I was talking about all the possibilities that enum gives and the difficult task to choose the best one. The "new illegal-nil-none item" in the enum can be placed everywhere but imho at end will give shorter code and so less chance to

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

> I suggest,if you want, apply it to ALL the source code in the repo and make one > commit that says trimming the whitespace. Done and dusted! ;-) Ho, yes, it would be wonderful. But... Mse has **many** units, doing this via a editor will takes ages... Fre;D -- Sent from:

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> if not fixed. Yes, as written in a previous mail, I let, for the sport, 2 Warnings to fix. This is the first, the second is not bad too. ;-) Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing

Re: [MSEide-MSEgui-talk] Space and empty lines removed in commits.

Hello Graeme. > change a editor setting (eg: trim trailing whitespace)? Yes, my fault, now I see that it was absolutely not a good idea. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

> scrollbarclicked = ord(sba_end) + 1; // not a "good boy" code. Imho, it is not a "good boy" code because later there is: ---> if kind = scrollbarareaty(scrollbarclicked) then // this gives a warning with fpc 3.2.0, not fpc 3.0.4. OK, I stop before to become (stay) completely crazy. Fre;D

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

>Sorry I dont find now the code that demonstrate that it was easier if > "sba_none" was placed at end. OK, I found it. This was a original code (see scrollbarclicked new added constant): type scrollbarareaty = (sbbu_down,sbbu_move,sbbu_up,sba_start,sba_end); const scrollbarclicked =

[MSEide-MSEgui-talk] Space and empty lines removed in commits.

Hello. When I check my last commits, doing a "diff", shows also all the spaces end empty lines removed. That makes the read of the change much more complicated, I would prefer that only the change in code was show. I know that there is a option in Git to ignore the change done for space and

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Sorry to monopolize. But re-re ooops. In previous mail, when I did try to explain why I opted to place the new "sba_none" at end, I did choose a wrong example. Of course the order of enum has no influence on bu1:= low(scrollbarareaty) to high(scrollbarareaty). But, (trust me), it was more easy

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Re-ooops. In previous mail: >Take this original example: >scrollbarareaty = >(sbbu_down,sbbu_move,sbbu_up,sba_start,sba_end,sba_clicked,sba_none) Please read (forget sba_clicked,sba_none): Take this original example: scrollbarareaty = (sbbu_down,sbbu_move,sbbu_up,sba_start,sba_end) Fre;D

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Oops, in previous mail: >Take this original example: >scrollbarareaty = >(sbbu_down,sbbu_move,sbbu_up,sba_start,sba_end,sba_clicked,sba_none) Please read (forget sba_none): Take this original example: scrollbarareaty = (sbbu_down,sbbu_move,sbbu_up,sba_start,sba_end,sba_clicked) Fre;D --

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Sieghard **Many thanks** for all that clear explanation. > BTW, I'd suggest to use the word "illegal" Ha, ok, in last commit I did use "none" or "nil", I will change it asap. > tabulatorkindty = (tak_illegal:= -1, tak_left, tak_right, > tak_centered,tak_decimal); Like explained to

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Roland. > but I am sure that"tabulatorkindty(tak_nil)" can be replaced with > "tak_nil". ;-) OK, done in last commit b7be824. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Roland. Sorry, I did commit some change following the advises of fpc-mailing list: https://github.com/mse-org/mseide-msegui/commit/ Of course it can be changed but is is to make advance the "schmilblick". It takes the same idea as yours, the only thing changed is that tak_nil is placed

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Code DZ and all others. > so i think this list should be extended Maybe. But after the conversation in: http://free-pascal-general.1045716.n5.nabble.com/New-Warnings-with-fpc-gt-3-2-0-td5734996.html Maybe also some code should be fixed with the "good boy" way. So the question is:

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

Hello Graeme. I did fix for the warnings in commit 5aa6640. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list mseide-msegui-talk@lists.sourceforge.net

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello. I did create a new topic about this in fpc mailing-list: http://free-pascal-general.1045716.n5.nabble.com/New-Warnings-with-fpc-gt-3-2-0-td5734996.html Maybe some light from there... Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Seighard. Here a example maybe more clear: msedrawtext.pas(1115,48) Warning: range check error while evaluating constants (-1 must be between 0 and 3) This warning point to: ---> if (kind <> tabulatorkindty(-1)) and tabulatorkindty is declared as: ---> tabulatorkindty =

Re: [MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello Roland. Doing this: const foldhiddenbit = 7; foldhiddenmask = byte(1) shl foldhiddenbit; currentfoldhiddenbit = 6; currentfoldhiddenmask = byte(1) shl currentfoldhiddenbit; foldlevelmask = byte(not (foldhiddenmask or currentfoldhiddenmask)); foldissumbit = 0; foldissummask = $01;

[MSEide-MSEgui-talk] About Warnings with mseide + fpc 3.0.4 / 3.2.0

Hello everybody. I think that the proposition of Code DZ is a "must be done" (first of all, fix the Warnings at compilation using fpc 3.0.4). Here are all the warnings while compiling mseide with fpc 3.0.4. You may see that all the warnings are about string type conversion in

Re: [MSEide-MSEgui-talk] msedbusinterface and fpc 3.3.1 trunk

Hello Seighard. Thanks for that clear explanations. By the way, I did check in all the msegui sources if there was, by bad chance, a other case with omitted parenthesis in "is" operator combined with "and". In all the code written by Martin, when "is" is used with "and", the parenthesis are

Re: [MSEide-MSEgui-talk] msedbusinterface and fpc 3.3.1 trunk

Re-hello Code DZ. > I tried fixing these warning but i lost . What makes you stop, what kind of warnings? Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list

Re: [MSEide-MSEgui-talk] msedbusinterface and fpc 3.3.1 trunk

Hello Code dz > i think msegui should stay with fpc3.0.4 until finding the fix Yes, of course, fpc 3.0.4 is the "official" last release of fpc. I do regularly check the new features of fpc 3.3.1 trunk, this to not be too far of what appends. (And I agree also to check if ,by chance, they fixed

Re: [MSEide-MSEgui-talk] msedbusinterface and fpc 3.3.1 trunk

Hello Sieghard. > I'd rather suggest parentheizing the first partial expression, like so: > if (fld1 is tblobfield) and (self.fblobintf <> nil) then begin Yes, it is exactly what was proposed in fpc mailing list. It is also what I did commit in mse-org/mseide_msegui

Re: [MSEide-MSEgui-talk] msedbusinterface and fpc 3.3.1 trunk

Hello. With my fpc friends, we fixed the problem: fpc-topic So, it was committed in

Re: [MSEide-MSEgui-talk] msedbusinterface and fpc 3.3.1 trunk

Re-hello. OK, I did apply the Graemes's fix: adding {$interfaces corba}, just after unit msedbusinterface. This fixes the error: "Error: The interface type of the forward declaration and the declared interface type do not match for interface idbusservice " Nice but now there is a new other

[MSEide-MSEgui-talk] msedbusinterface and fpc 3.3.1 trunk

Hello. I just have try to compile mseide with last fpc trunk 3.3.1 of 08-03-2020. There is that error message: msedbusinterface.pas(224,5) Error: The interface type of the forward declaration and the declared interface type do not match for interface idbusservice msedbusinterface.pas(564,1)

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

Glad you like it! In last commit was added focusedlinecolor. This is the color of the focused line-fixed column (high-light fixed row where is the carret). Of course if you dont like this feature, just set the color as cl_default. So, to resume, there is now 8 color values. editorcolors =

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

Hello Graeme. Sorry, I could not resist. It is done, and was very easy. 3 new parameters are added in msesyntaxpainter : [fontlinecolor [backgroundlinecolor [selectedcolor So now in the sdef file, for example for your pascal_solarized_dark.sdef, the code is this: # COLORS

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

> And to complete all the look that sdef can give, maybe add also a parameter > for the color of the first row. > (The one that contain the line number). grid.fixcols[-1].color := cl_yourcolor; Ok, I go. Have a perfect and polychrome WE. Fre;D -- Sent from:

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

And to complete all the look that sdef can give, maybe add also a parameter for the color of the first row. (The one that contain the line number). Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

> f the sdef definition/implementation doesn't currently support that color item, Imho, after fast check, it is not currently supported. OK, I let you play with it. ;) Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

>This will be added in ideU as extra-option : color of focused row and maybe > other color-custom that are missing. Or better, re-code syntax def file (.sdef) file to add a parameter to set the color of datacols[1].colorselected. Fre;D -- Sent from:

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

Hello Graeme. If you want to change it hard-coded, it is in sourcepage.pas, with Object Inspector on grid, change the color of datacols[1].colorselected := cl_yourcolor. see picture:

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

>I tried that, but it had horrible results on my side, with my color > scheme. See attached screenshots and the file name explaining what you > see. Ha, you did choose nearly the same color for font than the color of the row focused. So in the syntax definition file it should have also a

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

Hello Graeme. Many thanks! There is a very little problem in tprocedurelistfo.JumpToSelectedLine; The line jumped is 1 line too much. Also may I propose to change the color of the line jumped, so it is more easy to see. Here the code: procedure tprocedurelistfo.JumpToSelectedLine; var int1:

Re: [MSEide-MSEgui-talk] The evil that is mfm

> Where do you see "Touch form"? Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/ ___ mseide-msegui-talk mailing list

Re: [MSEide-MSEgui-talk] The evil that is mfm

Hello. In /mseide-msegui/tools/ there is form2pas.pas application. It says: program form2pas; //convert form files (*.mfm) to pascal files (*_mfm.pas) //commandline: form2pas FORMFILE[,UNITNAME] ... //Default UNITNAME is FORMFILE without extension. // //'form2pas main.mfm formdesigner.mfm' ->

Re: [MSEide-MSEgui-talk] The evil that is mfm

> Right click on a file in the file list (right > side of editor window) and click on "Show as form" This is enabled only if the 3 files are present. The same for "Touch form", if a .mfm or _mfm.pas is missing. By the way, do you know what is the goal of "Touch form" ? Fre;D -- Sent from:

Re: [MSEide-MSEgui-talk] The evil that is mfm

Hello Graeme. Indisputably one of the best feature of fpGUI is his "all in one" file feature. Imho, the 3 files way is more heavy and if, by chance, you could find a way to unify all that files, I vote X 10.000 for it. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

Hello Graeme. It was the only feature from Geany that was missing. And works very well. I did add a 2xclik in mouse event the ideU version, for those that have a broken keyboard. Hum, in your code: procedure tprocedurelistfo.AddProcedure(...) ... case Language of ltPas: ... ltCpp:

Re: [MSEide-MSEgui-talk] Procedure List add-on for MSEide

Re-hello Graeme. It works **very** well. I could not resist too to commit it to ideU. Many wow and many thanks. Fre;D -- Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/

<    1   2   3   4   5   6   7   8   9   10   >