Simple User Interface Improvement

There is one aspect of the user interface that has always slowed my productivity in LR. The scroll bars located on the far left and right of the side panels are thinner than standard scroll panels in Windows programs. When I work with the interface at my normal operating speed, I usually miss the scroll bar 50% of the time when I try and click and drag them. I thought over time this issue would go away as I got use to this irregular aspect of the LR interface, but it has not during the years I have used LR starting with version one. Since many people have wide screen displays, it seems like having a normal width scroll bar would not sacrifice that much screen real estate and would benefit those of us with hand eye coordination that falls outside what was envisioned by the LR user interface developers. Perhaps it could be an optional setting.
Of all of the user interface improvements possible in LR, this one simple change would be of the greatest benefit to my productivity.
Thank you for considering it

Ken, I agree. In general, many of the user-interface elements of LR are fussy and non-standard in their behavior. A couple of examples: The scroll bars don't have up and down arrows at the end, making it hard in large catalogs to scroll by one line of thumbnails using the mouse. Scrolling the Library Filter Keywords column is particularly painful when it has a thousand keywords.
Adobe wants feedback to the product team submitted at the feedback forum:
http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightro om
If you create a topic there, I'll vote for it!

Similar Messages

Labview Simple User Interface

I would like to know how to add a simple LED indicator in the TestStand Labview Simple User Interface that would display the Sequence Status( PASSED or FAILED ) ?
I'm using TestStand 3.1.
Thanks a lot
Olivier

Hi Olivier,
There are several ways to implement this.
The quick and easy method would be to read the ItemText from the Executions ComboBox control. Then scan it to see if it contains "Passed".
(see attached VI)
An alternative is to setup a TestStand UI Label Control, Using the ExecutionViewManager you can set a CaptionSource to the UUTStatus. This will then contain the UUTStatus of the currently selected execution. This is similar to above except the string will only contain the UUTStatus string, not all of the details in the execution string.
However a "more complete" method would be to setup a Callback VI for UIMessages, when the UIMsg_ModelState_TestingComplete is recieved, the UUT status can be retrived. (Refer to the TestStand Help file)
The callback (assuming it has a reference to the LED) can then set the value of it.
This method is prefered over the above 2 because you do not need to poll the TestStand controls to get the status information. When the TestingComplete event occurs, TestStand will execute the Callback VI.
I hope this helps.
Simon Holman
Software Engineer
Certified LabVIEW Developer
Certified TestStand Developer
measX GmbH & Co. KG.
http://www.measx.com
Attachments:
Simple OI - Top-Level VI (Quick).vi ‏191 KB

Building a simple User Interface

HI,
I'm interested in building a very simple User Interface. All I want to see is a panel with buttons and each button will execute a test sequence file.
1) Is it possible to create such a panel with CVI or LV and then call a sequence file which will be handled by TS?
In that case, I would expect to see TS panels while executing the sequence and once finished (or closed by the user) to come back to the original panel that calls the sequences.
2) is it better to create this panel with TS utility? (I have never done it and suspect it will not be a simple job).
Thanks
Rafi

You can do this in test stand if a simple interface containing just a prompt and buttons will do. In your main sequence, the first step is to create a MessagePopup step. Put a title like "Test Selection". Put a message like "Choose a Test". Label button 1 "test 1". Label button 2 "test 2", and so on. Create a local numerical variable called TestNum. In the post expression section of the first step, add the line Locals.TestNum = Step.Result.ButtonHit. You next step can be a sequence call to the first test sequence. Add a precondition that Locals.TestNum==1. The following steps can all be sequence calls to your other test sequences with preconditions of Locals.TestNum==x, where x is the number corresponding to the button hit in step one. When the selected test sequence is done, the main sequence will be repeated with the message popup asking for a test to run.
- tbob
Inventor of the WORM Global

Use networked Users.ini in deployed simple user interface

I'm using the Simple LabVIEW UI that comes with TestStand 2014. I have customised it to my requirements, but have a small issue. I want to deploy the interface to numerous production PC's but cannot workout how to get the interface to use a networked Users.ini, at Login on those PC's. Does anyone know how to make the user interface use a networked Users.ini? I know that in TestStand 2014 you can use the menus Configure>Station Options>User Manager to tell it where to find a networked Users.ini. I don't know how to make the Simple LabVIEW UI do the same thing. Hopefully I've missed something obvious and will soon be felling rather stupid.
Thanks
Colin

