Who's Online |
87 user(s) are online ( 56 user(s) are browsing Forums)
Members: 1
Guests: 86
amije,
more...
|
|
|
|
|
Re: MUI 4.0-2014R3 released
|
Posted on: 2014/3/16 20:11
#61
|
Just popping in 
|
@Prober
Sorry, but the step towards transfex has been taken and we won't go back. We just enhanced FlexCat to handle .po files natively on all supported systems, thus is it not as "alien" as you might think.
Perhaps you just try transifex for Amiga translations. It is not as bad as it might seem on the first look.
|
|
|
|
|
|
Re: MUI 4.0-2014R3 released
|
Posted on: 2014/3/16 12:45
#62
|
Just popping in
|
@all There is a public bug tracker on http://muidev.de. If you have any bugs to report, please do it there. The bug tracker makes things a lot easier. Just get a login there and open a new ticket for each single bug or enhancement request. Please remember to login before reporting or answering.
|
|
Why stop it now, just when I am hating it?
Thore Böckelmann
|
|
|
|
Re: MUI 4.0-2014R3 released
|
Posted on: 2014/3/16 12:39
#63
|
Just popping in
|
@xenic I admit that the WbMan demo is quiet outdated and does no longer match the current affairs of AmigaOS4 and its startup handling. Perhaps I will remove it for the next release. But in principle it is meant to be a simple demo how to use MUI. Quote: When I tried the NewStuff demo, if failed and a console popped up stating: "Failed to create Application." Please check with Snoopy if bz2.library and z.library are opened successfully.
Edited by tboeckel on 2014/3/16 13:16:20
|
|
|
|
|
|
Re: MUI 4.0-2014R3 released
|
Posted on: 2014/3/16 12:37
#64
|
Just popping in
|
@xenic
Sorry, that was just another quirk in the AutoInstall script. All libraries were simply copied to MUI:Libs, however btree.library, bz2.library and z.library really should reside in LIBS:. The Installer script does this portion right.
There is no need to open a ticket in the bug tracker, this has been fixed already for the next release.
|
|
|
|
|
|
Re: MUI 4.0-2014R3 released
|
Posted on: 2014/3/15 21:45
#65
|
Just popping in
|
@Chris
I just uploaded a new archive with a fixed AutoInstall script.
|
|
|
|
|
|
Re: Odyssey 1.23 progress
|
Posted on: 2014/3/15 21:16
#66
|
Just popping in
|
@Kicko
I just uploaded new archives with a fixed AutoInstall script. I hope it works correctly now. I cannot test this myself right now.
|
|
|
|
|
|
Re: MUI 4.0-2014R3 released
|
Posted on: 2014/3/15 19:15
#67
|
Just popping in
|
Updated archives have been uploaded.
|
|
Why stop it now, just when I am hating it?
Thore Böckelmann
|
|
|
|
Re: MUI 4.0-2014R3 released
|
Posted on: 2014/3/15 19:09
#68
|
Just popping in
|
@samo79
Unfortunately we don't have automatic synchronization between transifex and the MUI SVN repository yet. That's why I didn't know the translations were updated.
I will sync them immediately.
|
|
|
|
|
|
MUI 4.0-2014R3 released
|
Posted on: 2014/3/15 19:00
#69
|
Just popping in
|
A new release of MUI 4.0 for AmigaOS4 has been made available for download on the MUI development for AmigaOS page. The main focus was on bug fixing. The fixes done on the the new register class Title.mui will make this release the minimum requirement for future releases of Odyssey Web Browser.
|
|
|
|
|
|
Re: Odyssey 1.23 progress
|
Posted on: 2014/2/28 18:38
#70
|
Just popping in
|
@joerg Quote: No idea what it is, but "MUI imagespace screen notify" child process is still running after exit, and it's still waiting for some signals which shouldn't happen either. That is a process created by MUI which will flush all unused images used on a just closed screen. This process is started with NP_Child=FALSE.
|
|
|
|
|
|
Re: Odyssey 1.23 progress
|
Posted on: 2014/2/27 10:05
#71
|
Just popping in
|
@kas1e Quote: Quote:Why are you causing DSI exceptions (handled by the kernel, but all exceptions are very slow) by using
SysBase = *((struct ExecBase **) 4);
I don't have any DSIs there for those ones (and i am on debug kernel with munge). Or you mean they invisibly ? This is exactly what Jörg wrote. Peeking at address 4 is in fact causing a DSI exception, but this is handled silently by the kernel. The point is that exceptions cause a major performance penalty, even if they don't become visible. Peeking at address 4 must be supported, because this was documented to be valid since day zero of Amiga history. But there are lots of other ways to get a valid ExecBase address which don't require this kind of a big wooden hammer and hence don't cause any further performance penalty.
|
|
|
|
|
|
Re: Odyssey 1.23 progress
|
Posted on: 2014/2/10 10:00
#72
|
Just popping in
|
@kas1e
There is no need to call SetWindowPointer() anymore to set one of the internal pointers. set(window, MUIA_Window_PointerType, type) works perfectly. Check the SDK directory that is coming with the MUI releases. Depending on the possible directions a value like MUIV_PointerType_NorthEastSouthWestResize should be exactly what you are looking for. MUI4/AmigaOS4 has some additional pointer types compared to MUI4/MorphOS (see NewStuff demo).
|
|
|
|
|
|
Re: Imgur kills Odyssey?
|
Posted on: 2014/1/20 14:08
#73
|
Just popping in
|
The value 0xcccccccc in r9 clearly points out a duplicate Remove() of a node from an Exec list.
|
|
|
|
|
|
Re: MuiOWB does not recognise "local" image tags
|
Posted on: 2013/12/17 20:07
#74
|
Just popping in
|
@kas1e
I'd say helgis' account was hacked and the last comment was done by someone else, but not helgis himself. His last two comments don't really match word-wise and especially the last one doesn't sound like helgis. Take a look at the two comments. He seems to have changed his mind from "thumbs up, you did a good job" to "you are an idiot" within just 2 hours. I cannot believe this. This really sounds like a comment from a spammer, but not like helgis.
|
|
|
|
|
|
Re: MUI : NList notify on "end of multiselection" or "Mouse-Up" event
|
Posted on: 2013/9/3 19:34
#75
|
Just popping in
|
Quote: For example, I would like to know when a user end to multi-select elements of a NList.
Is it possible ? Short answer: No. Long answer: No, for what do you need it? You can never know when a multi selection is finished, because it is possible to add further elements to the selection at any time. A multi selection must not necessarily consist of adjacent elements.
Edited by tboeckel on 2013/9/3 19:50:53
|
|
|
|
|
|
Re: MUI : AmigaOS freezes when window resized to minimum ?
|
Posted on: 2013/6/17 21:24
#76
|
Just popping in
|
Quote: Actually this happens with BOOPSI/Reaction windows as well. Unfortunately I haven't reported this to anybody. I'd say this takes MUI out of the equation completely.
|
|
|
|
|
|
Re: MUI : AmigaOS freezes when window resized to minimum ?
|
Posted on: 2013/6/17 21:23
#77
|
Just popping in
|
Quote: For info, freeze is reproductible with MUI-Mplayer.
Open an video and resize the video window to minimum => freeze.
Is somebody have the same problem ? As MUI-MPlayer is not Open Source Roman 'kas1e' Kargin is the only who can answer this question. Maybe the window is not under control of MUI but created in the usual way using intuition/OpenWindow(). Furthermore the freeze might be caused by the video display due to a possibly invalid dimension, i.e. zero pixels width/height.
|
|
|
|
|
|
Re: MUI : AmigaOS freezes when window resized to minimum ?
|
Posted on: 2013/6/17 21:20
#78
|
Just popping in
|
Quote: Sometimes, not every time, when I resize a MUI window to the minimum size (very small window where even the close gadget is no more visible) my system freezes. Can you provide a small demo program which can be used to reproduce this issue? Quote: For now, to avoid this problem I force the closure of the window when size is < 100 pixels. Not a very convenient reaction as there is no way to open the window again. In fact it looks as if the program has terminated itself, although it just closed its window. Quote: Is it a way to set a minimum size to a MUI window (without adding a fixwidth object) ? No. This contradicts the basic MUI principles.
|
|
|
|
|
|
Re: Newstring.mcc a commodity????
|
Posted on: 2013/5/15 5:35
#79
|
Just popping in
|
Quote: If newstring.mcc as a commodity can't be (user) accessed (and the user can't do anything with it either), wouldn't it be possible to "hide" it from view (Exchange) et al? What is so wrong about letting the user see that there is something which hooked into the input stream, although it cannot be controlled by the user? Quote: It'd be still running in the background and Exchange knowing about it
i.e. it could be "greyed out" in the Exchange list My latest change will give you something similar. Although you still cannot control the Newstring.mcc commodity, you will now get some visual feedback: analog to the disabled Show and Hide buttons the Kill button will be disabled to indicate that this commodity cannot be removed manually.
|
|
|
|
|
|
Re: Newstring.mcc a commodity????
|
Posted on: 2013/5/14 18:42
#80
|
Just popping in
|
Quote: So it means one can't expunge it from memory, right? Not unless all applications dispose all instances of Newstring.mcc. There is absolutely no need to do this yourself. The commodity broker will be removed automatically upon expunging Newstring.mcc from memory.
|
|
|
|
|
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
