Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
The QB64 full screen editor
#4
I noticed in your "FINDDATA.BAS" file that you've also declared "FindFirstFileW" and "FindNextFileW". Were you planning on making a version that would enable usage of unicode (wide) strings?

Side note: You should change your declarations from UNSIGNED OFFSET to just OFFSET as an invalid handle return in Win32 API is a -1 but since you are currently casting them to UNSIGNED, you won't notice the failure unless you cast them back to a signed OFFSET. This would be your "FindFirstFileA/W" and "FindNextFileA/W" declarations. Typically, you'd only ever use an UNSIGNED OFFSET for a wParam in Win32.
I'd still change the UNSIGNED OFFSETs to OFFSET just for matching of the data types but it does look like INVALID_HANDLE_VALUE will be caught just fine.
Tread on those who tread on you

Reply


Messages In This Thread
The QB64 full screen editor - by eoredson - 08-29-2022, 05:08 AM
RE: The QB64 full screen editor - by mnrvovrfc - 08-29-2022, 09:53 PM
RE: The QB64 full screen editor - by eoredson - 08-30-2022, 03:39 AM
RE: The QB64 full screen editor - by SpriggsySpriggs - 08-31-2022, 01:59 PM
RE: The QB64 full screen editor - by eoredson - 08-31-2022, 11:52 PM
RE: The QB64 full screen editor - by krovit - 08-29-2023, 05:58 PM



Users browsing this thread: 1 Guest(s)