Colin,
This setting is stored in TestExec.ini. You can deploy this by following this link: http://digital.ni.com/public.nsf/allkb/E5E4FEADEFE6023D862571590000C5CC
Here's another link:http://zone.ni.com/reference/en-XX/help/370052N-01/tsdeploysystem/infotopics/includingcfgfiles/
TestExec.ini is just 1 of many cfg files for TestStand. They all need to be in the same folder. Generally the ProgramData\National Instruments\<TestStand>\Cfg folder. The exception is Users.ini. It is the only cfg file that can be in a different location (as you have discovered)
So I recommend pointing to the users.ini on your development machine and then adding TestExec.ini to your workspace. Then you need ot put it in the Cfg directory on the deployment machine. Be careful though because there are a lot of other settings stored in that file.
Hope this helps,

Teststand Simple User Interface in LabVIEW

Hello Community,
I am designing a user interface for Teststand by using the simple example vi provided. The name of the file is Top-Level VI.vi
I am trying to understand how the vi works inorder to make changes and ran into a few questions that I was hoping someone could answer for me please.
To start I add my sequence file and click "Test UUTs". Then a dialog box pops up asking to enter the serial number of the UUT, where and what causes that to happen in the code? After I enter my serial number it runs my sequence code and at the end another message box appears specifing in a green or red whether the UUT passed or failed. Where and what causes the Pass/Fail Boxes to happen in the code?
Thank you
Kevin
Solved!
Go to Solution.

The S/N dialog is part of the process model.
For the Sequential Model (SequentialModel.seq), the default S/N dialog in found in the 'PreUUT' sub-sequence and implemented as a DLL call.
The PreUUT sub-sequence of the SequentialModel is a callback, so you can override it in your own test sequence.
Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.
"You are what you don't automate"
Inplaceness is synonymous with insidiousness

In simple user Interface modify the sequence view to show only executing step

I want to see only the Single executing step in sequence view of the user interface
are there any egs for the same!!

This is relatively trivial to implement yourself. Handle the UIMessageEvent of the ApplicationMgr and when you get a trace UIMessage do something like the following:
if (uiMsg.Event == UIMsg_Trace)
    int notUsed;
    String currentStepName = "";
    SequenceContext context = uiMsg.Thread.GetSequenceContext(0, out notUsed);
    if (context.NextStepIndex >= 0)
        currentStepName = context.NextStep.Name;
    /// Do something with currentStepName like update an indicator control.
Hope this helps,
-Doug

'Design Patterns' for Application User Interfaces

I'm currently trying to unstick an architectural mess centred around a relatively simple user interface. The problem is thus:
The application has a number of toolbar buttons and menus, some of which require a specific frame or class of frame to be enabled. Some conditions are quite simple, others more complicated.
(Without going into any more detail, it should be possible to appreciate that this is a fairly common problem.)
For this application, I've created a large listener that accepts events from all over the program, converting them into state changes for UI controls. It feels messy, and (although it isn't finished) I suspect it'll be rather fragile.
JBuilder 4 does it by constant querying of application state - but this results in excessive CPU usage and apparant lag.
TogetherJ does it for menus by checking state immediately before showing the menu. This seemed like a good plan, but it's unsuitable for the Action/Button/MenuItem lashup I like to use.
My question is this:
In your opinion, how should an application be structured to reliably maintain the correct UI state at all times?

Check out the mediator pattern. It is pretty close to what you are describing, maybe the details you dig up on it will give you some new ideas?

Why hasn't Adobe navigation and user interface design improved as much as it could have over time?

