Recent

Recent Posts

Pages: [1] 2 3 ... 10
1
General / Re: Colore celle StringGrid
« Last post by JuanBell on Today at 10:37:56 pm »
Grazie di tutto thanks for everything
2
Debugger / Re: FpDebug likely bug
« Last post by 440bx on Today at 10:12:59 pm »
Created issues:

40922 https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/40922

and

40923 https://gitlab.com/freepascal.org/lazarus/lazarus/-/issues/40923
3
Networking and Web Programming / Re: Any upgrades to fpWeb page components?
« Last post by verasan on Today at 10:11:46 pm »
I would be happy for real documentation from developer team
4
Debugger / Re: FpDebug likely bug
« Last post by Martin_fr on Today at 09:48:34 pm »
Yes, TurboPowerIpProDsgn is installed by default, but you can uninstall it. Hence, you can build an IDE with grey hints. But that is not the issue here.

Yes, it should be reported as a bug. It should be reported as a bug against codetools. (as the & breaks more than just the hint).

"Codetool breaks on "&" in front of identifier (hint, source link, completion)"


I would say, there is a 2nd bug (though I am not 100% sure, could be missing feature).

If you go to Tools > Options > Editor > Completion and Hints: "Show declaration hints" and switch this off (this switches off the codetool hint).
But leave the "Show value hints while debugging" on.

Then the debug hint will always be grey.

It can be reported as "Source Editor hints not using yellow TurboPowerIPro hint for non-codetool hint"

Both can be reported using my example source, and the latter with reference to the settings above.
5
General / Re: Colore celle StringGrid
« Last post by Lutz Mändle on Today at 09:45:10 pm »
Use the OnPrepareCanvas event of the stringgrid for coloring the cells, for example like this:

Code: Pascal  [Select][+][-]
  1. procedure TForm1.StringGrid1PrepareCanvas(Sender: TObject; aCol,
  2.   aRow: Integer; aState: TGridDrawState);
  3. begin
  4.   if (ACol > 0) and (ARow > 0) then
  5.     if Odd(aCol) then
  6.       TStringGrid(Sender).Canvas.Brush.Color := clGreen
  7.     else
  8.       TStringGrid(Sender).Canvas.Brush.Color := clRed;
  9. end;
  10.  
6
General / Re: Colore celle StringGrid
« Last post by qk on Today at 09:34:32 pm »
Se non hai dimistichezza con l'inglese aggiungi comunque una copia
del tuo messaggio tradotta anche con google translator.
In questo modo il messaggio sarà comprensibile a tutti e più persone potranno aiutarti.

Sotto un semplice esempio di come colorare le colonne dispari.

Google translator:
If you don't speak English well, still add a copy of your message
translated with Google translator. This way, the message will be
understandable to everyone, and more people can help you.

Below is a simple example of how to color the odd columns.

Code: Pascal  [Select][+][-]
  1. procedure TForm1.StringGrid1DrawCell(Sender: TObject; aCol, aRow: Integer;
  2.   aRect: TRect; aState: TGridDrawState);
  3. begin
  4.   if (ACol > 0) and (ARow > 0) then
  5.     with Sender as TStringGrid do
  6.     begin
  7.       if Odd(ACol) then
  8.       begin
  9.         Canvas.Brush.Color := clGreen;
  10.         Canvas.FillRect(aRect);
  11.         Canvas.TextOut(aRect.Left + 2, ARect.Top + 2, Cells[ACol, ARow]);
  12.       end else
  13.       begin
  14.         Canvas.Brush.Color := clRed;
  15.         Canvas.FillRect(aRect);
  16.         Canvas.TextOut(aRect.Left + 2, ARect.Top + 2, Cells[ACol, ARow]);
  17.       end;
  18.     end;
  19. end;


   
7
Debugger / Re: FpDebug likely bug
« Last post by 440bx on Today at 09:30:18 pm »
Quote from: Martin_fr on Today at 09:10:31 pm
First of all, it would be an editor bug.

The debugger (any of them) only delivers the content of the window (as text), but nothing else.
I stand corrected.  I thought it might be FpDebug related because I was debugging and the value being shown had to come from the debugger but, I can see how the debugger may not have anything to do with the location and color of the window.

