 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : File Manager for PicoMite
  Page 19 of 19 |
|||||
| Author | Message | ||||
| dddns Guru  Joined: 20/09/2024 Location: GermanyPosts: 533 |
Copying a directory with F5 and move/rename with F6 are buggy. F5 dir copy does not return to the FM but the copy is done. F6 shows a blank page in serial console and nothing happens on local screen. Left panel does not show a column for file size. Tested with resolutions 848 and 1280 I cannot see a usecase for the command line, as it does not return to the FM. What do you use it for? Edited 2025-07-16 02:29 by dddns |
||||
javavi Guru Joined: 01/10/2023 Location: UkrainePosts: 497 |
Just checked on 640x480 everything works. These are hardware failures of the hardware or MMBASIC system due to overclocking, test on lower resolutions... I noticed that on high resolutions failures happen often! Wait a second, Coming soon... But you can also enable it in the program. For example, while in FM, you can type an option or a command and it will be executed upon exiting FM... That's how I save.)) |
||||
| javavi Guru Joined: 01/10/2023 Location: UkrainePosts: 497 |
The long-awaited release of File Manager v1.70 from Javavi  FM170.zip + Support for all resolutions + Switchable panel view (simple wide, with sizes) + Added function to search for one file from the current directory. etc...  |
||||
| dddns Guru Joined: 20/09/2024 Location: GermanyPosts: 533 |
Tested FM160, 164 and 169 with OPTION RESOLUTION 640 @252000. With none of these versions copying a directory works for me. A single file is copied without problems. F6 doesn't work for me either. In both cases it does not crash the pico! I'm playing around with this pico since half a year. Overclocking works rock solid and I never saw it doing things like that.. I would not exclude that it is really my specific setup..who knows All the best! With F6, ESC seems to help to get back into FM. I will check my sd card setup Edited 2025-07-16 03:15 by dddns |
||||
| javavi Guru Joined: 01/10/2023 Location: UkrainePosts: 497 |
Testing on PicoMite HDMI and VGA v.6.00.02 I just copied the PETROBOTS folder from disk to disk and moved it. There is a certain period of waiting for copying and it's done without any problems. The time depends on the number of files in the folder. A BASIC program should only do what it should do! |
||||
| dddns Guru Joined: 20/09/2024 Location: GermanyPosts: 533 |
Copy works! I overlooked, that the content is 3Mb and I was not patient enough. It took 1min to copy. F6 works as well. I found this with an USB keyboard, my terminal software uses F6 as clear terminal hotkey :)) I'm sorry for this bad report! |
||||
homa Guru Joined: 05/11/2021 Location: GermanyPosts: 470 |
  |
