I do wish there was some more navigation control, e.g. menu items and buttons for first/last/prev/next page, and support for PgUp/PgDn, for example.
Yep, i need to check morphos's version once morphos for x5000 will be out, to see if it not implemented, or implemented but just need to be deal with in port. But i for myself miss buttons "first page / last page". They will help quite a lot, hope author will add something in next versions.
Quote:
Edit: BTW, the behaviour when selecting and copying text is a bit strange. At least in this two-column document. I tried marking a paragraph in the right column and copy it. Both columns are marked with black simultaneously, and the black block starts too early and ends too early. There is also drawn a red outline, which seems to be more correctly placed, and only in the right column. But the copied text follows the black block marking and mixes content from both columns.
Yeah whole marking don't feels very fluid. In the sources there even warning saying "implement double buffering", so at least it is known and will be deal with probably.
But i for myself miss buttons "first page / last page".
Yep, me too.
Quote:
Yeah whole marking don't feels very fluid. In the sources there even warning saying "implement double buffering", so at least it is known and will be deal with probably.
I found a new bug related to saving some MUI prefs in vpdf. Here is how to reproduce:
1. Delete or move to backup location the ENVARC:MUI/vpdf.1.prefs file if it exists. 2. Open vpdf and select the Settings/MUI menu. 3. Go to the MUI "Screen" settings and select the "frontmost public screen" option. 4. Save the MUI prefs and quit vpdf. 5. Open vpdf by double-clicking the icon and select the "Project/Open FIle..." menu. 6. Nothing happens. No requester opens. You can't load a PDF file.
I noticed this when testing if I could make vpdf my default PDF viewer. Since I can open PDFs from my Dopus4 screen and Internect screen, I needed to have vpdf open on the sereen where I was working. Until this problem is fixed, I'll have to leave AmiPDF as my default PSF reader.
Interesting ! Can it be because of MUI itself , or its VPDF bug ?
@kas1e Assuming that vpdf uses popasl class for a file requester, it's hard to see how vpdf could be at fault. The popasl autodoc states that popasl puts the screen tag in the taglist before the program adds tags. Since it's a screen option (frontmost) that's being changed in the vpdf MUI prefs, I suspect that MUI isn't giving popasl the correct screen info; causing it to fail. That's just a guess and I haven't had time to locate another MUI program that uses popasl to see if changing the program's screen setting to 'frontmost' causes the same failure.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
@kas1e, I dont know whats happening, I reinstalled vpdf and MUI, but for me it's not working and only with that file :( Anyway thanks for the attention
All further discussion about the bug should be continued there. The bugtracker exists for very good reasons.
@kas1e Roman, you really should include your modified source code in your release archive. Otherwise it will be hard to tell whether a bug is caused by your modifications or whether it has been in the original code already.
@xenic You should not jump to conclusions so easily. The fact that an MUI application openes an Asl requester does not necessarily mean that Popasl class is responsible for the requester. Popasl class opens a requester upon user interaction only (i.e. clicking the popup button). This should have become obvious when reading the corresponding Autodoc, which you obviously did as you mentioned the Autodocs yourself.
All further discussion about the bug should be continued there. The bugtracker exists for very good reasons.
Yeah, replied.
Quote:
Roman, you really should include your modified source code in your release archive. Otherwise it will be hard to tell whether a bug is caused by your modifications or whether it has been in the original code already.
@tboeckel I tested setting the "frontmost" screen option with several other MUI programs that use popasl and there was no problem. My wild guess about the cause was apparently completely wrong.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
@kas1e Great. I'll try it when it's available. At this point it looks like tboeckel should thank you for porting vpdf and uncovering a number of MUI bugs
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
I not sure if Kiero will merge anything from, be it os4 changes (probably not), or few fixes which we do in whole, but at least i do my part. And probably it will be easy now if anyone will have need to port it to os3 for example.
The official site for MUI for AmigaOS exists since 3 years by now. It is really quite ignorant if you didn't spot it by now, left alone the regular announcements of new MUI versions here on this site. The last release is just 2 weeks ago.