Quote from: Martin_fr on Today at 09:10:31 pm
The yellow hint is created using IpTurboProDsg package => so if uninstalled, the grey hint is used. Yet, then all hints would be grey.
There are no "user-installed" packages in this installation.  IOW, this installation is as-is "out of the box".  I've seen the color difference other times, I don't know if in this case the "&" had something to do with it but, I've had other occasions where the window was unexpectedly grey instead of yellow and there were no variables nor fields involving an "&".  Should the occasional difference in color be reported as a bug ?

Quote from: Martin_fr on Today at 09:10:31 pm
On Windows, if you have more than one screen, and they have different DPI settings, and a window on one screen is focused, but the mouse hovers over a window on another screen, the wrong dpi is used to calculate the hint offset. => Btw, such DPI mixes even affect apps like the windows explorer, to have incorrect display in some cases...)
This installation is in a VM with a single monitor.  IOW, I don't think different DPIs have something to do with the location of the window.

Quote from: Martin_fr on Today at 09:10:31 pm
So, at this time, I say this is primarily a codetools bug, but there may be additional issues in the hint handling code...
Ultimately that's what matters, should any of this be reported as a bug, what part should be considered a bug and, lastly against what ?

I'll create a ticket if one is warranted.
8
Debugger / Re: FpDebug likely bug
« Last post by Martin_fr on Today at 09:10:31 pm »
First of all, it would be an editor bug.

The debugger (any of them) only delivers the content of the window (as text), but nothing else.

The yellow hint is created using IpTurboProDsg package => so if uninstalled, the grey hint is used. Yet, then all hints would be grey.

Probably not applying to your case either (as it looks like the source editor has focus / the very editor to which the hint belongs). On Windows, if you have more than one screen, and they have different DPI settings, and a window on one screen is focused, but the mouse hovers over a window on another screen, the wrong dpi is used to calculate the hint offset. => Btw, such DPI mixes even affect apps like the windows explorer, to have incorrect display in some cases...)

As for the position, I have no idea, but maybe it is a side effect of the below (if the below applies....)

The yellow hint is a html hint. I am not aware of any issue like the following, but it would not be impossible.... The content of the hint, might be such that it breaks the processing into html. If such breakage could happen (which I don't know), then I don't know if there would be a fallback to the grey hint....
For starters the "&" may have suddenly meaning or side effect...

Actually, after typing the above, I just made the test.
Code: Pascal  [Select][+][-]
  1. program Project1;
  2. var
  3. &a:integer;
  4. begin
  5.   &a := 123;
  6.   a := 123
  7. end.

Hovering the "a" is fine. but the "&a" is not.

Further this may even be a codetool bug => explaining why the hint has no other content (e.g. no position of declaration).
In the above code example, while NOT debugging, I can hover the "a" and get some info, but not on the "&a" (neither of the two).

And the same goes for ctrl click jump attempts.

So, at this time, I say this is primarily a codetools bug, but there may be additional issues in the hint handling code...
9
General / Re: Web Applications with Pascal
« Last post by Handoko on Today at 08:56:29 pm »
@Nate897

If you're good in Pascal, you may want to try using FPC to build web services. If you're not good in Pascal, there are many other options available. If you like it, use it. If it works for you, keep using it.

If you want to try and learn more, here:
https://wiki.lazarus.freepascal.org/fcl-web
https://www.getlazarus.org/learn/tutorials/examples/webserver/
https://wiki.lazarus.freepascal.org/fpWeb_Tutorial

This is support forum for answering questions for users who have problem using Pascal. I wonder what kind of discussion you want to get.

Moderators, please lock this discussion or better delete it. This kind of discussion will start flames of war.
10
Third party / Re: AI, NLP and CAI: Text Generation with Convolutional Neural Networks in Pascal
« Last post by indydev on Today at 08:54:00 pm »
After looking into it. It looks like OpenAI removed the assistant sharing quite some time ago. Probably because the API is tied to accounts and thus charges would be applied to the Assistant owner.
Pages: [1] 2 3 ... 10

TinyPortal © 2005-2018