PlanetSquires Forums

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1] 2 3 ... 10
 1 
 on: July 22, 2019, 10:51:10 PM 
Started by mysterydip - Last post by mysterydip
Ah, that makes sense. I was trying in areas without other controls. That seems a decent compromise. Thanks!

 2 
 on: July 22, 2019, 06:59:32 AM 
Started by mysterydip - Last post by Paul Squires
The way that it should work is that as you move a control around on a form, alignment lines should appear as it approaches the top/sides of adjacent controls. When you get really close to the control then it should snap to that control's position. It seems to work okay in most cases.

 3 
 on: July 21, 2019, 08:54:29 PM 
Started by mysterydip - Last post by mysterydip
I did see that and it is enabled, but I wasn't sure how to make use of it. I'll do some more digging/examples, thanks!

 4 
 on: July 21, 2019, 05:56:10 PM 
Started by mysterydip - Last post by Paul Squires
WinFBE does not have snap to grid. It has a snap to line type of system. Under the "Designer" top menu, just make sure that "Enable SnapLines" is checked. It works okay but can be a bit finicky if many controls are very close together. I will work on cleaning up that logic once the other visual designer elements are completed.

 5 
 on: July 21, 2019, 02:57:30 PM 
Started by mysterydip - Last post by mysterydip
Hi there,

New to FreeBasic and WinFBE, but have been using various flavors since I had a cartridge of BASIC on an IBM PCjr. This is probably just something I missed in the UI but wasn't able to find it and didn't see anything on the forum (which leads me again to think I'm missing something obvious). In VB6, the forms have a grid of dots that by default things snap to, which you can then edit their exact positioning after placement. Is there some equivalent here? I like to have everything line up as I freehand move things around and resize. If there is, is there also a way to set the size of that grid?

Thanks!
Keith

 6 
 on: July 17, 2019, 08:05:37 PM 
Started by SeaVipe - Last post by SeaVipe
Works! Thanks Josť,


I tried (almost) that code previously but got an error because I didn't use PTR correctly.

 7 
 on: July 17, 2019, 07:57:27 PM 
Started by SeaVipe - Last post by Josť Roca
Use lpNmh = CAST(NMHDR PTR, lParam)

 8 
 on: July 17, 2019, 07:42:07 PM 
Started by SeaVipe - Last post by SeaVipe
Hello,


I can't get rid of the compiler warning "Suspicious Pointer Assignment" generated by the code below:


Code: [Select]

Function FRMTASKEDITOR_CUSTOM ( _
                              hWndForm      as HWnd, _      ' handle of Form
                              wMsg          as UInteger,  _  ' type of message
                              wParam        as WPARAM, _    ' first message parameter
                              lParam        as LPARAM   _   ' second message parameter
                              ) as Long
    Select Case wMsg
        Case WM_NOTIFY
            Dim lpNmh  as NMHDR Ptr
            lpNmh => lParam ' <- Suspicious Pointer assignment warning.
            ' or
            lpNmh = lParam ' <- Suspicious Pointer assignment warning.


The code works correctly but the warnings are there regardless of what I try. Researched on FB forum also.
Using this line as an example resulted in a syntax error:
Code: [Select]
LPWSTR = Cptr(LPWSTR, RT_RCDATA)
Any ideas would be helpful, thanks...
Clive

 9 
 on: July 16, 2019, 03:05:40 PM 
Started by SeaVipe - Last post by SeaVipe
Thank you, David, Jean-Pierre's code works great; just what I was looking for!


Clive

 10 
 on: July 16, 2019, 03:02:21 PM 
Started by Jean-pierre Leroy - Last post by SeaVipe
Thank you, Jean-Pierre!

Pages: [1] 2 3 ... 10