I haven't tried CS6. I'm sure it's great based on what i've seen alone. But as a user of adobe products for a number of years, i have to noticed there are still a lot of stagnant,awkward, stiff, irriating, slowing down elements found in the navigation and user interface on cs3-cs5, that i'm sure could have been eliminated or improved on at least from 2005 or 2007 onwards. I find some of these things inexcusable and unprogressive from bad traits that defined 1980's and 1990's general computer navigation and so on.
CS5.5 has lessned this a bid bit and is more fluid in bits and pieces but for those using cs3-cs5 and in general, i find some things just horrid. As a graphic designer no one is supposed to admit the flaws or irrations of these programs. We must hail them as god, never critisize, and always adjust to new things which i think is a bit fascististic and silly
The way the tools, options are laid out can be improved to be quicker, and easier to find and use. Using your voice as a commanding system would be helpful as well.
A lot of cmds are too complex to remember, they can be simplier or resemble the name of the tool or option. Its makes a chore to follow this system and competition for the smart *** who memormized all the cmds.
The way in which you loose floating side boxes, and the amount of tools or names hidden in the bars sometimes seem random and its always a constant search to find them incase you forget where they are.
The inability to open cs4 or 5 files in cs3 is just beyond extremly annoying. Whey shouldn't you be able to open cs1 or 2 files or photoshop 9 files as well? Every five years work expires as well?
The layering system gets tricky and seems that a lot of things don't work when you normally move things. Its about going back, remembering and clicking on this or that, looking it up to make everything work. Sometimes which leaves you in a rut and wastes a good amount of time. You will always find this even after you've been using it for years.
The use of the fill paint/airbrushing, clone tool, lasso tool, pen tool, history being two steps back can be vastly improved to be much better to use
Masking and tools that have more complex features should find a way be automatically done or sampled. They can also have less complex steps and tha ability to be previewed, automatic or simpler ( in case you can't remember how to do something or aren't getting it)
A lot of the special effects, and blending modes are useless, outdated, super-ugly and don't resemble true darkroom effects ( such as polarization, and bas-relief for example) which they could much more vividly done. There also could be more options that are closer to repro cameras/CTP software for halftoning and more complex digital effects.
Having to press or get used to pressing muliple keys or clicks for the most basic things simultaneously can be reduced to be easier
Adjusting text, new documents, photos should have a smoother, quicker navigational experince where things a lot of room to be , clicked back, re-done, saved in the wrong place etc..
Indesign could use more shapes, include more features that illustrator has, and possibly even photoshop to save time.
There should be a way to remind you of features, complex things you've forgotten, other than history and daily usage/practice of the programs
The help should resemble more of "visual -learners" guide books with voice features.
There are a lot more
Regarding other things:
I think the price encorages more piracy and allows people to not have a concept of what is means to owning software.
The loss of a manual or lessening of them for certain programs is a loss because it's always useful to physical info you can flip through while looking at your program.
I think adobe should make entirely better products for professionals or people in the industry rather than spoonfeeding the same software to all.
They should also make less expensive add-ons like before for graphic software.
What do you adobe could have improved over time and if so what do you think they could have improved on?

You have this wishform to suggest improvements to Adobe products:
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
and the Creative Suites forums are here:
http://forums.adobe.com/community/creativesuites
This specific forum is only for discussions on the forums themselves, so you are not very likely to get any change by posting your comments here.

How can I improve the response time of the user interface?

I'm after some tips on how to improve the response time to mouse clicks on a VI front panel.
I have data acquistion application which used to run fine, but after spending a couple of weeks making a whole bunch of changes to it I find that the user interface has become a bit sluggish.
My main GUI VI has a while loop running 16 times a second, updating some waveform charts and polling about a dozen buttons on the front panel.
There is sometimes a delay (variable, but up to 2 seconds sometimes) from when I click on a button to when it becomes depressed. I have wired the iteration terminal of the while loop to an indicator on the front panel and can see that the while loop is ticking over during the delayed response to the mouse click, so I know that the problem is not that the whole program is running slow, just the response to mouse clicks.
Also, just for debugging purposes, I have indicators of the iterations of all the main while loops in my program on the front panel, so I can see that there are no loops running abnormally fast either.
One thing I've tried is to turn off multi-threading, and this does seem to work - the response to mouse clicks is much faster. However, it has the side effect of making the main GUI while loop run less evenly. I was trying to get a fairly smooth waveform scrolling across the screen, and when multi-threading is off it gets a bit jerky.
Any other suggestion welcome..
(I am using LabVIEW 7.1, Windows 2000).
Regards,
Mark.

