Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[José Roca]

> If I document as I develop then the task won't be so difficult than if I waited until the development was complete.

This is what I always do. The help for WinFBX has about 4,200 entries. Imagine that I had to write all of them at once.

[Paul Squires]

4,200 entries   That's a lot of work!

I have to say though that using Markdown language (and Typora or a regular text editor) is really easy and I find less formatting issues than using a dedicated HTML Help editor. Just a couple of problems with pdf output and tables bumping to second page when it should not.

I have uploaded new code and docs to github.
 

[SeaVipe]

Maybe a Quick Start note just to be on the safe side.
Perhaps user selectable colouring for such items?

Thanks.
Similar in syntax to a Metacommand?
'$Include - Alternate form of the #include directive.
'$Dynamic - Alternate form of the Option Dynamic statement.
'$Static - Alternate form of the Option Static statement.
'$Lang - Alternate form of the #lang directive.

Yes, that's basically correct. I could have called it anything but chose to use '#RESOURCE. Hopefully that doesn't become confusing to users.

[Paul Squires]

To be honest, in most cases a WinFormsX application will be created using a visual designer through a WinFBE project. When part of a WinFBE project, the resource will be identified as such and will be automatically part of the project compile. There would be zero need for the directive in those cases.

In the short one file examples that I have posted to test WinFormsX features, I use the directive in order to make compiling a little easier (not having to add it to WinFBE's compiler options). It also saves me from having to create a formal project for every code example.

[SeaVipe]

To be honest, in most cases a WinFormsX application will be created using a visual designer through a WinFBE project. When part of a WinFBE project, the resource will be identified as such and will be automatically part of the project compile. There would be zero need for the directive in those cases.

In the short one file examples that I have posted to test WinFormsX features, I use the directive in order to make compiling a little easier (not having to add it to WinFBE's compiler options). It also saves me from having to create a formal project for every code example.

Understood. Thanks for the explanation. Looking forward to the Visual Designer beta...

[Paul Squires]

Cleaned up some statusbar code, added new pdfs, added start of the cryptox password manager sample application.

[Paul Squires]

...working on the ListBox. Hope to have that one in the library pretty soon.

[SeaVipe]

Thanks, Paul,
Will there be some sort of a Grid example?

[Paul Squires]

I think a grid is essential. Not many options at this point other than Jim's version. Maybe I'll adapt that version. A printing library will be needed as well.

I have had bad headaches these past two days so I am a little behind. I can't stare at the screen for more than an hour before my head hurts. I have an eye examination booked..... getting old.

[SeaVipe]

There's a little island just south of you that would surely help with the eye strain - Barbados - PCs not allowed!

[Paul Squires]

  lol, count me in. I could use a little bit of sun and relaxation at this time of year.

[Petrus Vorster]

  LOL, you guys have all the good islands! The only one south of me is Robben Island, and that is a jail.

[Paul Squires]

ListBox code uploaded to GitHub.

[Paul Squires]

I think top menu will be the next control to implement.

[raymw]

Hi Paul, testing out the text box. Should the enter key/carriage return, whatever it's called these days, be counted as a key press? It's often used to signify end of data entry and skip to next field, but e.keychar shows no value.