Hi Paul,
I started to test FF3 with PB10.
I get an error message with each project with a FireImage control; see the printscreen below.
PS: I get this message either with the PowerBASIC include files or with the latest include files from Jose ROCA.
I hope that we can find a workaround or a fix for that.
Kind regards,
Jean-Pierre
I remember Jose saying that api functions taking the pt type can now be passed simply as pt rather than pt.x and pt.y. I would have to modify the custom controls to fix that. Another reason why a FF4, PB10 only version is easier to deal with then trying to fit PB10 into the existing FF3.
See this post: http://www.planetsquires.com/protect/forum/index.php?topic=2752.msg21030#msg21030
Either change PtInRect(rc, pt.x, pt.y) to PtInRect(rc, pt). If using my new headers, you can also change it to PtInRectXY(rc, pt.x, pt.y).
Quote
Another reason why a FF4, PB10 only version is easier to deal with then trying to fit PB10 into the existing FF3.
Instead of losing your time moving declares around, you should pay attention to important things like making your application High DPI aware.
I recently purchased a 20" monitor with high resolution. The size of the text was so small that I had to increase the DPI to 175% to be able to read it comfortably. The result is that a lot of applications that are not DPI aware are almost unusable. With FF, the main problems are that it is very hard to build a form with controls using the mouse (the main purpose of a visual designer!) and that drag and drop of files does not work as it should (this problem is shared with any application that allows drag and drop and is not High DPI aware, including my editor).
Therefore, I have been forced to look closely at the problem and I have updated my CWindow class for PB10 to be both Unicode and High DPI aware and provided methods to create controls and fonts, resizing and moving windows, etc., that are High DPI aware. Now that bloat is no longer a problem thanks to dead code removal, it's better to use a wrapper class that straight SDK code.
You should also write the new FF using unicode. My new headers allow to work with Unicode transparently, so one only needs to get the habit of using WSTRINGs instead of STRINGs and WSTRINGZs instead of ASCIIZs. My new editor allows the use of WYSYWIG Unicode in comments and strings literals using UTF8 encoding (since the compiler is ansi).
Progress comes at a price!
I'd be happy to pre-order a copy ;D
Quote from: Jose Roca on March 29, 2011, 09:08:45 PMTherefore, I have been forced to look closely at the problem and I have updated my CWindow class for PB10 to be both Unicode and High DPI aware and provided methods to create controls and fonts, resizing and moving windows, etc., that are High DPI aware. Now that bloat is no longer a problem thanks to dead code removal, it's better to use a wrapper class that straight SDK code.
Jose, do you have an "easy way" to update your Editor or Headers, instead of having to search your forums?
I was hoping for some "auto update" in your Editor that would update the Editor *and* the Headers??
Thx! : )
I got a similar error in the rrbuttoninc_module.inc
string operand expected
If PtInRect(rc, pt.x, t.y) then
Marc