Hi Altenbach,
Thanks for your reply. In answer to your questions:
I am doing both DAQ board and serial data acquisition. I am using NIDAQ traditional for the DAQ board, and VISA for the serial. I have other similar versions of this program that do only DAQ board, or only serial, and these work fine. It was only when I combined them both into the same program that I ran into problems.
The multiple while loops are actually in separate VIs. I have one VI that acquires data from the DAQ card, another VI that acquires data from the serial port, another VI that processes the data and saves to file, and another VI, the GUI VI, that displays the data in graphs and charts. The data is transferred betwen the VIs via LV2 globals.
The GUI VI is a bit more complicated than I first mentioned. It has tab control, with 4 waveform charts on one page, 4 waveform graphs on another page, and 3 waveform graphs on another page. The charts have a history length of 2560, and 16 data points are added 16 times a second. The wavefom graphs are only updated once per minute.
I don't use the value property at all, but I do use lots of property nodes for changing the properties of the graphs and charts e.g. changing plot colours, Y scale range etc. There is only one local variable (for the Tab control). All the graphs and charts have data wired directly to their terminals.
I haven't done any profiling yet.
I am building arrays in uninitialised shift registers, but this is all well under control. As the experiement goes on, more data is collected and stored, and so the memory usage does gradually increase, but only to the extent that I would expect.
The CPU usage is 100%, but I thought this was always the case when using NIDAQ with DAQ cards. Or am I wrong about this? (As a side note, I am using NIDAQ traditional, but would NIDAQmx be better?)
Execution priority of the GUI vi (and all the other VIs for that matter) is set to normal.
The program is a bit large to post here, and I'm not sure if my company would be happy for me to publicise it anyway, so I suspect that this is turning into one of those questions that are going to be impossible to answer.
Just as a more general question, why would turning off multi-threading improve the user interface response?
Thanks,
Mark.

Much improved user interface in DPM2012

I just wanted to thank the DPM team for the improved user interface.
I particularly like the Protection view where you can select "Data Source Health = Critical", this was a pain with the previous interface.
Still early days for me after updating from 2010 to 2012-SP1-RU2, but going ok.
I would next like to update the server OS from 2008 to 2012 next, I am hoping this is painless ?

Hi
Are you going to do an in-place upgrade or fresh install?

10.6: Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good it may be rejected

