+- QB64 Phoenix Edition (https://staging.qb64phoenix.com)
+-- Forum: Official Links (https://staging.qb64phoenix.com/forumdisplay.php?fid=16)
+--- Forum: Announcements (https://staging.qb64phoenix.com/forumdisplay.php?fid=18)
+--- Thread: QB64 Phoenix Edition v3.4.0 Released! (/showthread.php?tid=1028)
QB64 Phoenix Edition v3.4.0 Released! - DSMan195276 - 11-01-2022
QB64 Phoenix Edition v3.4.0!
https://github.com/QB64-Phoenix-Edition/QB64pe/releases/tag/v3.4.0
Enhancements
- #189, #216, #225, #227, #230 - Added several cross-platform dialogs - @a740g, @mkilgore
- The commands make a best-effort of determining the way to show the dialog based on what is provided by the system.
- The follow new commands were added:
- _NOTIFYPOPUP [title$][, message$][, iconType$]
- _MESSAGEBOX [title$][, message$][, iconType$]
- result& = _MESSAGEBOX(title$, message$, dialogType$, iconType$[, defaultButton&])
- result$ = _INPUTBOX$(title$, message$[, defaultInput$])
- folder$ = _SELECTFOLDERDIALOG$(title$[, defaultPath$])
- color32bpp~& = _COLORCHOOSERDIALOG(title$[, defaultRGB~&])
- result& = _OPENFILEDIALOG$(title$, defaultPathAndFile$, filterPatterns$, singleFilterDescription$[, allowMultipleSelects&])
- result& = _SAVEFILEDIALOG$(title$, defaultPathAndFile$, filterPatterns$, singleFilterDescription$)
- _NOTIFYPOPUP [title$][, message$][, iconType$]
- The commands make a best-effort of determining the way to show the dialog based on what is provided by the system.
Bug Fixes
Full Changelog: https://github.com/QB64-Phoenix-Edition/QB64pe/compare/v3.3.0...v3.4.0
RE: QB64 Phoenix Edition v3.4.0 Released! - bplus - 11-01-2022
Wow that's gonna help! Long time needed dialogues a welcome sight!
RE: QB64 Phoenix Edition v3.4.0 Released! - mnrvovrfc - 11-01-2022
Thank you for this! I have finally updated from v3.1 unconditionally on Windows and Linux!
Goodby "xmessage" ROFLMAO well done! Although I find the MATE/XFCE notification window very annoying at times, it's cool to be able to come up with one of those too.
LOL actually tested with this code snippet:
Code: (Select All)
DIM x AS INTEGER
x = ASC("")to create an error on purpose. In addition to the new statements and functions.
RE: QB64 Phoenix Edition v3.4.0 Released! - SpriggsySpriggs - 11-01-2022
Very cool stuff in this release, amigo!
RE: QB64 Phoenix Edition v3.4.0 Released! - Pete - 11-01-2022
What do you see these features being used for?
RE: QB64 Phoenix Edition v3.4.0 Released! - SpriggsySpriggs - 11-01-2022
(11-01-2022, 06:47 PM)Pete Wrote: What do you see these features being used for?
I could see people adding at least the open and save dialogs to their programs to enhance the user experience. Rather than having to create a dialog themselves, they can just use the native ones without all the guesswork.
RE: QB64 Phoenix Edition v3.4.0 Released! - Pete - 11-01-2022
That's probably what I used PCOPY and screens that appeared to create popup message boxes. Yeah, that's a bit of work, but at least it is fully customizable.
Pete
RE: QB64 Phoenix Edition v3.4.0 Released! - Coolman - 11-01-2022
compiled and testing under linux kde. so far, so good. great job.
RE: QB64 Phoenix Edition v3.4.0 Released! - bplus - 11-01-2022
(11-01-2022, 06:47 PM)Pete Wrote: What do you see these features being used for?
Default worked, 17 Enter worked, Cancel as seen worked as expected.
I have to note the first time I used _InputBox, it used a different title than the one I spec'd, something about TinyDialog...?
The second time and every time after it behaved as expected.
RE: QB64 Phoenix Edition v3.4.0 Released! - Jack - 11-01-2022
I am not C savvy but I get this warning when building QB64 with another toolchain
Code: (Select All)
internal\c/parts/gui/tinyfiledialogs.c: In function 'tinyfd_openFileDialog':
internal\c/parts/gui/tinyfiledialogs.c:3112:1: warning: function may return address of local variable [-Wreturn-local-addr]
3112 | }
| ^
internal\c/parts/gui/tinyfiledialogs.c:3060:14: note: declared here
3060 | char lBuff[MAX_PATH_OR_CMD];
| ^~~~~
internal\c/parts/gui/tinyfiledialogs.c:3060:14: note: declared herethe warning is eliminated if you add static to the lBuff declaration
Code: (Select All)
static char lBuff[MAX_PATH_OR_CMD];