||||
| Volhout Guru Joined: 05/03/2018 Location: NetherlandsPosts: 5072 |
hi javavi, Running FM169 on "classic" RP2040 VGA PS2 system with 6.00.03. I can use <ALT> and <BACKSPACE> to select the alternate function of the keys. Alternate functions F1 and F2 work (select drive) Alternate functions F3 and F4 do not work (view2 / edit) Alternate functions F5 and F6 (XMODEM RCV and TX) start RCV and TX Alternate function F7 does not work (find) I am pressing <ALT> or <BACKSPACE> and release these before I press the function key. Maybe I am not using FM correct, but since F1/F2/F5/F6 work, I assume there is something wrong with F3/F4/F7 implementation. UPDATE Running FM170 on "classic" RP2040 VGA PS2 system with 6.00.03 "find" now works. But alternate functions F3 and F4 do still not work. Bug: When using EDIT (F4) on a normal basic program, and closing the edit (either <ESC> or <F1>) I get an error message : [92] Color c(7),c(0):x=2*FW Error : 54241275355405417485 is invalid (valid is 0 to 268435455) Since the program I edit is only 10 lines, this must be the file manager causing the error. When I look in the editor, line 92 seems corrupt when shown in the error message. Regards, Volhout Edited 2025-07-16 22:33 by Volhout PicomiteVGA PETSCII ROBOTS |
||||
| javavi Guru Joined: 01/10/2023 Location: UkrainePosts: 497 |
hi Volhout, In the current version of FM v1.70, alternative functions F3 and F4 are provided but not implemented. sorry! I just checked the operation of FM on the PicoMiteVGA v6.00.01 firmware and the F4 file EDITOR function works, the editor opens with an editable text and successfully exits back to FM after closing. Yes, when opening very large files, it gives an error about lack of memory. Therefore, I think that this is not a FM problem, but the implementation of the EDIT FILE command in the new firmware, which appeared with the version of PicoMite in 6.00.02 and went to 6.00.03 To solve this problem, we need @matherp help! Edited 2025-07-17 00:14 by javavi |
||||
twofingers Guru Joined: 02/06/2014 Location: GermanyPosts: 1579 |
This is my new test version of the FM. FM02078.zip New features include: - a revised Replace function (shift-F7) - a Find function for multiple matches (shift-F5) - Merge now uses the file in the opposite panel as the insert file - "hf.bas", a module for displaying all function and subprocedure-headers of a file using F11. - several small changes: For example, line numbers are optional in the text viewer (can be enabled in the user menu). Basically, I'm still waiting for Peter's announced text mode so that the pop-up handling can be improved. I'll be offline for a few days. @Vadim, if you'd rather I didn't post in this thread anymore, just let me know. Regards Michael causality ≠ correlation ≠ coincidence |
||||
| dddns Guru Joined: 20/09/2024 Location: GermanyPosts: 533 |
It works in full extent! It works perfect with FONT 1 and 4, all other fonts work as well only the frame is missing. Colours and inverted text work fine as in HDMI. My resolution is 800x480. Your new scaling is solid! The processing speed is at least as fast as on HDMI and 2350. Very usable! It looks very nice on a LCD! Pictures are shown in true colour :) Edited 2025-07-17 20:00 by dddns |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10273 |
Prompted by a comment on the 6.00.03 thread I've just checked the FM code and see that EDIT FILE is called from within a subroutine. This is a definite no-no and a comment will be added to the manual. Like CHAIN and SAVE CONTEXT, EDIT FILE must be called from the main program. |
||||
| javavi Guru Joined: 01/10/2023 Location: UkrainePosts: 497 |
I checked this, moved the call of the EDIT FILE TMP$ command from the subroutine to the main DO...LOOP loop, but this had no effect, the error after closing the tditor is exactly the same as with the COLOR c(7) command, supposedly an invalid value is passed to it from the c(7) array variable, although the values in this array are not distorted. |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10273 |
That sound more hopeful but I still need a simple test program exhibiting the bug if you want it fixed. |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2440 |
peter: generate a firmware where the COLOR command outputs additional information about the parameters passed to it to either COM2: or the USB console. in theory, you could output pages of data to help figure out what is going on. javavi then just needs to use a terminal emulator to capture the data. while not a 'simple (BASIC) test program', this would be a simple means of moving a fair bit closer to figuring out why the wheels are falling off. cheers, rob :-) Edited 2025-07-19 02:15 by robert.rozee |
||||
| matherp Guru Joined: 11/12/2012 Location: United KingdomPosts: 10273 |
Just looked at the FM code again. You appear to have a settick set up. This should be cancelled before entering the edit. This could definitely cause problems. |
||||
| javavi Guru Joined: 01/10/2023 Location: UkrainePosts: 497 |
Completely disabling SetTick 1000 did not bring the expected result, it still crashes into an error. I solved the traps and determined that the color array c() is still damaged, causing an error in the COLOR c(0) command. Moreover, the data distortion in the array does not occur immediately after the EDITOR command, but only after calling two consecutive subroutines. In this case, if you swap it below in the order of array declaration, then another array that comes first in the declaration is damaged. P.S. And if you first declare an empty array for the ballast BALL(15), then the program continues to work without failures after opening and closing the file for editing.  P.P.S. But reopening a small file for editing leads to the error: [94] Edit File TMP$ Error : Not enough Heap memory Edited 2025-07-19 03:29 by javavi |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2440 |
javavi: what would happen if you were to do this in your code: VAR SAVE TMP$ CLEAR VAR RESTORE TMP$ EDIT FILE TMP$ then, immediately after returning from the call the editor, rebuild all the variables you have lost? things like the current view (directory) for left and right windows could similarly be saved. this would mean that peter would be able to modify EDIT FILE so that it no longer needed to bother with moving the contents of RAM, and could just work with whatever was currently free. cheers, rob :-) |
||||
| Page 19 of 19 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
