![]() |
QB64-PE v3.14.1 is now released - Printable Version +- QB64 Phoenix Edition (https://qb64phoenix.com/forum) +-- Forum: Chatting and Socializing (https://qb64phoenix.com/forum/forumdisplay.php?fid=11) +--- Forum: Announcements (https://qb64phoenix.com/forum/forumdisplay.php?fid=18) +--- Thread: QB64-PE v3.14.1 is now released (/showthread.php?tid=2984) Pages:
1
2
|
RE: QB64-PE v3.14.1 is now released - Cobalt - 11-20-2024 you mean like click on something then wait 3 or 4 seconds then click again? Afraid I've never used it like that, I've always double clicked. Why I didn't see any difference. But yes, apparently before you could wait (probably indefinitely) between clicks and it would open a file or change directory. But now you do have to double click. RE: QB64-PE v3.14.1 is now released - bplus - 11-20-2024 Yeah, I never like double clicking it makes my index finger twitchy when done often. But really only .5 sec if that much between single clicks. I am wondering if this change was done on purpose it seems like an artifact of some other change. RE: QB64-PE v3.14.1 is now released - RhoSigma - 11-20-2024 Well B+, good news I've identified the change responsible for the different behavior, it's the addition of the _ANDALSO timeElapsedSince#(firstClickTime#) < 0.3# part in line 14339 in file source/ide/ide_methods.bas, it's part of SUB ideobjupdate. Bad news, that SUB handles the object updates in ALL kinds of dialog boxes and the mentioned change was required to better distinguish between single click objects, click and hold objects and double click objects in regard to catch stray clicks from falling through from one object type to another and maybe accidentially trigger an unintended action on that other object. In short the change needs to be kept in place for now, probably a complete rewrite of that entire SUB or eventually even the entire legacy dialogs system in the future may organize things better, but that would be a lot of work and certainly happens not very soon. On the other hand I think double clicks on list box items are pretty common anyways. RE: QB64-PE v3.14.1 is now released - bplus - 11-21-2024 Thanks for tracking that down Rho. At least I know why I have to double click quicker now. RE: QB64-PE v3.14.1 is now released - bplus - 12-05-2024 Why is my Recent List of Files never going past 19 items. I am losing the order I did things and what I did! oddly the slow printing has resolved. but one session I had strangely named folder stuck in open file dialog. This version seems shoddy! RE: QB64-PE v3.14.1 is now released - SMcNeill - 12-05-2024 (12-05-2024, 12:19 PM)bplus Wrote: Why is my Recent List of Files never going past 19 items. I would guess it's because you have that set as a limit for your stuff. Change the limit if you want. MAIN MENU >> Options >> Undo/History Set it for up to 200 items if you want. It's only doing what you've told it to do. ![]() RE: QB64-PE v3.14.1 is now released - RhoSigma - 12-05-2024 It's also to note, that since v3.14.0 the recent files and search string histories are globally shared between all running IDE instances. Hence if you open a file in one instance, then that file goes automatically to the top of the recent list in all other instances too. Same with search strings, each new search string entered in any instance is immediately available for selection in all other instances too. RE: QB64-PE v3.14.1 is now released - bplus - 12-05-2024 (12-05-2024, 01:04 PM)SMcNeill Wrote:(12-05-2024, 12:19 PM)bplus Wrote: Why is my Recent List of Files never going past 19 items. Never told it to do 20 must be default setting. Never knew I had to reset that when I started 3.14.1 RE: QB64-PE v3.14.1 is now released - RhoSigma - 12-05-2024 (12-05-2024, 03:46 PM)bplus Wrote: Never told it to do 20 must be default setting. Never knew I had to reset that when I started 3.14.1 B+, approx. 2 weeks ago (look at post #7) you're using v3.14.1 now, I'm not sure what was your all day working version before, but I assume you skipped at least v3.14.0 if not more versions. I'd kindly suggest carefully reading through the release notes of all versions you may have skipped at the GitHub Releases page to bring yourself up to date again regarding the changes. |