| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] 19 20 30 .. 30 :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Kapila Parthalan
   |
Posted - 2010.08.05 17:16:00 -
[511]
I got the autoupdate to work by deleting eve-files from the update servers list so that it goes to starfreeze instead, then restarting EMMA. So, an issue with the update files on eve-files does seem likely.
|
Kapila Parthalan
|
Posted - 2010.08.05 18:22:00 -
[512]
Now that I have 1.5.1.5, I have some issues to report:
I'm still seeing problems with assets. Transaction and order updates resulted in some inaccurate assets data for one item (which has also been erroneously shown as missing earlier).
The transactions update made a change in the quantity of the normal stack that matched the net change from transactions since the last update. On top of this, though, the For Sale Via Market stack disappeared from assets, even though a sell order for this item still appeared in the orders window. This resulted in some missing units overall. The transactions themselves seem fine.
After the orders update, this item still had no units shown in the assets window as For Sale Via Market even though there was an active sell order that was correctly shown in the orders window. This sell order was newly created since the last update.
After these, I did an assets update. The unacknowledged asset changes window showed a gain in this item that matched the discrepancy from the previous inaccurate data.
 Quote:
Grid Calculator will now treat red isk values as negative.
This doesn't work; they still show up as positive.
|
Dalden V
Blue Lounge Industries
|
Posted - 2010.08.05 20:43:00 -
[513]
Edited by: Dalden V on 05/08/2010 20:43:43
Originally by: Lost Hamster
Edit2: I have the feeling that something is not right with Eve-Files.
I have just downloaded the file, and I found a version 1.5.1.2 inside
Then I have downloaded it again, and I got a different file with the correct 1.5.1.5 version inside. 
I had another look at the file I got from eve-files and it was actually 1.4 - which is why it probably did not work for me when I tried to manually update the files.
Originally by: Kapila Parthalan
I got the autoupdate to work by deleting eve-files from the update servers list so that it goes to starfreeze instead, then restarting EMMA. So, an issue with the update files on eve-files does seem likely.
Bingo. After removing eve-files from the list of update servers in user.config EMMA found an update and updated me from 1.5.1.0 to 1.5.1.5, thanks!
|
Ambo
Mortis Angelus
|
Posted - 2010.08.06 07:49:00 -
[514]
Originally by: Kapila Parthalan
Now that I have 1.5.1.5, I have some issues to report:
I'm still seeing problems with assets. Transaction and order updates resulted in some inaccurate assets data for one item (which has also been erroneously shown as missing earlier).
The transactions update made a change in the quantity of the normal stack that matched the net change from transactions since the last update. On top of this, though, the For Sale Via Market stack disappeared from assets, even though a sell order for this item still appeared in the orders window. This resulted in some missing units overall. The transactions themselves seem fine.
When sell transactions are added to the database, EMMA will first try to remove those items from a matching 'for sale via market' stack, if it can't find enough then it will remove items from a 'normal' stack.
In your case it sounds like either the for sale via market stack was already empty or the same amount has been removed from both for sale via market and normal stacks..
I can't see any problems with this code though and it certainly works fine for me. Where there any complications with this? (i.e. did you have more than one sell order for the same item, the same item being moved around or used in other ways at the same time, etc)
Originally by: Kapila Parthalan
After the orders update, this item still had no units shown in the assets window as For Sale Via Market even though there was an active sell order that was correctly shown in the orders window. This sell order was newly created since the last update.
That's actually correct behaviour, although slightly confusing. Changes to assets are only made during the transaction and asset updates. i.e. the orders update will not move items from a normal stack into a for sale via market stack.
Originally by: Kapila Parthalan
Quote:
Grid Calculator will now treat red isk values as negative.
This doesn't work; they still show up as positive.
Can you give some more info on this? Again, it works for me so any extra info about which window you have the problem in, which columns are involved, etc would help.
Originally by: Dalden V
Originally by: Kapila Parthalan
I got the autoupdate to work by deleting eve-files from the update servers list so that it goes to starfreeze instead, then restarting EMMA. So, an issue with the update files on eve-files does seem likely.
Bingo. After removing eve-files from the list of update servers in user.config EMMA found an update and updated me from 1.5.1.0 to 1.5.1.5, thanks!
Thanks for the update. Sounds like eve-files is definitely having issues then. Think I'll switch it round so that starfreeze will be the first place EMMA looks for updates if both are available.
--------------------------------------
|
Kapila Parthalan
|
Posted - 2010.08.06 13:41:00 -
[515]
Originally by: Ambo
In your case it sounds like either the for sale via market stack was already empty or the same amount has been removed from both for sale via market and normal stacks.
The stack wasn't empty. I think the latter is correct.
Originally by: Ambo
I can't see any problems with this code though and it certainly works fine for me. Where there any complications with this? (i.e. did you have more than one sell order for the same item, the same item being moved around or used in other ways at the same time, etc)
At the time of the previous update, there was one sell order for this item. After that update and before the next one, I created another sell order and had the previous one filled. Nothing was moved or used in any way other than through the market.
I'll see if I can provide more details later today.
Originally by: Ambo
Originally by: Kapila Parthalan
Quote:
Grid Calculator will now treat red isk values as negative.
This doesn't work; they still show up as positive.
Can you give some more info on this? Again, it works for me so any extra info about which window you have the problem in, which columns are involved, etc would help.
That's strange. This happens everywhere I checked: all of the isk columns in transactions, journals, and orders.
|
Argro
Caldari
A A Enterprises Inc.
|
Posted - 2010.08.06 16:11:00 -
[516]
I have an issue with my Orders viewing page.
Each order is displayed twice, and also I cannot filter orders by owner. If I do not have the 'Any Owner' option ticked then no orders will display at all.
Any suggestions on what I am doing wrong?
Thanks, and sorry if this has been asked before.
|
Kapila Parthalan
|
Posted - 2010.08.06 16:36:00 -
[517]
Originally by: Kapila Parthalan
...
I'll see if I can provide more details later today.
I've discovered that this particular issue is apparently caused by buying from your own sell order. If you want, I'll send you some XML files that demonstrate the issue.
Originally by: Argro
I have an issue with my Orders viewing page.
Each order is displayed twice, and also I cannot filter orders by owner. If I do not have the 'Any Owner' option ticked then no orders will display at all.
Any suggestions on what I am doing wrong?
Thanks, and sorry if this has been asked before.
I don't know what is causing that problem, but could you tell us what version of EMMA you are using?
|
Flodez
|
Posted - 2010.08.06 17:31:00 -
[518]
Don't know if this has been reported, but there's a typo in the tutorial, under the "Assets Tracking->Assets Change Reasons", it says "Destoryed or Useed". |
Argro
Caldari
A A Enterprises Inc.
|
Posted - 2010.08.06 18:24:00 -
[519]
Originally by: Argro
I have an issue with my Orders viewing page.
Each order is displayed twice, and also I cannot filter orders by owner. If I do not have the 'Any Owner' option ticked then no orders will display at all.
Any suggestions on what I am doing wrong?
Thanks, and sorry if this has been asked before.
I don't know what is causing that problem, but could you tell us what version of EMMA you are using?
Version 1.5.1.0
|
Kapila Parthalan
|
Posted - 2010.08.06 18:38:00 -
[520]
Originally by: Argro
Version 1.5.1.0
You might want to see if this has been fixed in a later update. To get auto-update to work, go to other settings, click on eve-files in the list of update servers and press delete, then restart EMMA.
This is also in response to Dalden; you don't have to edit the config files to change this.
|
|
|
Dalden V
Blue Lounge Industries
|
Posted - 2010.08.07 09:24:00 -
[521]
Originally by: Kapila Parthalan
This is also in response to Dalden; you don't have to edit the config files to change this.
Del on the keyboard? I tried right-clicking to find a popup window and also couldn't see a delete button to click with my mouse so assumed you couldn't do it from the UI 
|
Anna Weston
Gallente
Holdings Inc
|
Posted - 2010.08.07 13:00:00 -
[522]
Originally by: Ambo
1.5.1.5 Beta is now up.
This contains a fix for the issue that causes corporate orders to keep asking for acknowledgement
Big thanks to Lost Hamster for tracking this bug down for me.
- Version 1.5.1.0 included a change to store corporate orders and assets by the corporation ID rather than the character ID of the character that had been used to retreive the data from the API. Unfortunatley, a bug slipped in that caused an order's owner to be set to the character ID when it was acknowledged. This has now been fixed.
Very nice work again Ambo.
I updated yesterday morning (after removing EVE-files from the update list) and I'm now only getting order acknowledgement requests for orders that have actually been completed. Also no further errors in the Exception Log since the update.
I still am getting a bunch of "item is lost or destroyed" messages for items that were sold through orders but for now I'm assuming these are a hangover from the previous order confusion. If I'm still seeing these next week I'll post an update.
And finally. I'm pretty sure this is an old behaviour (I'm sure I remember it from when I was using EMMA last year) but it's a mild irritation. If I leave EMMA on in the background then I get multiple (duplicate) order acknowledgment windows to click through, possibly one for every API update that happened while EMMA was minimised. This is just a UI niggle but it would be nice if it went away. 
|
Ambo
Mortis Angelus
|
Posted - 2010.08.10 07:17:00 -
[523]
Thanks for all the info guys. Hoping to get a new release out soon.
--------------------------------------
|
Vested Interest
|
Posted - 2010.08.10 14:44:00 -
[524]
Edited by: Vested Interest on 10/08/2010 14:44:41
Ok so I've got like 18-19 guys to queue up for updates currently. The 1.5 and later release seems to be doing something different.
What I do is once a day I enable everyone's updates for a single API call, and then disable them again until next time. The odd thing is that it won't enqueue the Assets update (per character) until after the Transactions Journal and Orders are finished making their call. In other words, the Assets update sits there with an orange status, refusing to queue up, until the first 3 sections are finished. What I'd like is for all 4 sections to queue up so I can uncheck the box and move on quickly. I am pretty sure it used to do this.
Also, seem to have lost the old "click the portrait to enable/disable updates". Just fyi, I kinda liked it because it makes the above process faster yet.
An alternative to the above would be a hotkey shortcut (ctrl-shift-space?) to enable/disable all queues. That'd be pretty cool.
Thanks for the help!
|
Ambo
Mortis Angelus
|
Posted - 2010.08.10 15:14:00 -
[525]
Originally by: Vested Interest
Ok so I've got like 18-19 guys to queue up for updates currently. The 1.5 and later release seems to be doing something different.
What I do is once a day I enable everyone's updates for a single API call, and then disable them again until next time. The odd thing is that it won't enqueue the Assets update (per character) until after the Transactions Journal and Orders are finished making their call. In other words, the Assets update sits there with an orange status, refusing to queue up, until the first 3 sections are finished. What I'd like is for all 4 sections to queue up so I can uncheck the box and move on quickly. I am pretty sure it used to do this.
That is the way it used to work yes. It was changed so that the asset update was always guaranteed to occur after the transaction and orders updates.
In the next version, I've changed this so that the downloading of XML and updating of the database are more seperate operations.
This allows me to download all the XMLs at once and then keep them in a queue. The asset XML simlpy gets moved to the back of the queue until there are no other items left.
(In short, this issue will be resolved with the next update)
Originally by: Vested Interest
Also, seem to have lost the old "click the portrait to enable/disable updates". Just fyi, I kinda liked it because it makes the above process faster yet.
This is still in there, will check why it's not working.
Originally by: Vested Interest
An alternative to the above would be a hotkey shortcut (ctrl-shift-space?) to enable/disable all queues. That'd be pretty cool.
Thanks for the help!
Nice idea. I'll add something that will allow you to update everything in one go.
Another thing you may be interested in from the next update is the compact status view. This reduces the amount of space taken up by each API status update panel. Will probably be pretty handy since you have so many chars included in the group.
--------------------------------------
|
Ambo
Mortis Angelus
|
Posted - 2010.08.11 14:25:00 -
[526]
Version 1.5.2.0 beta is now available.
- EMMA will now retrieve data from the industry jobs API and store it in the database (although currently it won't do anything with it)
- Added a compact version of the API update status view. It can be enabled in settings -> api update settings.
- Added an 'Update All/None' button to the top of the API update status panel. This will enable/disable API updates for ALL characters and corporations in the current group.
- Corrected bugs in the asset and order views that would show the character's assets when the user tried to view a corproation's data.
- Corrected a bug that caused items bought via contract to have negative 'cost' values.
- Corrected a spelling mistake in the tutorial text.
- The default update server is now starfreeze instead of eve-files. (Note existing installations will still keep thier current settings, to set starfreeze as the default, go into settings -> auto update settings and click restore defaults)
- Corrected a bug that caused many instances of the unacknowledged orders window to be opened if EMMA was minimized while updates were occuring.
- Added an option 'Show in taskbar when minimised'. This is in settings -> other settings. Previously, EMMA was always hidden when it was minimised. This has led to various problems in my daily use so I've added this setting. Default is for EMMA to be displayed in the taskbar when minimised.
--------------------------------------
|
Anna Weston
Gallente
Holdings Inc
|
Posted - 2010.08.11 15:34:00 -
[527]
Nice work and excellent decision to minimise to taskbar. Windows 7 tray icons are a bit annoying to deal with.
One slight problem with the API update display I see is that that there seems to be a slight mismatch between the window content and the window border on the right-hand edge, so that the last few millimetres of text is cut off. This isn't an issue of window size, I can drag the window as wide as I like and the text still refreshes into the same position. Minor really.
And I hope you don't take it the wrong way if I start raising new issues, but I can't help myself while I see how much stuff you're adding and fixing right now!
The Net Asset Value report is theoretically my favourite report as it would be the ideal tool for measuring the progress of my trading business. Except that there always seems to be something funky going on with the numbers somewhere so it's hard to trust the results.
1)Cash in Escrow consistently shows as zero in the most recent period of a NAV for multiple periods, or an all-time NAV report. Earlier periods will show varying amounts for Cash in Escrow, none of them correct and some of them negative.
2) Wallet balances are correct for the most recent period or in an all-time report, but in earlier periods the wallet balances of corp members are always identical to the corp wallet balance.
Historical asset values look very odd as well though right now it's hard for me to see enough of a pattern to make a useful bug report.
Once again, thanks for all your work so far.
|
Ambo
Mortis Angelus
|
Posted - 2010.08.11 19:36:00 -
[528]
Originally by: Anna Weston
Nice work and excellent decision to minimise to taskbar. Windows 7 tray icons are a bit annoying to deal with.
One slight problem with the API update display I see is that that there seems to be a slight mismatch between the window content and the window border on the right-hand edge, so that the last few millimetres of text is cut off. This isn't an issue of window size, I can drag the window as wide as I like and the text still refreshes into the same position. Minor really.
Yeah, I just noticied the same thing. Serves me right for only testing on XP.
Originally by: Anna Weston
And I hope you don't take it the wrong way if I start raising new issues, but I can't help myself while I see how much stuff you're adding and fixing right now!
The Net Asset Value report is theoretically my favourite report as it would be the ideal tool for measuring the progress of my trading business. Except that there always seems to be something funky going on with the numbers somewhere so it's hard to trust the results.
1)Cash in Escrow consistently shows as zero in the most recent period of a NAV for multiple periods, or an all-time NAV report. Earlier periods will show varying amounts for Cash in Escrow, none of them correct and some of them negative.
2) Wallet balances are correct for the most recent period or in an all-time report, but in earlier periods the wallet balances of corp members are always identical to the corp wallet balance.
Historical asset values look very odd as well though right now it's hard for me to see enough of a pattern to make a useful bug report.
Once again, thanks for all your work so far.
No problem.
The NAV report is based a lot on orders so all those duplicate orders you had will be screwing it up right now.
Unfortunately, these can't be corrected automatically so you really have 3 choices:
1. Wait for a while and be aware that older nav reports will always be messed up.
2. Try to correct the data manually with something like sql management tool express.
3. Nuke the old database and start from fresh.
I can give you some help with option 2 if you decide to go that way and I'll see if there are different ways I could produce the data but for now, I'm afraid your stuck with it.
--------------------------------------
|
Anna Weston
Gallente
Holdings Inc
|
Posted - 2010.08.11 20:23:00 -
[529]
Originally by: Ambo
No problem.
The NAV report is based a lot on orders so all those duplicate orders you had will be screwing it up right now.
Unfortunately, these can't be corrected automatically so you really have 3 choices:
1. Wait for a while and be aware that older nav reports will always be messed up.
2. Try to correct the data manually with something like sql management tool express.
3. Nuke the old database and start from fresh.
I can give you some help with option 2 if you decide to go that way and I'll see if there are different ways I could produce the data but for now, I'm afraid your stuck with it.
Yes, I recognise that problem is always in the background and I've provisionally decided to nuke my database and start again once this beta phase is over.
However, I'm pretty sure the messed up orders don't explain problem 2 and I'm not sure I can see how they explain problem 1. Also, I was testing with a NAV report with 10 daily report periods so the most recent days should be free of the effects of the duplicated orders, no?
|
Lucyna
Minmatar
Interstellar Killer Bee Enterprises
|
Posted - 2010.08.12 01:24:00 -
[530]
HI
I'm getting a
violation of primary key constraint 'pk_AssetsHistory'. cannot insert duplicate key in object 'dbo_AssetsHistory'....
error when I generate NAV reports. I'm running the latest beta.
|
|
|
Kapila Parthalan
|
Posted - 2010.08.12 03:20:00 -
[531]
The check for updates during startup did not find the update, even though clicking the update button in the settings did work. I have enabled check for updates when EMMA starts and check for beta updates. The same happened for the previous update as well, to 1.5.1.2 (which was before the eve-files problem started).
|
Ambo
Mortis Angelus
|
Posted - 2010.08.12 07:14:00 -
[532]
Originally by: Kapila Parthalan
The check for updates during startup did not find the update, even though clicking the update button in the settings did work. I have enabled check for updates when EMMA starts and check for beta updates. The same happened for the previous update as well, to 1.5.1.2 (which was before the eve-files problem started).
This was due to a change that made sure EMMA would only auto check for updates once every 48 hours. In retrospect, I decided it was pretty confusing so changed it back to 5 hours in the latest version.
Originally by: Lucyna
HI
I'm getting a
violation of primary key constraint 'pk_AssetsHistory'. cannot insert duplicate key in object 'dbo_AssetsHistory'....
error when I generate NAV reports. I'm running the latest beta.
Interesting.. I think this might be another problem down to switching over to storing corporate asset data by corp id instead of char id.
Will take a look.
--------------------------------------
|
Lucyna
Minmatar
Interstellar Killer Bee Enterprises
|
Posted - 2010.08.12 19:39:00 -
[533]
Originally by: Ambo
Originally by: Kapila Parthalan
The check for updates during startup did not find the update, even though clicking the update button in the settings did work. I have enabled check for updates when EMMA starts and check for beta updates. The same happened for the previous update as well, to 1.5.1.2 (which was before the eve-files problem started).
This was due to a change that made sure EMMA would only auto check for updates once every 48 hours. In retrospect, I decided it was pretty confusing so changed it back to 5 hours in the latest version.
Originally by: Lucyna
HI
I'm getting a
violation of primary key constraint 'pk_AssetsHistory'. cannot insert duplicate key in object 'dbo_AssetsHistory'....
error when I generate NAV reports. I'm running the latest beta.
Also, I now get crashes
Interesting.. I think this might be another problem down to switching over to storing corporate asset data by corp id instead of char id.
Will take a look.
|
Ambo
Mortis Angelus
|
Posted - 2010.08.13 07:54:00 -
[534]
Edited by: Ambo on 13/08/2010 07:54:29
Version 1.5.2.2 beta is now up.
This primarilly focuses on fixing the NAV report (I didn't realise how badly broken it had become with all the other changes elsewhere)
- Corrected a bug that caused the NAV report to store calculated corporate asset values using the character ID of the associated character rather than the ID of the corp itself.
- Corrected a bug in the NAV report that would cause the 'cash in escrow' for a corp to always be reported as 0 for the most recent period. (This also caused subsquent periods to be incorrect.)
- Corrected a bug in the NAV report that could cause incorrect wallet balances to be reported for characters that were part of corps that were also included in the report group.
- The changes to assets in 1.5.0.0 included updating the assets table to store the current assets in sell orders. The NAV report was calculating the value of items in sell orders in a seperate section so they were being counted twice. This has been corrected by removing the seperate 'sell order value' section from the NAV report.
- When the NAV report calculates historic asset values, it uses transaction data to work out what changes have occured to assets within a particular time frame. Now, it will also use the AssetsLost and AssetsProduced tables. (These store changes to assets that are picked up by EMMA's asset tracking system.)
- The 'cash in escrow' part of the NAV report has been revamped and will now be far more accurate.
- Fixed an occasional bug with the display of the compact API update status panel.
- Fixed a bug that caused the API status update panels to appear slightly under the edge of the main update status window in Windows Vista & 7.
- Fixed a bug that caused EMMA to think there was new documentation available every time it was was updated.
- Fixed a bug that caused the vertical scroll bar to appear slightly under the edge of the window in reports on Windows Vista & 7.
--------------------------------------
|
Anna Weston
Gallente
Holdings Inc
|
Posted - 2010.08.13 12:08:00 -
[535]
Edited by: Anna Weston on 13/08/2010 12:14:56
*drools*
Edit: Oops, I think you "fixed" the API update status window in the wrong direction. I can't see the timers at all now, in Windows 7.
|
Ambo
Mortis Angelus
|
Posted - 2010.08.13 12:32:00 -
[536]
Originally by: Anna Weston
Edited by: Anna Weston on 13/08/2010 12:21:02
Edited by: Anna Weston on 13/08/2010 12:14:56
*drools*
Edit: Oops, I think you "fixed" the API update status window in the wrong direction. I can't see the timers at all now, in Windows 7.
Edit 2: I'm thinking now's the time to nuke this database so that I can properly use/test the New Improved NAV. If I delete the database files under C:\Users and copy in the blank database files that get installed in the EMMA folder, will that be all that's needed? Are API details etc stored in the database or in a separate config file somewhere?
God damn it! I actually had this ready to go yesterday but waited so that I could test it on my win 7 pc and there it was fine. Guess there must be something else going wrong here...
Yes, copying in the blank database files from the install folder will do the job nicely.
Almost everything is stored in the database, the only things that are not are in the *.exe.config file. This contains things like database connection strings, main window size & position, auto update settings, etc.
--------------------------------------
|
Hexxx
Minmatar
|
Posted - 2010.08.13 12:35:00 -
[537]
Originally by: Ambo
Originally by: Anna Weston
Edited by: Anna Weston on 13/08/2010 12:21:02
Edited by: Anna Weston on 13/08/2010 12:14:56
*drools*
Edit: Oops, I think you "fixed" the API update status window in the wrong direction. I can't see the timers at all now, in Windows 7.
Edit 2: I'm thinking now's the time to nuke this database so that I can properly use/test the New Improved NAV. If I delete the database files under C:\Users and copy in the blank database files that get installed in the EMMA folder, will that be all that's needed? Are API details etc stored in the database or in a separate config file somewhere?
God damn it! I actually had this ready to go yesterday but waited so that I could test it on my win 7 pc and there it was fine. Guess there must be something else going wrong here...
Yes, copying in the blank database files from the install folder will do the job nicely.
Almost everything is stored in the database, the only things that are not are in the *.exe.config file. This contains things like database connection strings, main window size & position, auto update settings, etc.
If you have the ability to, maybe construct some unit tests using NTest or MSUnit? It may help.
Projects Blog |
Kapila Parthalan
|
Posted - 2010.08.13 12:53:00 -
[538]
Edited by: Kapila Parthalan on 13/08/2010 12:54:44
Originally by: Ambo
Originally by: Kapila Parthalan
The check for updates during startup did not find the update, even though clicking the update button in the settings did work. I have enabled check for updates when EMMA starts and check for beta updates. The same happened for the previous update as well, to 1.5.1.2 (which was before the eve-files problem started).
This was due to a change that made sure EMMA would only auto check for updates once every 48 hours. In retrospect, I decided it was pretty confusing so changed it back to 5 hours in the latest version.
I see. It did indeed find the latest update automatically.
I have not seen the issue with missing assets showing up incorrectly in unacknowledged asset changes since I updated from version 1.5.1.2 to 1.5.1.5. I still have no idea why it was happening, but it may have been fixed.
The most recent issue I had that was caused by buying from your own sell order is still present.
Edit:
Originally by: Anna Weston
Edit: Oops, I think you "fixed" the API update status window in the wrong direction. I can't see the timers at all now, in Windows 7.
I see the same thing.
|
Ambo
Mortis Angelus
|
Posted - 2010.08.13 13:31:00 -
[539]
Originally by: Hexxx
Originally by: Ambo
Originally by: Anna Weston
Edited by: Anna Weston on 13/08/2010 12:21:02
Edited by: Anna Weston on 13/08/2010 12:14:56
*drools*
Edit: Oops, I think you "fixed" the API update status window in the wrong direction. I can't see the timers at all now, in Windows 7.
Edit 2: I'm thinking now's the time to nuke this database so that I can properly use/test the New Improved NAV. If I delete the database files under C:\Users and copy in the blank database files that get installed in the EMMA folder, will that be all that's needed? Are API details etc stored in the database or in a separate config file somewhere?
God damn it! I actually had this ready to go yesterday but waited so that I could test it on my win 7 pc and there it was fine. Guess there must be something else going wrong here...
Yes, copying in the blank database files from the install folder will do the job nicely.
Almost everything is stored in the database, the only things that are not are in the *.exe.config file. This contains things like database connection strings, main window size & position, auto update settings, etc.
If you have the ability to, maybe construct some unit tests using NTest or MSUnit? It may help.
The problem is less the test itself and more the environment. At work I can test on win XP only and build release versions. At home I can test on both XP and win 7 but cannot build release versions.
The layout issue still does not occur on XP and since that's all I can test on at work, the use of unit testing becomes a moot point. (at least in this case) 
--------------------------------------
|
Ambo
Mortis Angelus
|
Posted - 2010.08.13 15:09:00 -
[540]
1.5.2.3 beta is up
Will hopefully resolve this layout problem but I can't be sure (since I can't test on win 7 right now)
I'll be away for the next week so hopefully this works. 
--------------------------------------
|
|
|
|
|
| |
|
| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 [18] 19 20 30 .. 30 :: one page |
| First page | Previous page | Next page | Last page |