Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - LM

Pages: [1]

QB64 Discussion / Question regarding interacting with Excel files

« on: April 01, 2022, 05:55:42 pm »

I am wondering whether anyone has looked into interacting with Excel files (reading and/or writing), preferably in the .xlsx format but .ods (OpenDocument Spreadsheet) format would be useful too. I use CSV files a lot (readable and writable by Excel) but could really use a way to read and write directly to XLSX.

Has anyone tried this or does anyone have any suggestions or pointers to how it can be done? I would be happy if I could get as far as just reading and writing data to cells. Accessing formatting and graphs and such is not as important.

Thanks in advance for any input.

LM

QB64 Discussion / Any ideas on SHELL behavior (dir versus attrib)?

« on: March 29, 2021, 05:10:44 pm »

I don't understand why this won't work for me. Any ideas? I tried it on Windows 8.0 and 10, and I tried both QB64 v1.4 and 1.5. Here is my problem:

Shell "dir /s >textfile.txt" correctly produces "textfile.txt" like I expect.

Shell "attrib /s >textfile.txt" does not produce the expected "textfile.txt"

If I just run Shell from a QB64 program and manually type "attrib /s >textfile.txt", it does correctly produce the text file.

If I make a .bat file (e.g., "createtextfile.bat") containing "attrib /s >textfile.txt" and then do Shell "createtextfile.bat", then the "textfile.txt" is created.

Any ideas on why attrib won't work from within the QB64 program? Perhaps there is a more elegant way of getting a listing of all files in the current directory and its sub directories. I appreciate ideas on that too!

LM

QB64 Discussion / _SCREENIMAGE bug?

« on: March 22, 2021, 09:40:37 am »

I thought I'd throw this out there to see if anyone has any ideas.

Trying to do a screenshot using image& = _SCREENIMAGE. My screen is set to 1920x1080, but I only get a partial image of the screen. This is what I get:
_Width(image&) reports 1536 instead of 1920
_Height(image&) reports 864 instead of 1080

I am wondering if it could have to do with the font/text size zoom in Windows 10? I have the resolution at 1920x1080 but have the Windows font/text size set at 125%. 1920 /1.25 = 1536 and 1080 / 1.25 = 864. Not certain yet whether the text size is the issue as I have not had a chance to test my hypothesis. I need to keep the Windows text size at 125% while still being able to get a full screenshot.

What do people think? Any other ideas? If that is the issue, how can I get a full screenshot instead of a partial screenshot?

InForm Discussion / Inform editing question

« on: March 15, 2021, 09:42:47 pm »

I have a beginner's question about InForm. I am using v1.2 build 15.

I am ran InForm Designer (UiEditor.exe). I made a simple form with some labels and buttons. I then saved and exited to QB64. I wrote a few lines of code to respond to events (like mouse entering a control or mouse down on a control). I then found that I would like to add some additional controls to the form. I again went to the InForm Designer, loaded my form and added the controls. Here is my question: Is there a way to save the new form and use it with the code I already wrote without losing it? I did not immediately see how this is done. My edited form resulted in a new .bas file without the code I already wrote. Am I missing something? Do you have any recommendations?

Thanks!

LM

QB64 Discussion / Just saying hi and thanks!

« on: May 11, 2020, 11:05:59 pm »

I hope I am not posting in the wrong place. Mods: please move as needed.

I just discovered QB64 in the last week or so and I am amazed. I want to say thanks to all of you who have worked, and are working, so hard to keep QB alive and to expand it!

I started out with C64 BASIC and then got into BASICA/GWBASIC, then QBASIC, QB45, and VB5/VB6. Other than some simple games, most of my programs were designed to control scientific equipment, collect data from that equipment, to facilitate data interpretation, to solve specific problems, or to automate/simplify tedious tasks. QB45 was always my favorite. I have not done as much of this in recent years.

I recently had a problem that was perfect for a quick program and I found myself digging up QB45 and running it on an old computer that could still run it. Although I have learned some Python in recent years, QB45 was what immediately came to mind and what I effortlessly could apply to solve the problem. Being dismayed that QB45 would not easily run on a newer system, I began exploring alternatives and that is when I found QB64. The familiarity of the interface put a smile on my face! To immediately be able to apply the old skills is amazing and the new functionality is exciting!

Thank you for the hard work and dedication! You guys are amazing!

L