i am newbie in IOS i am web developer
so i use html 5 and i development jquery mobile based application.
in my application i just call view from web.I used objective c webview .
but my application rejected following issues
- Included low resolution/jagged image/s; see screenshot
- Portions of your app loaded, refreshed, ran, and/or responded very slowly.
- Was not optimized to support the device screen size and/or resolution; see screenshot
- Did not integrate with iOS features.
they said your app is slow but app speed is good(you can see here : http://teknonova.com/Map)
they said did not integrate with ios features .yes i just call URL from web view?is it illegal?
and they gave issues screenshot there is no problem with screenshot .it is good : (http://a1523.phobos.apple.com/us/r30/Purple/v4/c3/76/8a/c3768ae0-9b41-820f-9315- 40db2afc57b6/temp..gwvpnmiu.png)
what should i do?
should i delete and add new app?

10.6: Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good it may be rejected
for this problem what is a good solutions, how need to solve our problem, we need to published our apps. so plez telme the solution for this resons

Introduction of User Interfaces in SAP CRM

Can someone tell the progression on how the SAP CRM User interfaces (UI) were launched? for example, which CRM versions supported which UIs (PCUI, WEBUI etc)
Thanks
or else, is there a documentation that provides differences and commonalities between CRM UIs

Hi,
concerning CRM User Interfaces it is very simple:
1. WebClient UI: is the only supported User Interface for Users since CRM 5.1 and this is also the way forward from SAP point-of-view. SAP keeps investing in improving the WebClient UI for CRM in the coming releases.
2. SAP GUI: is only used for Adminstrative tasks, customizing and developments in CRM.
3. PCUI: is no longer supported since CRM 5.1
Kind regards,
Carl

Nokia's user interface and software A terrible e...

(hope this is in the right section, here goes)
I got my E63 about a month ago. I thought it only fair to list my grievances with the phone so far, because I am really close to selling it and buying something else, and I think Nokia deserves to know the reasons why, and will hopefully improve in the future.
I will start off with what I love about the phone, because I do in fact, really like it. The slim size, excellent keyboard, great connectivity like 3G and Wi-fi, and the reasonable battery life, make it a great phone, but its in the user interface, and actual usage of the phone, where things really start to fall flat.
The user interface is very disorganized and difficult.
Why is everything so hard to find and use? For example, if I want to change the applications that appear on my home screen, I need to navigate the following directory tree:
Menu > Tools > Settings > General > Personalisation > Mode Settings > Home Screen Applications > Application Shortcuts > Shortcut 1
and then, when I finally get to the list, the items arent even in any order!
You must be joking, what a horrible menu! Its insane. As a user, I feel like its a terrible experience.
But thats not all. Why are there 2 notes applications on my phone? There's notes, and active notes. Why does Nokia OVI store exist twice, once in the main menu, and once under installations? Why do I have Contacts, and OVI contacts on my phone? Why can't my phone have just one app that works well, instead of 2 that differ slightly.
Why is email setup in the installations menu? Why isn't it under email, where mailboxes get set up? Its just sitting there cluttering up Installations, when its something you only use once or twice.
Not to mention the fact that the configuration settings are all over the place, i.e. there is an Email Key setting in Menu > Tools > Settings > General. Its all on its own, not near anything. Why isn't it in the same menu where the other shortcut keys get set? Or even in the email app settings?
I am not naive, I know that the E63 is on the cheaper end of the scale, so I can't expect it to be the fastest phone in the world, but scrolling through my email in HTML mode is so horribly slow, and the view tends to jump from left to right on some emails, I hardly even use the phone to check my email anymore, which is sad because that is the reason I chose the E63.( for the nice keypad and email syncing)
These are just SOME of the things that I have noticed. So please Nokia, PLEASE PLEASE PLEASE! Spend some of your R&D money on user interface and user experience!
If there is anything you take away from this letter, let it be this:
Doing anything on the phone just feels like hard work, it makes me not want to use the phone.
Your phones should be simple and easy to use, even without the mass of Help files that appear in a lot of the menus.
I know, some people may say that if I want a better experience, I should be willing to buy a more expensive phone. Well, I can say that if I do spend more money on a phone, the chance is very slim that it will be a Nokia.
Really, I am not being nasty, just trying to be honest. I know that Nokia is run by human beings like myself, so I tried to be polite, and I dont intend to hurt anyones feelings.
I am quite willing to answer any questions you may have. Its a bit of a pipe dream, but I would love to see Nokia release an entirely new version of the phone software, with everything re-organized and re-done. The sad truth is that will probably never happen, and I will end up swopping my E63 for something that is easy and pleasant to use.
So please, let me know if there is anything I can do to change the situation, or help you guys in making this better for everyone.

"If your not used to symbian you'll learn it quick enough, compared to android it's childsplay."
On the contrary, Ive been using Nokia phones for the last 8 years, and for the last 2 years Nokia exclusively, and the UI has just got worse.
The fact that "you'll learn it" is of no comfort. Why should I have to spend hours learning how to use a cellphone? Whenever I want to do something I havent done before, I have to spend time digging through obscure menu options. That is absurd.
"What phone do you have in mind to replace the E63, that would help us users alot more then telling us what is wrong with your phone. Although over all I like my e63."
I don't have any specific phone in mind, Im just going to ask and look around until I find something with an operating system that is organised in a logical manner, and that allows me to access and read my email quickly and easily.
I put this here hoping that other users would come forward with UI related things that they were unhappy about, and then Nokia would take notice. I could easily have just gone out and changed phones, but I chose to do something different.

A more successful experiment in creating compositable user interfaces for Config Dialogs

A couple weeks ago I posted an experiment in creating compositable user interfaces using transparent subpanels. The approach might best be described as, "It at least was notable for being novel."
Today, I'm posting another attempt, this one along more traditional lines, and far more successful. Particularly notable: this one can do all the arbitrary composition of the last one AND it solves the TAB order problem.
This solution uses a picture control and renders N copies of a control. When the user tabs to a control or moves the mouse over the control, a real control slides into that position to be able to catch the events (update mouse over draw state, highlight for keyboard focus, handle typing, etc). When the Value Change occurs, a master array of data is updated and the picture control is updated.
This is something that has been attempted in various forms in the past, but there are two aspects of this particular implementation that make it nice:
its programmatic interface for specifying the behavior of the various objects should make it fairly easy for a user of the framework to programmatically generate their dialogs
it handles the TAB problem without flickering, something I haven't seen in other attemps
This idea spawns out of conversation about the previous experiment -- thanks to those of you who posted on various forums, e-mailed me, or, in a couple cases, showed up at my desk. That last one is not something I'm encouraging unless you work at NI... just saying. :-)
Now, this experiement has already yeilded some interesting conversation. We note that as long as controls are instantiated independent of each other -- that is, no property of one control depends upon the property of another control -- this dialog system scales nicely. But in this experiment, I implemented Radio Buttons, which interact with each other -- when one is set True, the others go False. As soon as controls start interacting with each other (such as graying out one control when a checkbox is toggled, or having expandable sections, or really complex cases like updating a graph as some options change, like happens in some Express VI config dialogs) then we start needing ways to refer to the other controls. This rapidly moves us in one of two directions: naming controls or creating references. The naming approach is definitely my preference as it fits better with dataflow and I can do some interesting effects with breaking apart some of the tree. But all of this quickly starts sounding like "Please implement a XAML parser in LabVIEW." For those of you unfamiliar with XAML, in the world of UI design, it might very well be the coolest thing since sliced bread. A XAML string would indeed fit with dataflow, and we could start building that up. I hesitate to head down this road for two reasons. One, as many have noted, there's really not a good XML parsing library written in LabVIEW that can give me a useful DOM tree. Two, that's a huge project and my gut sense is that you'd have to complete a fairly large chunk of it before you'd start seeing any return on investment. But it is worth thinking about -- I might be wrong. Wouldn't be the first time. This code that I've posted today can at least get you started on the generation side if one of you decides to become industrious.
I'm turning my attention away from this project for now... coding in G is lots of fun, and I wish I could spend more days doing it, but this has been a side project and it's time to get back to my assigned projects in text programming. Building a powerful platform for automatic UI generation in LabVIEW would be really useful -- I see lots of requests for this sort of thing, and other languages are pulling ahead of us in this domain.
[UPDATE 5/17/2012 - There is an improved version.]
Solved!
Go to Solution.
Attachments:
ConfighThroughCtrlCreation.zip ‏558 KB

Elijah K wrote:
Thanks for posting this Aristos. I would normally be one of those to go bug you at your desk, but in case I'm not the only one with this question... which particular flickering problem are you referring to? The act of switching tabs? In all honesty, I've never noticed...
When you move controls around on the screen, normally you try to Defer Panel Updates while you do that. But Defer Panel Updates has an effect on control's abilities to catch certain mouse clicks, so when you're trying to move a control to catch the mouse, you have to work a lot without Defer Panel Updates, so if you're adjusting captions, etc, to match the new location, you can see flicker as properties adjust. You can move the control off-screen, as long as you have already updated the picture control to reflect the changes. It took a while to catch all the ways that the flickering can crop up. I think I got 'em all.
Attached are the VIs saved for LV 2009. Actually, they're saved for LV 8.6, but it doesn't work in 8.6 because of a bug in the picture control that existed back then.
Attachments:
ComposableUI_LV2009.zip ‏391 KB

Hi all, i'm new and facing a problem while creating a new file for Xcode. I can't select the box "with XIB for user interface" if the subclass is "UIViewController".this problem happen after i upgrade Xcode to 4.6 version.Appreciate for any help rendered.

Hi all, i'm new to Mac book & Xcode. I'm learning and facing problems while creating a new file for Xcode. Before i upgrade the software, i have no issue to create simple steps in apps. After upgrade Xcode to 4.6 version, i'm facing lot's of issue eg.
1) "the identity "iphone developer" doesn't match any valid certificate/ private key pair",
2) can't select the box "with XIB for user interface" if the subclass is "UIViewController"..
Appreciate for any help rendered.

Mikko777 wrote:So what is the best?
I wouldn't judge. I've been to Arch for a week, you know? But as said, it's VERY close to it.
What I dislike after a week is makepkg not handling dependencies automatically (which would be overhead, so probably not appropriate).
Mikko777 wrote:Also theres KDEmod for modular kde, dunno if its for 64 bits tho.
Don't actually need that as said ... I see no real benefit of having that other than not beeing a KDE user or having Gentoos useflags.
Mikko777 wrote:PS:You produce a lot of text and welcome smile
Yeah. Wonder why I'm still employed? So do I ...

Simple User Interface Improvement

Similar Messages

Maybe you are looking for