Ge van Geldorp wrote:
> Last item is perhaps a bit controversial. I don't like the huge icons in
the
> start menu. It also makes the start menu not fit in 640x480. Can we please
> go back to smaller icons?
If my memory serves me correctly, (I don't have the code in front of me),
this change was intended to support 24x24 icons in the start menu as per
Windows. However as we don't have any 24x24 icons, it defaults to 32x32 (the
huge ones we see now)
I have this reverted in my tree. I was going to revert it in HEAD until we
have 24x24 icons to allow the change to work as it should. However I haven't
been able to get hold of Martin and didn't want to revert without his say
so.
I think reverting in the 0.2.9 branch would be ok though and I'll do it
later if no one objects.
Ged.
************************************************************************
The information contained in this message or any of its
attachments is confidential and is intended for the exclusive
use of the addressee. The information may also be legally
privileged. The views expressed may not be company policy,
but the personal views of the originator. If you are not the
addressee, any disclosure, reproduction, distribution or other
dissemination or use of this communication is strictly prohibited.
If you have received this message in error, please contact
postmaster(a)exideuk.co.uk
<mailto:postmaster@exideuk.co.uk> and then delete this message.
Exide Technologies is an industrial and transportation battery
producer and recycler with operations in 89 countries.
Further information can be found at www.exide.com
When i try to make a bootcd i get:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
G:\ROS>mingw32-make bootcd
[CABMAN] all
ReactOS Cabinet Manager - Version 0.9
File does not exist: output-i386\lib\oleacc\oleacc.dll.
Directive file contains errors at line 140.
mingw32-make: *** [bootcd] Error 1
G:\ROS>
doing a mingw32-make works fine, just once i go to bootcd. I also tried
deleting makefile.auto which didnt change anything. Am i missing something?
Brandon
fireball(a)svn.reactos.com wrote:
> + if (Pdo)
> + IoInvalidateDeviceRelations(Pdo, BusRelations);
> + else
> + DPRINT1("Pdo == NULL, not sending IoInvalidateDeviceRelations()!");
This is going to be a problem if DPRINT1 isn't expanded. You should
create a {...} block for the else branch.
- Thomas
Hi,
It was Steven's idea that I should post this emai and I agreedl, so
please don't take it as my personal childish attempt to get attention,
unless you find that both I and Steven (our Project Coordinator) are
children.
Steven has recently expressed his opinion that: (modified quote so that
"your" -> "my")
"My arrogant attitude hurts this project more then any amount of code or
patches I commit will ever help it."
Therefore, since:
1) I really care about this project
2) I don't wish to spend time writing useless code (since no amount of
code will help the project more then I hurt it, then the code is
useless, like heating a room where the windows are open in winter).
I think it's important to know if this is a public opinion or not, so I
am opening a public ML vote. If it is, then I will gladly leave and stop
hurting this project, since those were not my intentions when I joined.
If this is the case, then I only regret for having stayed here so long
and done nothing but hurt the project for almost two years now, and I'm
sorry.
[ ] Alex's arrogant attitude hurts this project more then his code helps
it. Alex should therefore leave, so that the project can stop being hurt.
[ ] Alex's arrogant attitude is annoying at times but his presence in
this project significantly helps it grow and move towards reaching its
goals, and does not hurt the project.
Best regards,
Alex Ionescu
At the moment, there's one blocker bug registered, 1107: Opening a Command
Prompt (console) window causes the desktop to hang.
A lot of networking apps crash, all due to the same bug. Arty is working on
that one.
On each boot, I have to get rid of 5 device install screens. I'm not
complaining, I understand PnP is a work in progress, but if nobody objects
I'll change the code in the branch to never pop up the device install
screens.
Last item is perhaps a bit controversial. I don't like the huge icons in the
start menu. It also makes the start menu not fit in 640x480. Can we please
go back to smaller icons?
Other than these items (only 1 of them serious as far as I'm concerned) I
like the branch and I believe it will become a good release.
GvG
> From: Alex Buell
>
> I just got the following when trying to ftp to my host
> machine from ReactOS running in VMware. Are there any
> documentation out there that can help me make sense of what's
> happening below? Thanks.
>
> hal/halx86/generic/irql.c:272 CurrentIrql 2 NewIrql 1
> KeBugCheck at hal/halx86/generic/irql.c:273
Yes, this happens with a lot of networking programs at the moment. Art is
working on it.
GvG
2005/12/11, Alex Buell <alex.buell(a)munted.org.uk>:
>
> The patch that I issued for main.cpl DOES work - if you call control.exe
> directly and select either the keyboard and mouse applets you'll notice
> the patch works.
>
> Care to explain why you think the patch I sent in doesn't work?
>
sorry,
that's true.
I know that this is fluff, but I would like to contribute a good, honest
attempt at making a screensaver program for ReactOS. Basically, what I
am looking for is how is the API set up for ReactOS to write programs
for it? I am familiar with writing programs for Windows, and I know the
basic ins and outs of making a screensaver for
Windows (including it's registry settings), however there is some API
specific code that I need in order to give this a shot.
Do you guys have a reference of some kind as to what API functions,
constants, etc. that you have implemented in ReactOS that mirror those
of Windows?
Thanks in advance, and if there isn't enough in ReactOS yet for me to
try this out yet, then I'll try to help on something else that I would
be capable of.
And I must say, and I'm not trying to kiss ass here, but I really
appreciate what you guys are working at here. Keep it up.
Kenneth Armstrong