QB64.org Forum
Active Forums => QB64 Discussion => Topic started by: bplus on February 03, 2021, 03:36:45 pm
-
How close are we to a stable v1.5?
and what still needs to be more fully tested?
-
We're pretty close to releasing. Some new bugs that have been reported recently might not make it and may take a bit more to be addressed.
This is what's new/fixed so far: https://www.qb64.org/portal/development-build-changelog/
BTW, development builds page updated today (the automated process got tweaked, we're now storing dev builds in AWS): https://www.qb64.org/portal/development-build/
-
AWS = Amazon Web Services storage virtually unlimited Cloud storage.
-
OK so Constants with Suffix not worth the trouble to fix? or was that in Math Evaluator fix?
Getting the Alphabet Keyword List on first click, was that fixed and I just need an update?
-
The constant bug the Qwerkey had reported some months ago (https://www.qb64.org/forum/index.php?topic=1303.0) got fixed.
Did I forget to add it to the log? Just added it to the log.
Getting the Alphabet Keyword List on first click, was that fixed and I just need an update?
What was that again?
-
The constant bug the Qwerkey had reported some months ago (https://www.qb64.org/forum/index.php?topic=1303.0) got fixed. Did I forget to add it to the log? Just added it to the log.
What was that again?
Well the constants with suffix just came up again recently, as I recall it's fine (specially functions, non literals) but problems crop up with suffix symbol on variable, gone, no problems when suffix removed or no suffix to start.
Help Menu > Keyword Index > gets you a blank Help window with Alphabet Tab next to Help tab
Click Alphabetical all you want now and nothing happens.
Click Help again then chose either Help "Tab"or Alphabetical "Tab" and we are OK.
This might have been fixed and I just have to update keywords in Help, I will check now...
Oh I thought there was an option to update the Help, OK it's in the Help Menu off IDE, ...10 minutes!
-
I'll look into that, I didn't recall it was a thing. Thank you.
-
Yes, I just updated all Help pages and the problem as described remains but this is version 1.4 you will have to confirm for dev v1.5
-
Just fixed it for v1.5. You can grab the latest dev build to help test the new features out now.
-
OK which change are you most leery about?
-
Latest Dev version:
Oh we aren't going to shout out the keywords anymore!? (see attached) I missed that announcement.
Confirmed the Help thing is fixed, one or two less clicks to the Keyword Index.
PS Oh wait... all those rounded up, I was expecting they would round down, 1, 2, 3.
OK they actually do round up or down.
-
New Folder button nice, I am going to need for 1.5 because these ReDim's aren't going to work in old Bas file Folders.
Ctrl+K is going to nice, if I can remember the Combo, no more lookup of the arrow key numbers.
Say is there a place that tracks all the Short-cut keys?
====> Hey the ASCII Chart and the Math menu items off the Help Menu Item are missing!
-
OK which change are you most leery about?
- CONST fix (can you still break it?)
- SEEK has to reset EOF() fix (after a file is read in INPUT mode until the end, using SEEK to another position within the file must reset EOF())
- New DIM/REDIM/STATIC/SHARED/COMMON/TYPE syntax (did I miss any detail?)
- New CamelCase internal keywords (did I miss any keyword? - although you should notice some will remain all caps because they are initials, like EOF, LOF, RGB)
- Find and Change dialogs (Search menu) now allow you to ignore text in comments and strings - or search exclusively in comments or strings. (is there any corner case that gets it to not work properly?)
CamelCase comes enabled by default but can be disabled via the Options menu. You gotta agree it does look much calmer (since it's NOT SHOUTING ANYMORE) and it does look more elegant too.
-
Yes I like new Camel Case.
@FellippeHeitor did catch my note of missing ASCII chart and Math off the Help menu?
Update: Well I try another update of the Help pages maybe that will fix it.
Oh hey! That's a new dialog box, prettier than the list on words running down the screen earlier today.
-
Yes I like new Camel Case.
@FellippeHeitor did catch my note of missing ASCII chart and Math off the Help menu?
Update: Well I try another update of the Help pages maybe that will fix it.
Oh hey! That's a new dialog box, prettier than the list on words running down the screen earlier today.
There’s a new Tools heading in the menu.
-
I didn't catch it because you edited an older post. As Steve pointed out, look into the new Tools menu.
-
Oh! Thanks, guess I don't have to memorize Ctrl+K to check keyhits.
-
I've always liked the upper caps keywords, but that camel case is really growing on me. Looks good.
Looking through the changelog, you all have done a lot of great work in this version. Thanks!
- Dav
-
Yes I was just going down the list of Changes, hadn't come to Camel Case and Tools menu yet.
It is easier to review the ChangeLog with the QB64 version it's talking about.
Like the dark Blue!, I changed comment color to 0, 160, 0 you guys might like that too.
-
Is there a listing of short cut keys anywhere in Help?
or maybe an idea for Tools?
-
Boo, hisss, about this "camel case" change. Keywords being all caps helps, because it confirms that you just wrote a keyword. I think it should be enabled by default. But okay, at least the new idea can be disabled.
I realize that VB did it this way too, no shouting. But to me, the all caps was a feature. Hell, it even helps when we type up stuff in this forum, to make it clear.
Thanks for allowing its continued use.
-
When in doubt about which way to take a feature, let the user choose. :)
-
Boo, hisss, about this "camel case" change. Keywords being all caps helps, because it confirms that you just wrote a keyword. I think it should be enabled by default. But okay, at least the new idea can be disabled.
I realize that VB did it this way too, no shouting. But to me, the all caps was a feature. Hell, it even helps when we type up stuff in this forum, to make it clear.
Thanks for allowing its continued use.
I am working into a system, if the first letter is Capital it's Global like Const, Type, Shared variables or Arrays and my Subs and Functions I define, so as long as Keywords which start with Cap have to be Global, fine!
And just use camel again for local but have the 1st letter always lower case.
Then when you type, don't ever shift for caps, do all lower case (it's easier anyway) and the Globals will pop up if you typed them right. The locals are just a quick scroll up or down if you need to double check the spelling.
-
Yes, I get that, bplus. Thing is, I also tend to type everything lower case, except that I may have caps and lower case letters, in some of my variable names. As in, something like, InitialAngle.
So, to the extent possible, just like you I'm typing in lower case. So it's very reassuring when the keywords are trivially easy to distinguish, right after you've typed them. It also confirms that there are no syntax errors elsewhere in the program, when the keyword changes itself to all caps.
Here's the irony. I thought that QB64 stayed with all caps, in keywords, because it was better, than the way VB did it. I guess we make our own realities, eh? Anyway, fine with me, if we have a choice.
-
Not only you have a choice of switching back to all caps, but you also get confirmation of keyword correctly typed because the initial will still change to a capital - sometimes more than the initial for keywords like InKey$ - not to mention that even if you disabled any formatting (which you can do - some people like to keep their code in all small letters, right @luke?) you could still confirm all you typed is correct because keywords are colorized immediately as you type them.
-
I hope I can get my WP wrapped up... no pun, wait, pun intended... so I can upgrade from 1.3 to 1.5. Version 1.3 is great, but I'm going to want that "AS" UDT ability in 1.5. I'm skeptical about the new IDE text features. I'll either love them or hate them, but whogas, as long as I can decide to keep or toss them in the options menu.
Looking forward to the stable release date,
Pete
-
you could still confirm all you typed is correct because keywords are colorized immediately as you type them.
Aha, a detail I had missed. That might make enough of a difference, right there. I'll be downloading this update in short order, and give it a spin. Got to get some work out of the way first. Thanks!!