Re: [Lazarus] New debugger for Mac based on lldb (Call for testers)

2018-10-16 Thread Martin Frb via Lazarus

On 16/10/2018 23:23, C Western via Lazarus wrote:

On 14/10/2018 20:09, Martin Frb via Lazarus wrote:


- Go to Tools > Options > Debugger
  In the "debugger type" dropdown, you should find and select "LLDB 
debugger (with fpdebug)"
  The edit below this (where you normally have the path to gdb), 
should be changed to the path of lldb.
  (lldb comes with the tools from apple; and as such it is already 
codesigned by apple).


Did you mean the option "(with fpdebug)"? Trying with this option 
lazarus throws an exception trying to open a .o file that exists - I 
can't immediately see why it is throwing the exception. It doesn't 
seem to reach the stage of starting the program. If I try it without, 
the debugger seems to be working OK, at least at first glance.


Depending on which of the LazDebugger...LLDB package(s) you installed, 
you should have one or two entries:

  "LLDB Debugger (Alpha)"
  "LLDB Debugger (with fpdebug) (Alpha)"

The 2nd one should be the better one.
The first (without fpdebug), will accept/display watches in C style 
only, and has had way less testing.


If you get an error, please provide the stacktrace (if you have), 
together with console output, and logfile.


Please also test with and without "external debug info".
When using (or having used) external dbg info, ensure that the folder 
with the debug info is not left behind/outdated (IIRC a folder with psym 
in the name)


I tested this on a Mac, that I had on loan. Currently I do not have a 
Mac for testing.


---
What you mean by "without, the debugger"
Without any debugger, or with the lldb without fpdebug?

--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] New debugger for Mac based on lldb (Call for testers)

2018-10-16 Thread C Western via Lazarus

On 14/10/2018 20:09, Martin Frb via Lazarus wrote:


- Go to Tools > Options > Debugger
  In the "debugger type" dropdown, you should find and select "LLDB 
debugger (with fpdebug)"
  The edit below this (where you normally have the path to gdb), 
should be changed to the path of lldb.
  (lldb comes with the tools from apple; and as such it is already 
codesigned by apple).


Did you mean the option "(with fpdebug)"? Trying with this option 
lazarus throws an exception trying to open a .o file that exists - I 
can't immediately see why it is throwing the exception. It doesn't seem 
to reach the stage of starting the program. If I try it without, the 
debugger seems to be working OK, at least at first glance.


Colin

--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Forms.pp function error?

2018-10-16 Thread Dmitry Boyarintsev via Lazarus
On Tue, Oct 16, 2018 at 1:29 PM AlexeyT via Lazarus <
lazarus@lists.lazarus-ide.org> wrote:

> Value $400 makes sense.
> And also this must be changed then:
> function KeysToShiftState(Keys: PtrUInt): TShiftState;
> it uses same constants.
>

The value you're looking for is $2000
It's being used/supported by all current widgetsets
-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Forms.pp function error?

2018-10-16 Thread AlexeyT via Lazarus

Value $400 makes sense.
And also this must be changed then:
function KeysToShiftState(Keys: PtrUInt): TShiftState;
it uses same constants.

Alex
--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Forms.pp function error?

2018-10-16 Thread Michael Van Canneyt via Lazarus



On Tue, 16 Oct 2018, AlexeyT via Lazarus wrote:



On 16.10.2018 09:56, Michael Van Canneyt via Lazarus wrote:

There does not need to be if there is no corresponding MK_nnn value ?
What would be the MK_nnn value for ssAlt ? 


We can  add in, LCLType.pp:

const
  // Mouse message key states
  MK_LBUTTON  = 1;
  MK_RBUTTON = 2;
  MK_SHIFT = 4;
  MK_CONTROL = 8;
  MK_MBUTTON = $10;
  MK_XBUTTON1 = $20;
  MK_XBUTTON2 = $40;
  // following are "virtual" key states
  MK_DOUBLECLICK = $80;
  MK_TRIPLECLICK = $100;
  MK_QUADCLICK = $200;


I understand that, but what additional value makes sense ?

Michael.-- 
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus


Re: [Lazarus] Forms.pp function error?

2018-10-16 Thread AlexeyT via Lazarus


On 16.10.2018 09:56, Michael Van Canneyt via Lazarus wrote:

There does not need to be if there is no corresponding MK_nnn value ?
What would be the MK_nnn value for ssAlt ? 


We can  add in, LCLType.pp:

const
  // Mouse message key states
  MK_LBUTTON  = 1;
  MK_RBUTTON = 2;
  MK_SHIFT = 4;
  MK_CONTROL = 8;
  MK_MBUTTON = $10;
  MK_XBUTTON1 = $20;
  MK_XBUTTON2 = $40;
  // following are "virtual" key states
  MK_DOUBLECLICK = $80;
  MK_TRIPLECLICK = $100;
  MK_QUADCLICK = $200;

--

Regards,
Alexey

--
___
Lazarus mailing list
Lazarus@lists.lazarus-ide.org
https://lists.lazarus-ide.org/listinfo/lazarus